Windows 10: Universal Orchestrator Start wakes laptop, reliably leads to Windows hardware errors

After noticing hardware errors and Cortana/search errors appear in the Windows Reliability Monitor almost daily, I've finally tracked down the basic reason for it: almost every night, Universal Orchestrator Start wakes my laptop to search for updates, immediately after which I always get a windows hardware error and more often than not get Cortana search errors, too.


I thought this could be due to me undervolting my PC, but after turning off undervolting completely, it still happens, so that's not it.


I've temporarily circumvented this by not allowing the PC to have wake timers under Advanced Power Settings --> Sleep in the Control Panel, but that's not quite solving the problem, since I shouldn't get constant hardware errors when a wake timer occurs.


Here are some possibly relevant details. I can't find a minidump for the issue. Any help's appreciated. Thanks in advance!

• Running Windows 10 Pro 1909 on Lenovo X1 Extreme Gen 1 with an 8850H processor
• Here's the wake message that powercfg /sleepstudy gives that leads immediately to the hardware problem:
  Timer - Windows will execute 'NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start' scheduled task that requested waking the computer.
• Here's the hardware error output that happens after the wake:

Source

Windows

Summary

Hardware error

Date

‎5/‎13/‎2020 5:18 AM

Status

Report sent

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

Code: 141

Parameter 1: ffff9d824a4ba050

Parameter 2: fffff8016a10a270

Parameter 3: 0

Parameter 4: 0

OS version: 10_0_18363

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.18363.2.0.0.256.48

Locale ID: 1033

Extra information about the problem

Bucket ID: LKD_0x141_Tdr:6_IMAGE_igdkmd64.sys

Server information: 94c36dc9-d2db-401e-a1df-2c0150c3db58

• Here's the Search/Cortana error from Reliability Monitor:

Source

Search and Cortana application



Summary

Stopped responding and was closed



Date

‎5/‎13/‎2020 5:17 AM



Status

Report sent



Description

A problem caused this program to stop interacting with Windows.

Faulting Application Path: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe



Problem signature

Problem Event Name: MoAppHang

Package Full Name: Microsoft.Windows.Cortana_1.13.0.18362_neutral_neutral_cw5n1h2txyewy

Application Name: praid:CortanaUI

Application Version: 10.0.18362.752

Application Timestamp: 5e7049d9

Hang Signature: 73d0

Hang Type: 2097152

OS Version: 10.0.18363.2.0.0.256.48

Locale ID: 1033

Additional Hang Signature 1: 73d0f7954aa334999f1d4897ff24a3ff

Additional Hang Signature 2: 9f42

Additional Hang Signature 3: 9f42e976d7c4f2ca4d3b14f2959b1208

Additional Hang Signature 4: 73d0

Additional Hang Signature 5: 73d0f7954aa334999f1d4897ff24a3ff

Additional Hang Signature 6: 9f42

Additional Hang Signature 7: 9f42e976d7c4f2ca4d3b14f2959b1208



Extra information about the problem

Bucket ID: b5b17e2b1e695bdaabd10b323b0af197 2004395619523424663

:)

 

Task "Universal Orchestrator Start" keeps waking up my computer

Hello, I just want to prevent Update Orchestrator from waking up my computer. I've already gone into Task Manager with pstools and the following command

psexec.exe -i -s% windir% \ system32 \ mmc.exe / s taskschd.msc

In the "Universal Orchestrator Start" task, I have already cleared the "Wake the computer to run this task" checkbox on the "Condition" tab many times, but the computer continues to check this box.

I already checked many forums to get here, but I could not find any answer on how to stop the system checking this box again.

How can I get the system to not check the box again?

Thanks in advance.

Kind regards,

Adam

 

what process creates the task "NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start"?

hello,

in my home i have a computer that i always put in hibernate mode instead of turning it off.

from time to time my computer wakes up automatically at around 23:00 for few minutes and turnd off again.

(ans sometimes it doesn't turn off - then the computer still runs in the morning, when i get up)

and every time the computer is doing that, i wake up as well, because the initial power-on fan-test is very very noisy.

i was looking powercfg what the cause was of the last wake and it was always

"NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start".

but when i take a look to "NT TASK\Microsoft\Windows\UpdateOrchestrator\" in the task schedule, there is no

"Universal Orchestrator Start" anymore, that i could muten/prevent from turning on the computer next time.

it seems the taks deletes itself as soon it was rebooting the computer.

what process is creating "NT TASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start"?

for what is it good for?

is there a way to turn off creating that task?

i observed that issue more often in the last few days/week - was something changed in the last update (1909 / 2019-12)?

 

Updates are paused but Update Orchestrator keeps waking PC.

I normally do updates every few days but so it does not inconvenience me I do them then set them to be paused so the PC which is in my bedroom does not wake me at night. For the past few days even though its paused Update Orchestrator is waking my pc, but why? Should it not be disabled when Updates are Paused? I'm on 1903 for reference.

Here is my Powercfg -lastwake report:

Owner: [SERVICE] \Device\HarddiskVolume4\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.

I know you can murder the task and take system privileges from it to make you have to force it do updates but I only have my laptop doing that as if this happens to it in a bag that can be a very bad thing and used to happen till pausing was a thing.

Any steps I should take to fix this, for now I have changed my active hours to more when I will be on it at least.
Malcolm