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
    2019-12-16T10:51:59+00:00

    Since a recent update a few weeks ago, my brand new laptop wakes up every night and also ignores all settings to shut down at certain battery levels.

    EVERY MORNING it is at 0% - which kills lithium batteries. Basically Microsoft has ruined the batteries on my new laptop, and I can't find any solution. It wakes from sleep, hibernate, AND Shut down.

    Every tutorial on the issue I've followed online ends in "greyed out" options, or my account doesn't have privileges.

    This is like class action lawsuit level incompetence from Microsoft.

    I've literally lost customers over the fact when I sit down at a specified meet time, my computer is 100% dead...

    Was this answer helpful?

    0 comments No comments
  2. 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

  3. Anonymous
    2019-11-21T01:24:18+00:00

    I hope these few tips solve the issue.

    But, I cannot imagine a "world class company" like Microsoft causes such discomfort for MILLIONS of people around the world: 

    the computers do not go to sleep after these wakeups, every night, for millions, causing CO2 footprint that is a DISGRACE.

    And.. MSFT never offered a proactive remedy for this??? We have to search and fight on our own, each user for herself/himself?

    **** & WTG, MSFT.  A pure DISGRACE!!!!

    "Help the Global Warming, proactively?" - which side are you on, MSFT?

    OFFENDED, INSULTED, BRUISED, CAUSED HARM, VIOLATED ... by MSFT.

    How or why they do such idiotic harm to users is beyond me.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-11-12T17:45:23+00:00

    Maybe it will help someone. I was having the same problem for some time and I finally resolved it.

    'powercfg /lastwake' was saying that Universal Orchestratro/Universal Orchestrator Start scheduled task was waking my PC at night but there was no such task defined in Task Scheduler so I couldn't disable it.

    At the same time 'powercfg /waketimers' was listing Universal Orchestrator/Backup Scan as the only wake timer defined.

    This must be a bug somewhere becuase what was actually waking my PC was not listed by 'powercfg /lastwake' nor by 'powercfg /waketimers'. 

    The root cause in my case was that after upgrade of NIC driver, power management option in NIC driver to 'allow this device to resume computer from standby', which was once manually disabled by me, got silently re-enabled. So newtork card was able to resume PC from sleep. But the option 'only allow Magic Packet to resume computer from sleep' did not get re-enabled. So any network packet (not just WOL packets) sent to my PC could wake it up and this led to this random wakeups at night.

    This however used to work properly once. That, is, I recall that in the past, when this option for network card was enabled, 'powercfg /waketimers' was listing network card as possible sources of wakeups and 'powercfg /lastwake' provided correct reason when computer woke up becuase of network card activity.

    This is not true anymore. Computer is waking up because there was a network packed sent to it but powercfg is no longer providing ocrrect ouptuts, they are only misleading....

    Was this answer helpful?

    0 comments No comments