This problem happened to me two times already. Can confirm that sleep issue appears a week or so before I get next cycle of updates and then disappears when those updates are installed. mmdriley is spot on.
Mouso core worker process
![](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)
Anonymous
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?
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.
317 answers
Sort by: Newest
-
Anonymous
2020-09-11T20:15:38+00:00 -
Anonymous
2020-09-08T09:46:54+00:00 Just to add some details, to avoid folks diving into lost causes: this is a failure in Microsoft's flighting mechanism for updates.
To review: Microsoft no longer has any method of validating updates in the broader ecosystem except for, well, letting y'all install them. They watch to see if the update corrupts all your data and then let it roll out to 2%, 5%, 10%, etc.
Some updates are scarier (read: less tested) than others, so they roll them out more slowly.
When the currently-deployed Windows Update implementation hits one of these "better not install this yet" updates, it says: "I really want to help test this update, but I can't yet! Better pend on a no-action sleep while keeping the computer awake so I can install the update whenever Microsoft tells me it's ready." This why your laptop is burning its battery -- because Microsoft hasn't decided to make you a test subject yet for a particular update.
The most perverse part of this is that computers will waste more energy and stay awake longer when Microsoft releases a patch they're less confident in, and choose to deploy over a longer timeframe.
-
Anonymous
2020-09-07T17:24:21+00:00 My PC with this problem got an update and for now is fixed and enters sleep mode correctly. Hopefully it'll stick.
There's nothing listed with the "powercfg /requests” command.
-
Anonymous
2020-09-06T18:13:42+00:00 Since a couple of days, I have this same problem and when installing KB4568831, the system says that this patch is not applicable for this system.
Windows 10 version: 2004
OS Build: 19041.450
@microsoft, when is this being solved, because now my computer never goes to sleep.
-
Anonymous
2020-09-06T13:22:08+00:00 Same here, same update number too, only came available after stopping and restarting the Windows update service. Was preparing for another S3 battle as per the last 10 years but hopefully all OK now.
Interesting. So the consensus is that updates "stuck" in the background waiting to be installed are the cause of this.