Me too. I don't have any problems with it and I tested it by dropping internet connection and it works fine for me.
One of the things I did early on when this was first reported was to make a simple program which ONLY called GetInternetState() and gave to people who had the issue, so can't really be any more specific than this.
I am not using async (but it doesn't matter because the freeze occurs on GetInternetState() not on HTTPRequest (which times out correctly if needed).
It was a casual question, because I was going to take the GetInternetState() call out of the code, because only about 2 people in 100+ testers are getting this issue - one of which seemed to be only on wireless and OK on wired, so I was just wondering.
Still, I've found many issues I've had to work around because a tester finds something that only seems to happen on their PC setup and no-one else does.. this seems to be one of those things?
[edit] I only wanted to use it to inform the user if they had an issue with their own connection to differentiate from a problem on the web server.
