Sleep is often more a problem with device manufacturers and the Windows drivers they release--it's not really a "Windows" problem, per se. It becomes especially problematic in laptops which sacrifice everything on the altar of power conservation for battery life, and in which 2nd-tier components and drivers are often used (and rarely updated), as well. The problem with devices and their drivers isn't so much the "going to sleep"...it's the "waking up" that hurts...
I disable both sleep and hibernation system-wide and have done so for years...with the exception that I generally have no trouble with monitors "sleeping" as they generally wake quickly and without complaint. People have to watch disconnecting their hard drives, their PCIe slots, and etc. as although all of that makes sense for battery life conservation theoretically, what good does that do if your machine refuses to wake? I don't use laptops of any description these days except when I'm forced to, but I find that simply setting my cpu and gpu to throttle way down when I don't need the power is more than sufficient for me (my cpu is set to drop to 10% of full speed and ramp up the power on demand only as needed, and my GPU is automatically set to do about the same thing itself.) Things stay cool when they should be and power is conserved when it makes sense--and ramp up on demand is perfect and never causes me problems. (I think Intel calls it "Speed Step" and AMD calls it "Cool 'n Quiet," for their cpus.) Best of all--no problems ever with "sleep" because when it never sleeps it never has to wake up... My boxes sleep every day *only* when I shut them down.
I just tested auto sleep on the Win 10 VM and it worked.
I set it to 1 minute for a quick test.
I changed it 30 minutes and will see how it works the next few days.
I really don't see much need for auto sleep on a VM as the PC will still be running because of Host activity...
But, testing it, it didn't cause any issues going to sleep or waking up so I'll play with auto sleep and see if it works.
In VMware it puts the machine into "suspended" state.
I like sleep and hibernate and it works for me on Win 7 and Win 8.1.1.
I did have sleep issues because of srvnet requests but overrides fixed that issue.
As far as Windows Defender definition updates, in Win 7 MSE and Win 8.x WD a scheduled task can be created to automatically update the definitions.
I assume this would work in Win 10, but haven't set up a task and tested it myself.
Not sure if such a task would help, if definition updates are causing a sleep issue ???
My problem is not Definition updates. Any update registers a power request and this never gets released. I did a manual update which gave a request svchost.exe (ProfSvc). Any of these execution requests stops sleep.
I tried your override and see in requestsoverride:-
The override doesn't work as it won't sleep, regardless.
What is it that folks don't understand about win 10. . .it is a tech preview. . .there are going to be problems, albeit I have not had the problem you are talking about on any Windows OS. Also there is the shut down method (it does work).
What is it about tech preview that you don't understand? Why do you think MS put this out approx 9 mths before release?
What would have been the point unless they were looking for feedback from 'ordinary' users? Why did they include a Feedback app do you think?
And why would we care if you shutdown your system? That's going to help MS debug the OS, isn't it.
I CAN definitely indicate, however, that the problems @linw is reporting as the causation for his sleep problem on Win10b is not the same issue causing the sleep problem on my Win8.1 install...
Last edited by Gork; 06 Oct 2014 at 04:34.
True, Gork, this 10 problem is not like the 8.1 one.
And thank goodness for that since, as has already been said, the cause you're reporting for Win10b at least seems easily staked out for a fix!