This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My computer (Windows 10, 64-bit Build 19041) is constantly waking up from sleep and then going back to sleep for a short time only to repeat the cycle. I ran sleep diagnostics on the Windows PowerShell as administrator i.e. powercfg /systemsleepdiagnostics. The report from yesterday (5/31/2020) indicates that my computer awoke from sleep 50-55 times during the course of the day until at about 8:00 p.m., I decided that it was better to fully shut down the computer rather than have these continued cycles. The common thread in all these awakenings from sleep is MoUSO Core Worker Process (MoUsoCoreWorker.exe).
- Power Requests
- \Device\HarddiskVolume5\Windows\System32\MoUsoCoreWorker.exe | START TIME | DURATION | TYPE | TOKEN | | --- | --- | --- | --- | | 2020-05-31T18:18:53 | 0:00:01 | Execution | 0xffff8389192ab2e0 |
This executable is a Microsoft programming element.
Why is this happening and what can I do to eliminate this totally annoying phenomena?
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.
As promised, just to feedback a couple of weeks later. The solution I outlined 10th November has worked for me. PC is now going into standby without fail as it always used to. A couple of days ago Windows version updated to 20H2 and standby is continuing to work fine.
the solution WAS : (its now different if you do a clean install with windows 10 version 20H2)
the "C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start" file is now replaced in version 20H2 by UpdateModelTask file
5 nights later after clean install of version 20H2 no awaking in sleep mode, like it did with version 2004 and older version without any modification
read this all before doing anything
with windows 10 home version 2004 :
stop the updater in C:\windows\system32\tasks\microsoft\windows\UpdateOrchestrator by doing these :
DO A COPY of "Universal Orchestrator Start" file to return to "normal" when you'll do the windows updates... store it where you will know to use it for when you'll do windows updates and only modify the the file kept in C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator
modify
file "Universal Orchestrator Start" in properties\security, add your user administrator name and check "full control" , disable inheritance in advance
in powershell as administrator,
Disable-ScheduledTask "\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start"
BUT
it stops all updatings
I forced an update that Windows seemed reluctant to install including 20H2 and KB4580364. A wee bit later and the confuser was sleeping soundly. Here's hoping. Thanks again for the prompt, Delphiwizard. I had sort of given up but all is well now in the land of nod.
This issue has recently started on my five year old PC. Running Windows 10 Pro 2004 19041.0 it has never previously had this issue.
Running powercfg /requests the only thing listed having power requests: [PROCESS] \Device\HarddiskVolume4\Windows\System32\MoUsoCoreWorker.exe USO Worker
Not sure of the relevance but did seem to coincide with installing:
2020-10 Cumulative Update Preview for.NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for X64 (KB4580419)
2020-10 Cumulative Update Preview for Windows 10 2004 x64-based systems (KB4580364)
Windows Update stated it was up to-date but MoUsoCoreWorker.exe USO Worker was consistently showing up.
I restarted the Windows Update service and re-ran Windows update and it offered me KB4486712, then stated it was up to-date.
However cycling through restarting the Windows Update service and re-running Windows update another four times, it offered me one by one KB4486680, KB4484397, KB4486710, KB4486720.
Windows Update now stating it is up to-date and MoUsoCoreWorker.exe has not shown up for a couple of days.
Will see how it goes but to me does appear to be some sort of issue with Windows Updates getting stuck. Will post an update after a couple of weeks.
tldr
The problem will be back as son as there is another update available.
This issue has recently started on my five year old PC. Running Windows 10 Pro 2004 19041.0 it has never previously had this issue.
Running powercfg /requests the only thing listed having power requests: [PROCESS] \Device\HarddiskVolume4\Windows\System32\MoUsoCoreWorker.exe USO Worker
Not sure of the relevance but did seem to coincide with installing:
2020-10 Cumulative Update Preview for.NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for X64 (KB4580419)
2020-10 Cumulative Update Preview for Windows 10 2004 x64-based systems (KB4580364)
Windows Update stated it was up to-date but MoUsoCoreWorker.exe USO Worker was consistently showing up.
I restarted the Windows Update service and re-ran Windows update and it offered me KB4486712, then stated it was up to-date.
However cycling through restarting the Windows Update service and re-running Windows update another four times, it offered me one by one KB4486680, KB4484397, KB4486710, KB4486720.
Windows Update now stating it is up to-date and MoUsoCoreWorker.exe has not shown up for a couple of days.
Will see how it goes but to me does appear to be some sort of issue with Windows Updates getting stuck. Will post an update after a couple of weeks.
