For those who still complain about the problem causing lost work, use one of these current solutions mentioned on this thread:
- Use hibernate, not Sleep, or use sleep for less than 1 hour
- Get the new driver
A small 'nit' - neither are solutions - just temporary hacks / workarounds. While they appear to work for some we need Microsoft to finds a solution that works for everyone.
All together now..."Come on Microsoft, get yer finger out! and fix this one"
A new driver isn't a temporary hack / workaround. It's an update from the manufacturer (Intel) to correct problems in an earlier release. In this instance, the new driver hasn't been incorporated into updates from MS yet. I'm sure they have their reasons.
Maybe they want to thoroughly test it first to ensure it doesn't create other problems. Or maybe they don't want to release it if it only fixes the issue for 90% of the users, and they want 100%. Or maybe they're just lazy. ; )
I know everyone is PO'd at MS, demanding a fix, with some even resorting to using the strongest tool in our arsenal - ALL CAPS - to make their frustration known. As someone who's worked in hardware/software dev (many years ago when things were much simpler)
I know this is a complex issue to hunt down and destroy. The SP4 packs a lot of tech into a small package, including a new OS.
I got mine on 12/26, and had a lot of wake from sleep issues and a couple freeze ups. I installed the Intel .4352 driver on 1/1 and reset the Windows power settings back to default. Aside from occasionally using Ctrl-Alt-Del to wake up my screen, it's
been golden. No need for hard power down anymore. One freeze up over the last 2 weeks. Progress.
For those that the .4352 driver hasn't helped, you have my sympathy.