Win 10 not sleeping, again.

[Distinctly Average]

Seems every update something goes wrong with Windows. Once again my machine is not sleeping. The monitors turn off but the machine stays awake. I have tried resetting the power profile to default, set allow sleep on the disk drives and run powercfg - requests and everything shows as None. Anything else I can try?

[Mark Kaine]

Sleep function of win 10 is severely messed up and can slow a computer down massively, definitely recommend not to use it, same with 'hibernation'. 

 

But I guess this solution isn't satisfactory for you so just to be clear, there is a "sleep" button in your start menu and it does nothing, except turning off the monitors? 

 

[Distinctly Average]

35 minutes ago, Mark Kaine said:

Sleep function of win 10 is severely messed up and can slow a computer down massively, definitely recommend not to use it, same with 'hibernation'. 

 

But I guess this solution isn't satisfactory for you so just to be clear, there is a "sleep" button in your start menu and it does nothing, except turning off the monitors? 

 

Yep, just turns of monitors. In my case I often walk away from the machine and just rely on it going to sleep, or I will leave it running a task knowing that it will go to sleep when finished. I just want to get on with life while the machine is doing its task. So having sleep working as it should comes in handy.

[Distinctly Average]

Finally got this sorted. Took a bit of head scratching but eventually got there.

 

In the past I could simply check the power profiles in Power and Sleep settings. Occasionally in the advanced area something would stop the machine sleeping and resetting to defaults would cure it, then setting allow sleep on disk drives.

 

If that failed the next step was always to open a command window as admin and run powercfg -requests . Normally this would show anything stopping the machine from sleeping. Often in the past it has been an errant audio driver or windows update. The tool makes it quite obvious. Usually re-installing a driver or resetting a service fixes thing. In this case nothing showed, which is odd.

 

So my next step was to update the chipset drivers from the board maker (Gigabyte in this case) and I did the BIOS while I was at it. Still nothing. Finally I installed the AMD power profiles and voila, all was good again. Seems the last windows update messed something up and the AMD profile fixed it. I am sure I will be there again next time a big windows update hits.