"Cannot connect to the Internet" is a USELESS error message. It does not tell the CAUSE of the error. It would be easy to name the cause of the error by naming:
WHERE the error occurred in the program flow
WHAT exactly caused the error
This information would be easy to get for a programmer. I wonder WHO wrote the program and the error management. I am not happy about the lacking support in getting this resolved.
An example: When a car stops running, it is meaningless to have an indicator on the dashboard that says, "The car is no longer running." There must be an indicator for the fuel level, the coolant temperature, for the oil level, and so on. These are all elementary things. A programmer should know that.
It is only till Microsoft recently caused a breaking issue related to root certificate handling on a small percentage of machines with Windows updates, that this problem popped up. Never in the 10 years before was this a real issue. Even now, the Microsoft error result codes returning from the wininet API tell little to nothing about this specific problem and weren't helpful for us either to analyze this case.
And it is never useful to use denigrating language in communication either.