I have a new Windows 7 Home Premium X64 configuration with an intermittent problem that I have been unable to resolve. When the PC is awakened from Standby (not Hibernation) the PC will not open any application or Explorer window for 30 seconds (round circular wait indicator). It makes no difference if the PC goes into Standby via time-out or through an explicit command (%windir%\system32\rundll32.exe powrprof.dll,SetSuspendState). During the Standby wait period I can pop-up the Start menu. After each wait event I have looked for an Event Viewer message that indicates a 30000 ms delay, but have found none. I then clear all the event logs before testing again. I have all current MS updates and device drivers. I am using a current AV program and have checked for spyware/malware. The hardware configuration is unchanged and consistent. This is a clean install, not an upgrade. Any help would be appreciated. Thanks, RB.

I would suspect something network related first-adapter drivers-reconnection difficulties-shared network files-mapped drives Disable the network adapters and test a sleep and awake cycle Look for the most recent drivers for all of the hardware, like manufacturer specific drivers for 64-bit -devices and motherboard chipset Is the BIOS updated to the most recent from the manufacturer?-also check the BIOS settings \options for sleep modes-let Windows\not the BIOS control it- Plug and PLay OS=Yes(enabled) Perhaps the security AV software views the wake as a boot and scans-temporarily disable protection and test a sleep\wake cycle You could check other software by using msconfig and disabling non-Microsoft services and testing a sleep\wake cycle. Then 50\50 the nons back on until the delay happens again. It sounds like hybrid sleep- where recovery is happening from a drive-like a hibernate-but Win 7 likes to sleep or hibernate-Vista was the hybrid user

Sorry that it took a while for me to reply. Some other things went south in the configuration over the weekend. First was an updated Realtek NIC driver that manifested in video driver errors; the video errors went away when I dropped back to an earlier NIC driver. I then decided to take another look at the BIOS settings as you suggested and switched from S1to S3. When I did that I started getting scary "... corrupted memory across the previous system power transition .." event messages. I found that if I turned off the NIC IPv6 the error did not occur again (noted that others had the same experience). I downloaded the MS "Firmware Corruption of Memory During Sleep Transitions" doc - but haven't had time to read it yet (not sure that I would understand it anyway). S3 seems to work OK so far. The keyboard will now not wake the system - but the mouse still wakes just fine. Since the problem was intermittent, and testing specific other solutions is way time consuming - I think I'll declace victory for now and hope for the best. Thanks

First was an updated Realtek NIC driver that manifested in video driver errors; the video errors went away when I dropped back to an earlier NIC driver. You should not have to disable IPv6. Try to find a proper Windows 7 driver for the NIC. Windows update should find it. Re-enable IPv6. Windows 7 uses it for intra-net security when it can. You have forced the S3 or sleep to be used instead of the S1, which is why the keyboard is being powered off. It sounds like a thorough review for specific Windows 7 64-bit drivers would be in order. Be sure that you have the latest BIOS available for the mainboard. Good luck and post any updates!