Computer wakes from sleep automatically every night

Anonymous
2019-07-03T12:00:53+00:00

I put my computer to sleep before going to bed, but the signon screen is brightly lit every morning. Furthermore, when I launch Windows Update, it never seems to finish searching for new updates. In searching for a cause of the waking, I have come across the following potentially useful information. Any assistance will be greatly appreciated.

>powercfg -lastwake

Wake History Count - 1

Wake History [0]

  Wake Source Count - 1

  Wake Source [0]

    Type: Wake Timer

    Owner: [SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (SystemEventsBroker)

    Owner Supplied Reason: Windows will execute 'NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start' scheduled task that requested waking the computer.

***Modified title from: windows 10 wakes from sleep EVERY night and the screen stays on until morning***

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
Answer accepted by question author
Anonymous
2019-09-28T10:57:12+00:00

I think i found a fix that doesn't require downloading anything or complicated steps. 

It's worked for me so far.

1.  Go to: Control Panel\Hardware and Sound\Power Options\Edit Plan Settings (it may also be called Change plan settings)

     (you can alternatively just search for "Edit power plan" in the windows search bar)

  1. Click "change advanced power settings"

3. Go to "Sleep->Allow wake timers" and change the setting to Disable.

If this doesn't work, then using psexec like RichStevens2 suggested might be the way to go.

The directions i found on another forum was helpful:

"1. First go here to download PsTools. Extract it to a folder on your desktop. 

  1. Open Start and type cmd. Right-click the program and choose to run as administrator.
  2. Navigate to the folder where you extracted the tools by typing "cd C:\Users\Username\Desktop\Pstools", replace Username with your username and Pstools with the folder where you extracted the tools.
  3. When you have navigated to the correct folder, copy the following command without the quotes: "psexec.exe -i -s %windir%\system32\mmc.exe /s taskschd.msc".
  4. Open the command window and right click, choose paste. Press enter.
  5. Navigate to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator.
  6. Right click the task called Reboot and click on Disable.
  7. The task should now be disabled"

Hopefully one of these two options works for ya'll

Was this answer helpful?

200+ people found this answer helpful.
0 comments

86 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-05-09T16:10:01+00:00

    ADT_2020 didyou open up those highlighted items to see the details?

    Another useful command is powercfg /requests  That will tell you what is preventing sleep at the moment you run it. Run first thing when you find your computer unexpectedly awake.  I see the audio driver listed in your report. Perhaps that was preventing sleep?

    As an example, if I leave YouTube.TV active in a Chrome tab the computer will not sleep.

    powercfg /requests it will report this:

    EXECUTION:

    [PROCESS] \Device\HarddiskVolume5\Program Files (x86)\Google\Chrome\Application\chrome.exe

    Playing audio

    That's just one quick example. Regardless of the fact that Orchestrator is a maintenance process common to all Windows 10 installs waking up the system, the root cause of what is preventing sleep will vary considerably depending on each user's particular configuration, installed applications, and usage practices. It does take some effort to diagnose.

    Just curious - those of you who don't want your computer to wake up at night to run maintenance tasks - why bother leaving it on at the end of the day? Why not simply power off? What does leaving it on at night buy you if you're not letting Windows run disk optimization, defrag, updates, security scans, backups, etc. outside of working hours?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-08T18:08:21+00:00

    I did something like that - I forget what it was that ran a similar report and now I forget what I changed - but that didn't work. And I didn't disable Orchestrator update altogether, just had it run during the day instead. And yes, I did disable Cortona, per another blog.

    I ran the sleep diagnostics report as you had suggested and the few days that it hibernated successfully, there were no reds. The issue that caused it to wake (Power Request Red) ~ after midnight was this:

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-08T17:40:34+00:00

    I do not think it is the whole truth. My PC is not configured to go to sleep. I use it frequently and I just do not want it to be so. If I had to enable autosleep, it would have to be a really long timeout, like a couple of hours. When I stop using it, I used to manually hibernate it.

    If I configured it with such long timeout, that means that, when it gets woken up by UpdateOrchestrator at night, it would stay powered on until morning, which means I could very well hibernate it manually again then.

    The result is that now I just power it off rather hibernate, to block auto-wakeups.

    M$ certainly got broken something here and I recall it started to happen with 1903 update. Before that, even though I had auto-sleep disabled, it would wake up to check for updates and then go asleep again. It is not happening anymore since that update and it is what most folks here are experiencing since then I think.

    This automatic wakeups to perform updates have another side effect. My wife's laptop is actually configured to go to sleep automatically. So it wakes up to install updates, then reboots (if needed). But it is conifgured with BitLocker and the laptop does not have TPM so there's a boot password required. The effect is that rather to finish installing updates and go to sleep, it stays powered on awaiting for the boot password.

    I think most folks here need a way to disable these autowakeups which are broken since 1903 release and requires workarounds or fixes that impact other functionalities and are not easy to implement for lee experienced people.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-05-08T17:30:12+00:00

    Because powercfg must be run from an elevated command prompt.

    Was this answer helpful?

    0 comments