I was having an issue connecting to a wifi network last week. Just got "Sorry, we can't connect to that." every time. The troubleshooters were useless - "Have you tried setting your computer to autmagically connect to Starbucks_WIFI?" "Have you tried plugging in an ethernet cable?"
After I (manually) Toggled wifi, toggled my router, restarted, reinstalled drivers, set my card to never turn off due to power concerns (who knew that was default?) and failed to find any form of error message in event viewer, I started getting into the CMD. Surely, I reasoned, I can get an error if I connect in a CLI.
The first problem was that I wasn't already set up with that connection. I don't know how the profile XMLs are set up so I had to export my Wifi profile from another computer with netsh and throw it on using a flash drive. After I'd imported that - which is TERRIBLE, why can't I just give it the network and pass? - I tried connecting. Once, trice, three times.
Every time I used Netsh connect the response was "Connection successful!" Obviously it never was. I threw some pings to see if my UI was lying, but no, it just failed to connect every time. Who knows why?
I'm getting angry again just thinking about it. I even asked microsoft tech support. After about an hour the response was "I have nothing else for you to try, I have no way to find out the error, but if you pay us money we can set up a remote session." Yeah, that will help me get online.
I tried being a microsoft apologist from around 2009 to mid-2013. It wasn't for me.