When wakeing up from "Sleep" 30 sec. until active desktop.

I am using build #9926 with all updates to drivers and Win 10 TP. I have a system with 3 SSD's one for Win 7, Win 8.1 Pro and Win 10 TP. When putting the computer to sleep (S3) all goes well. When I try to wake up, using mouse or keyboard, the desktop screen pops right up. However, the mouse or keyboard actions on the desktop (clicking on a icon etc.) have no affect at all. The mouse cursor arrow can be moved around the desktop. When cursor is placed over the taskbar there is a blue rotating circle. This goes on for about 30 seconds or so before the mouse/keyboard becomes active and reacts to a click and becomes fully woken up. If I click on a icon before the 30 seconds is up the computer remembers those clicks and activates/opens the icon clicked. This does not happen in WIN 7 or Win 8.1 pro. I have the Intel 82597v Gigabyte Network adapter with driver #12 12 50.4 dated 11/17/14. This adapter/driver could be the problem as the network internet access icon in the tray show the computer is not connected until about the 30 second mark. One more thought, I don't think I had this problem with earlier builds. I realize that this is a preview build and there are bugs. Any suggestions will be appreciated.

Lee said:

Have a look in your Startup problems in "Start Manger" to determine what is coming up when exiting Sleep, and you could go into MSCONFIG and have a look at what services may be doing the same thing (coming out sleep). . .Good Luck

Thanks for the suggestion....I'll check it out.

usasma said:

Try the drivers from here: http://www.intel.com/support/network.../CS-032484.htm
It seems to be an older adapter, so it's possible that it's not going to be supported in Win10.
I'd try another NIC card - they're cheap and it never hurts to have a spare one at hand.

Also, be sure that you have the latest Intel drivers for the motherboard (chipset, MEI, SCT, RST, etc).

Thank you for the info. I downloaded and installed the Win 8 64 bit driver but it did not fix the problem. I'll check new NIC cards.