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 No 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 No comments

86 additional answers

Sort by: Newest
  1. Anonymous
    2020-02-29T01:25:52+00:00

    Well, it's a nice suggestion. When I run powercfg/requests, I did get all "None" except

    EXECUTION:

    [SERVICE] \Device\HarddiskVolume2\Windows\System32\svchost.exe (UsoSvc)

    Universal Orchestrator

    Orchestrator. Go figure. (For effect, say "Orchestrator" like Seinfeld said "Newman".)

    > Orchestrator and other tasks such as backups needto run periodically.

    > Doing so at night is preferred so as not to interfere with daytime work.

    1. Windows Update was introduced with Windows 98 and no version has ever had to wake up my laptop at 2 in the morning!
    2. And it's not as if the update service is so heavyweight.
    3. Again, why does usoft think they know better than me about when to do updates on my computer? Give me the option to specify when updates should occur!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-02-28T22:51:40+00:00

    For the past few months I found my computer awake in the morning even though I had put it to sleep when finished working on it the previous day. Running Powercfg /lastwake revealed Update Orchestrator as the task that woke the computer. However that is not a problem!

    While the many solutions presented in this forum and across the internet focus on preventing Orchestrator from waking the computer, I don't see that as a problem that needs fixing.

    Orchestrator and other tasks such as backups need to run periodically. Doing so at night is preferred so as not to interfere with daytime work. The Orchestrator task on my system was showing a last run time of 11:41 PM each day. I also have a backup that runs at 2:00 AM once per week. My assumption was that both of these tasks would wake the computer, do their job and then the computer would go back to sleep per the power settings. This was clearly not happening in recent months.

    The real problem is the computer was not going back to sleep after the wake event.

    Powercfg /lastwake only tells us what last woke the computer. It does not tell us what prevented it from sleep.  To determine that...

      Launch a command prompt with admin privileges.

      Run powercfg /requests

    You'll see 6 categories. You want to have None under each. If you see an application listed, you may need to take some action in the app's settings or simply uninstall if it is not needed. 

    In my case, MiniTool ShadowMaker was listed. I had previously installed that to try it out, but had no need to continue using it. I uninstalled it and ran powercfg /requeststo verify there are now no applications listed.

    Since doing that, my computer is always in sleep mode when I check it in the morning. It still wakes up at night as it should for maintenance tasks and backups and then goes to sleep per the Power Plan. Which is what I want it to do.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-02-11T04:05:56+00:00

    I just moved to Windows 10 after spending 7 years happily on Win7.  My new machine has Version 1909 and, while it will go to sleep fine, is always awake in the morning.  Asking powercfg what happened points to UpdateOrchestrator:

    Wake Source [0]

        Type: Wake Timer

        Owner: [SERVICE] \Device\HarddiskVolume4\

    Owner Supplied Reason: Windows will execute 'NT TASK\Microsoft\Windows\

    Universal Orchestrator Start' scheduled task that requested waking the computer.

    The machine is "up" in the morning and, oddly, leaves the monitor on with no screensaver enabled.  I don't really mind the wake event, but Universal Orchestrator Update seems to be leaving the machine in an unusual state -- incapable of idling.

    This misadventure, although slight for me since the desktop is always plugged in, and the lack of end user control afforded in the service scheduling for Universal Orchestra seems to be an unfortunately excellent example of the lack of control that kept me on Windows 7 for so long!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-01-19T17:01:23+00:00

    Yeah, from what I can tell UpdateOrchestratorStart is a "one-time only" task created on-the-fly.

    I've done two things recently and my machine hasn't woken up in the past two weeks. (Note though that my laptop had been quiescent in this regard for 2-3 months then this UpdateOrchestratorStart task started running at 2 in the morning):

    1. A previous poster said to make sure you've turned off all wake timers. I had left mine at "Important wake timers only" but now I've set it to "Disabled": Control Panel - Power Options - Change Plan Settings next to your selected option - Change advanced power settings - Allow wake timers - Disable both On battery and Plugged in.
    2. I changed the "active hours" of my computer to the middle of the night so that if Windows decides to update my machine, it's doing it during the day when my machine is already on: Start button - Settings button - Update & Security - Windows Update - Change active hours. I set mine from 5 pm to 9 am.

    Obvs. it would be so easy for usoft to allow me to set the time it checks for updates, but somehow, someone in Seattle decided they know it's best to check for updates at gawdawful hours and have no problem waking up my laptop to do so... for a 1 meg update to the antivirus definitions.

    Was this answer helpful?

    0 comments No comments