Windows 10: Windows 10 machine will not sleep automatically

I've tried every step out there for trying to get my pc to sleep automatically.. nothing has worked.

I've tried disabling network adapters.. i've tried looking at lastwake for powercfg and it usually shows 0, though /requests will show a remote file is accessing the machine.. or nvidia audio has something open.

So I then pulled every USB from the PC.. same difference.. i then tried disabling virtually everything i could think of in device manager, usb's included.. no luck.

I also went through task manager processes and killed pretty much everything.. no luck.. i tried going in services and stopping every non microsoft service.. no luck.

Here is the interesting part.. if i boot into another partition where i have a clean creators update.. it sleeps (all drivers installed, except oculus ones, and yeah i tried disabling/unpluggin oculus devices).

So it clearly isnt the hardware.. something software wise is a bit screwed up.. i've tried looking at the energy report to see a culprit, not much there to go on.

I tried setting wake timers to disabled.. usb selective state to disabled.. you name it.

Any thoughts or suggestions out there?

Thanks in advance

:)

 

Windows 10 Won't Sleep Automatically

Just a little background. I'm an IT professional & developer and have my own Windows Active Directory domain at home. I have two machines now running Windows 10 Professional Creators Update. The systems work fine sleeping by themselves
until I connect to them via RDP. Once I connect via RDP they will never automatically sleep even after I've disconnected. I've run powercfg /requests and on both machines it shows this:

EXECUTION:

[SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (TermService)

Remote Desktop Services Power Request

I see lots of people wanting to keep a system from sleeping but how can I prevent Terminal Services from preventing the system from sleeping automatically? Why is Terminal Services preventing sleep?

 

windows 10 will not go to sleep automatically

Thanks for your comments. For clarity, Regarding the display driver, my driver is newer than that on Dell's website. Should I revert to an older driver? And would you do the norton uninstall first and try that, or explore the video driver first?

 

Hello Mark, *Smile

If you haven't already, you might see if turning off Fast Startup may help. It can sometimes cause shutdown and sleep issues.

*Arrow Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

 

I can give that a try, though like i said, on my "clean" partition of win10, i dont think i have the issue, so not sure it would matter.

I do get the srvnet driver (remote file open) message a bit.. most of the time non specific and still there even after killing the network connection/disabling.. i think something on the machine is causing this.. however.. despite this..
when i do kill it (not sure how i did one time.. reran the /requests and i saw nothing listed.. the pc still wouldnt sleep and no wakelocks for the count either.. very strange.

 

View Event ID 1 and 42 for Wake and Sleep
"They are Event 1 and Event 42 (wake and sleep, respectively).
Open the Event Viewer and expand "Windows Logs" then click on the 'System' event log.
Right-click, and then choose "Filter Current Log".
Input the event id 1 and 42 number into input box above the "Task category" input box.
In the "Event sources" window, click the drop-down and put a check-mark beside "Power-Troubleshooter" and "Kernel-Power" and then click "OK.
You will see listing of wake & sleep events and look at the the "General" tab at the very bottom for each Event ID 1 for wake events the wake source will be shown it will be display at the "Wake Source: " entry.

*Arrow See Wake Source in Windows 10 Performance Maintenance Tutorials

 

This is a good tip.. although i have nothing showing for today and i've attempted sleep (by timeout) a few times, oddly.

For the ones that have shown up in days past.. its either the network adapter or "unknown".

 

When I've had this sort of issue I've just gone old school and added a bat file to my start-up folder

WakeInfo.bat is a simple one

Just contains a basic call to the standard function when run ...

Code: MD c:\wakelogs powercfg -lastwake >>c:\wakelogs\Wakeup.Log[/quote] just manually check c:\wakelogs\Wakeup.Log after each incident and see what shows up, it's simplicity often shows more than the logs which are filled using a more complex system, no guarantees but the fact that it runs every boot it will sometimes catch what the logs miss

You can simply delete the log file and it will be recreated when next run - if left it will be added to and some form of pattern may emerge

 

just manually check c:\wakelogs\Wakeup.Log after each incident and see what shows up, it's simplicity often shows more than the logs which are filled using a more complex system, no guarantees but the fact that it runs every boot it will sometimes catch what the logs miss

You can simply delete the log file and it will be recreated when next run - if left it will be added to and some form of pattern may emerge[/quote] Thanks.. that seems to generate a wakelock count only.. and only if its run at startup.. not sure it would help see what is causing it to not sleep.. at least this is what shows when manually run for me?

 

It may need running in elevated mode in Win 10, which would need a start-up scheduled task to run the bat file Create Elevated Shortcut without UAC prompt in Windows 10 Customization Tutorials is the way to do this..

there is a full systemised write up here for troubleshooting issues where, like yourself, the system does not appear to catch the issue ... How to Prevent Your Computer From Waking Up Accidentally

As you mentioned that the network adaptor has been mentioned you may want to check the options for disabling the Wake on LAN option which can cause issues ( only if you are not using the WOL for it's designed purpose)

Win 10 does have a number of it's own tasks that run at various times and some, or should I say most, are set to wake the system if needed.

There are sometimes Bios settings relating to sleep system used - you may want to check with your Motherboard manual and see if you have these available and try different choices and see if that can help

 

Even elevated it still really only shows a wake count which is always 0 on my system.

I've tried disabling the network adapter (as well as a ton of other adapters).. along with most of the non essential services .. same difference.. maybe ill look into the bios, but i'm still skeptical, again, since it works fine when booted to my other clean win10 creators partition.

 

I decided to work around this using a scheduled task that fires off sleep mode via a batch file after so many minutes.. largely this works with a few issues..

I set the idle timer at 50 minutes.. here is the strange part.. if i come to the computer.. wake it up.. generally after i let it sit for about 10 minutes after that, it then decides to sleep, firing off the scheduled task.. i cant figure out why.. i wish i could see some sort of idle timer going to see if it somehow thought it was at 50 minutes and it wasnt.. or maybe the timer isnt resetting.. unsure

 

Applications, services and drivers can prevent sleep by setting the thread execution state. https://msdn.microsoft.com/en-us/lib...or=-2147217396

You can see if something is preventing sleep from an elevated command prompt by typing powercfg /requestsoverride If all you see is [SERVICE]

[PROCESS]

[DRIVER]

Then nothing is presently resetting the sleep timer.

 

I do see one thing.. i had this before, i thought i briefly fixed by either disabling it or switching the default audio device.. however.. even with the device disabled in dev manager it still shows up, though it says away mode (i think i forced it to get around this, but still doesnt work to go to sleep)


[DRIVER]High Definition Audio Device SYSTEM AWAYMODE
NVIDIA SYSTEMNVIDIA High Definition Audio SYSTEMHDAUDIO\FUNC_01&VEN_10DE&DEV_0083&SUBSYS_38426288&REV_1001\5&2a63c883&0&0001 SYSTEM

 

Away mode is (If I recall Correctly), related to a short lived mode to prevent early Media systems from entering sleep mode when used unattended ( so that the did not sleep in the middle of a movie Etc.) - you may have some software running in the background that is calling this routine which is then waking the system

How to disable away mode? Solved - Windows 7 Help Forums is an old thread that deals with this - It may give you a start point