When installing PicoScope 6 there are several very long delays where nothing is apparently happening but what's actually happening is the installer mindlessly banging away in the background, attempting to connect to CRL.VERISIGN.NET.
This being Windows, I allow only LAN access and block any attempted WAN access - which is effectively the same thing as having no WAN connection from the installer's viewpoint.
Please add some intelligence and check for WAN access first, instead of just assuming it's available and "going to sleep" when it isn't.
Also; why is access to CRL.VERISIGN.NET required?
When starting a Windows application it's conventional to provide some indication of activity if the application is expected to experience some delay before it becomes obvious to the user that it's running. In other words, the hourglass cursor.
While PicoScope is sorting out its USB connection to the 'scope it's not obvious that something is happening and once again, gives the impression that it's "gone to sleep".
(P4 3.02GHz, 4GB RAM, WinXP Pro, 3206 oscilloscope)