PC waking up by itself from sleep

I could eventaully make that , but not by SYSTEM but my user account with my password. I simply could not make the task with the SYSTEM account because of repeating error :/ - and solution made like that did not helped so today my computer ran from midnight to morning

Octopuss said:

I've found this thread by googling after noticing my PC woke up in the middle of the night and didn't even go back to sleep since.
I have a weird problem though.
EventLog says:
Wake Source: Timer - Windows will execute 'NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start' scheduled task that requested waking the computer.

BUT when I go to Task Scheduler, there's nothing like that inside.

I only have these:

So how am I supposed to change the properties of nonexistant task?

Also, even though I took ownership and replaced/added permissions to the physical task files, I am unable to change anything in the Task Scheduler, which is completely puzzling.
Damn piece of shit.

I had that same problem, if you don't mind the maintenance task running and just want it to be able to go to sleep afterwards you can try this:

Go to Start -> Type: "cmd" and right-click "run-as administrator" -> On the cmd line, type:

powercfg /requestsoverride SERVICE "Universal Orchestrator" EXECUTION

It tells the OS to ignore wake holds from that service. With Windows10 1909 my system would often sit awake with a wake hold from this task.

The actual maintenance tasks should have their own wake locks, so it shouldn't change maintenance, just allow it to go to sleep when done. Seems the task doesn't always clear it.

Hi - just wondering if anyone ever found a solution for this?

merkk said:

Hi - just wondering if anyone ever found a solution for this?

Post #33 (shown right before yours on my screen) described a solution I had not seen before. I'd tried most of them before just turning off all Wake Timers in advanced Power Settings.

Today I turned Wake Timers back on, used the Command Line with administrator privileges (hope it works):
powercfg /requestsoverride SERVICE "Universal Orchestrator" EXECUTION

i thought i found a solution using pstools to run task scheduler so i could set the Universal Orchestrator Start task so that it can not wake the pc - but unfortunately even though it appears like i was able to change that setting, as soon as i power down, that setting is set back to allow it to wake the pc.

This is seriously one of the stupidest damn things MS has done.

- - - Updated - - -

Think i might have found the solution - it involves using the group policy editor. You can find the solution here: https://answers.microsoft.com/en-us/...6-064092a6df6e Look for the post dated March 31st

It worked for me - at least for today anyhow. I put my pc to sleep a little while before the task was scheduled to run and it stayed asleep.

Hi all,

I have just registered for posting my ideas in this old thread in a hope that I can add something. Trying to be as clear and detailed as possible. NB: I'm an IT pro but not a Windows expert.

TL;DR I think this is a one time task that the user should allow to complete. Repeated waking up of the PC happens because the task was not able to complete even once.

Symptom: Company managed Windows 10 starts waking up from sleep, after an upgrade to 21H2, which may or may not be related. Didn't have the problem at all before. I had this like 2 or 3 times lately - I just went to the PC and powered it off without logging in because who wants to troubleshoot during the night. Poweroff took minutes.

The Event Viewer details were, in order:

1 - Information 2022. 08. 16. 0:08:34 Kernel-Power 131 (33): Firmware S3 times. ResumeCount: 2, FullResume: 1614, AverageResume: 1616
2 - Information 2022. 08. 16. 0:08:34 Kernel-Power 130 (33): Firmware S3 times. SuspendStart: 626364734, SuspendEnd: 626364778
3 - Information 2022. 08. 16. 0:08:38 Power-Troubleshooter 1 None: The system has returned from a low power state. Wake Source: Timer - Windows will execute 'NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Idle Start' scheduled task that requested waking the computer.

After reading this thread, I went to Task Scheduler: \Microsoft\Windows\UpdateOrchestrator and found this task there as expected:
Universal Orchestrator Start

But in the Triggers tab, it displayed 'One time', yet it didn't seem to have ever completed, presumably because I never actually let it complete. In the History tab there were no events whatsoever. So I just ran the task manually now (right click, Run or use the controls in the right hand pane). Eventually, in the History tab I could see an event that says 'Task completed'.

I will keep putting the PC to sleep as I did for years and will report if the issue surfaces again.

Gabor

- - - Updated - - -

gabor10 said:

TL;DR I think this is a one time task that the user should allow to complete. Repeated waking up of the PC happens because the task was not able to complete even once.

Update: The above did not work and this turned out the night after. Had the PC wake up again with the same event log lines as above. Continued research. So where I'm at is:

In Task Scheduler, \Microsoft\Windows\UpdateOrchestrator, there are several tasks. Ordering them by Last Run Time after the last wake up, it showed that the task "Schedule Retry Scan" ran last. Note that it was not named "Universal Orchestrator Idle Start" as per Event Viewer log - in fact, I don't even have a task named so. The Conditions tab in this task shows that the "Wake the computer to run this task" is indeed ticked. So this must be the culprit. In the event logs this looks like a task that collects and downloads updates. I have new updates ready to install.

When trying to modify this task (disable wake), it became apparent that it is managed by the corporate group policy - logically - similarly to updates in general. The task cannot be disabled or deleted either. It clearly says: "The user account you are operating under does not have permission to disable this task." This is the point where you could contact your admin or support if you think the policy would be changed upon your request. But I have found something else as well.

In Windows Power Options > active plan > Change advanced power settings > Sleep > Allow wake timers > Plugged in, I had "Important wake timers only" set.
This can be changed by the user to "Disabled" which - I hope - means that you are able to suppress whichever sheduled task to wake up the PC.

I'll keep you updated only if the above fails again.

PS. I believe it's normal and recommended to let the update task to do its job as designed, but I want control over Windows and cannot allow it wake my PC up for various reasons.