Windows 10 won't go to sleep after recent fall update

Anonymous
2018-01-16T23:07:44+00:00

Have checked there are no active wake timers Turned off wake via Ethernet and all drivers/BIOS seem up to date. Any suggestion as to why this is happening and is this a known bug requiring a patch? Also via powercfg no application are preventing sleep

*Modified title for accuracy*

*Original title: Desktop Computer won't go to sleep after recent fall update the PC will close the screen but immediately go to log on screen*

Windows for home | Windows 10 | Sleep and Power on, off

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2018-06-08T15:28:31+00:00

I too had a similar issue. I'm posting because this thread is one of the top results Google gives for Windows 10 sleep problems.

The solution that worked for two computers I had that were not sleeping was as follows:

  • Run an admin command prompt
  • powercfg -requests
    • This command lists all processes or services currently running that are preventing the computer from sleeping. The list is helpfully broken down by categories. One of my affected computers had sleep blocked by the IncrediBuild component of Visual Studio, the other by a different TSR program.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

76 additional answers

Sort by: Oldest
  1. Anonymous
    2019-11-19T21:19:20+00:00

    I too had a similar issue. I'm posting because this thread is one of the top results Google gives for Windows 10 sleep problems.

    The solution that worked for two computers I had that were not sleeping was as follows:

    • Run an admin command prompt
    • powercfg -requests
      • This command lists all processes or services currently running that are preventing the computer from sleeping. The list is helpfully broken down by categories. One of my affected computers had sleep blocked by the IncrediBuild component of Visual Studio, the other by a different TSR program.

    Thank you for your post. 

    This has been driving me nuts and every resolution simple says to fix the power management setting which is NOT the issue. 

    This command revealed that it was Intel's Turbo Boost 3.0 technology program.    I attempted to "disable" it, but it did not help.   It had to be uninstalled completely.  

    Edit: Apparently this program keeps reinstalling on it's own without my permission.  

    here is a fix I found: 

    https://www.58bits.com/blog/2018/04/04/intelr-turbo-boost-max-30-technology-application-service-preventing-windows-sleeping  

    Edit2: The previous edit, ended up not permanently working after all because you do not have permission to change or modify the Task Scheduler, and despite disabling from any other means, Intel's Turbo Boost 3.0 Technology keeps reverting back after a windows update takes place despite my best attempts to stop it from waking the computer. 

    [SYSTEM:

    [SERVICE] \Device\HarddiskVolume4\Windows\System32\svchost.exe (Schedule)

    Windows will execute '\Intel(R) Turbo Boost Max 3.0 Technology Application Launcher' scheduled task that requested waking the computer.]  

    The Actual FIX:

    I had to go to C:\Windows\System32\Tasks\Intel(R) Turbo Boost Max 3.0 Technology Application Launcher open that in notepad and change "<Enabled>true</Enabled>"   to false anywhere I saw it,   I also attempted to change wake to run to false, but that alone did not seem to work for me.  

    I then had to go to C:\Windows\System32\Tasks_Migrated\Intel(R) Turbo Boost Max 3.0 Technology Application Launcher and also change those "Enabled" values to false.  

    Then in the lower right hand corner, task bar, click the "^" and find Intel(R) Turbo Boost Max 3.0 Technology, right click it, and select "disable"

    Then in the start menu bar, type: msconfig go to "startup" search for the Intel(R) Turbo Boost Max 3.0 Technology Application and disable it there also, then save and restart. 

    I have not had a windows update as of doing this, but I will update if it reverts back again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-12-01T21:33:15+00:00

    Yes! This is solution for 80% of this problem. Also solution for my PC and for my laptop. Just, instead to look the driver on intel official, i suggest to look it at your motherboard web page.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2020-01-06T16:55:02+00:00

    Have checked there are no active wake timers Turned off wake via Ethernet and all drivers/BIOS seem up to date. Any suggestion as to why this is happening and is this a known bug requiring a patch? Also via powercfg no application are preventing sleep

    *Modified title for accuracy*

    *Original title: Desktop Computer won't go to sleep after recent fall update the PC will close the screen but immediately go to log on screen*

    I had similar issue but i rectified it because i knew why this is happening. Just came here to help some people out.

    This problem occurred to me very recently after i started using "windows 10 hotspot". I triedswitching off this hotspot before pressing the sleep button, and it worked.

    So, this hotspot is not letting the computer sleep. It doesn't want to disconnect users who are connected to computer via hotspot.

    I think you can still make your computer sleep while it is actively using hotspot. You can follow some of the suggestions given by some people in the above discussions. => going to power options, etc...

    If you're not using "windows 10 hotspot" but still facing this issue then there must be something that your system is giving priority to, over "sleep". Find that out.

    Was this answer helpful?

    0 comments No comments