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.
I noticed this after a bought a new mouse and keyboard. I chalked it up to my wake on USB setup in my bios. The keyboard is backlit and it is much more sensitive than my old keyboard. After reading the thread I see that KB4568831 may be a piece of the puzzle.
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
As I mentioned in my post of the 10th Nov it does appear to be some sort of issue with Windows Updates getting stuck and I agree it entirely makes sense that it will keep trying to get recommended/optional updates with the unfortunate consequence of waking windows from sleep.
Going through the steps I mentioned in my post of the 10th Nov, has resulted in my PC going into standby without fail since, as it always used to. My PC has received updates in the meantime without further problem and I report back again in early Jan, given others have suggested the issue might return at some stage.
I suspect there are several different flavours of this issue within this thread, but hopefully at least some can be fixed by getting stuck updates downloaded as I did.
I do backup my PC image using Acronis to a NAS regularly so do not have the concern that stopping/starting the WU service would cause windows update to fail for whatever reason; it's only dependency is RPC. Stopping/starting services is a common practice when troubleshooting issues. I note that Microsoft introduced Windows Update Medic Service (WaaSMedicSVC) in Windows 10 circa Oct20. The entire purpose of this service is to fix any damages suffered by the Windows Update components.
R. Hanson 690 mentioned problems after installing the KB4586853 update Preview and I would comment that unless fixing a specific issue that a user has encountered, it is not really necessary to install these preview patches as they are issued as part of the mandatory Patch Tuesday release further down the line. I noticed that my problem might have occurred after installing KB4580364 (a different preview patch).
It would be interesting to get confirmation that users with the Windows 10 20H2 update and Windows Update Medic Service installed also see the issue?
While everybody who posted on this thread agrees the behavior is undeniably flawed, making the assumption that it's a failure rather than by design seems unlikely. This issue has persisted for over 6 months without even an iota of acknowledgement on Microsoft's part.
The process only continues calling when there's an uninstalled Recommended or Optional Update.
Uninstalled Driver Updates are not subject to perpetual powercfg request.
At this point, it stands to reason the the process is functioning as intended.
Scripting can never be a solution to this problem. This is a failure of an integral part of the OS.
