ksh
New Member
Following some of your threads and digging more, I have now conquered my problem. 
The issue was USB wireless interface would not work after waking from S3. I was able to restore functionality by disabling the device and re-enabling (key part of diagnosis). That was a pain, and certainly not something I want to tolerate over time.
This problem is nicely discussed A USB device may no longer work correctly after Windows Vista resumes from sleep or from hibernation I know MS gets blamed for lots of PC issues which sometimes are BIOS, 3rd party drivers, and unresolved PC architecture issues. This work around forces an HCI reset after sleep/hibernation, much like how removing and replacing a notebook to a docking station would do.
I expect this will evolve over time with more use of S3. New drivers, hotfixes, maybe BIOS... but for now this brute force workaround works and makes total sense. Hope this helps and spread the word!
The issue was USB wireless interface would not work after waking from S3. I was able to restore functionality by disabling the device and re-enabling (key part of diagnosis). That was a pain, and certainly not something I want to tolerate over time.
This problem is nicely discussed A USB device may no longer work correctly after Windows Vista resumes from sleep or from hibernation I know MS gets blamed for lots of PC issues which sometimes are BIOS, 3rd party drivers, and unresolved PC architecture issues. This work around forces an HCI reset after sleep/hibernation, much like how removing and replacing a notebook to a docking station would do.
I expect this will evolve over time with more use of S3. New drivers, hotfixes, maybe BIOS... but for now this brute force workaround works and makes total sense. Hope this helps and spread the word!