Mouso core worker process

Anonymous
2020-06-02T04:20:14+00:00

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.

0 comments

317 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-02-22T09:56:58+00:00

    I installed the optional KB4023057 yesterday which should have resolved the issue yet the process continues to prevent my computer from sleeping. This is a new development.

    Even worse, I have just checked and KB4023057 installed on my PC the day before it's inability to sleep problems returned. I'm not a great believer in coincidences so have rolled back to an Acronis backup 14/02/21 and paused updates for 7 days and am guessing PC will sleep ok. It has been sleeping fine since December (powercfg -requests no longer shows anything).

    Unfortunately it looks like KB4023057 is now being pushed out as mandatary it's not an optional update. Once I have confirmed PC is sleeping again, I will let KB4023057 install and report back.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-22T04:10:05+00:00

    I installed the optional KB4023057 yesterday which should have resolved the issue yet the process continues to prevent my computer from sleeping. This is a new development.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-21T17:48:22+00:00

    As previous users have noted, the culprit is usually Windows Update. CMD "powercfg -requests" shows this to be the only issue:

    EXECUTION:

    [PROCESS] \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe

    USO Worker

    Before fixing it, Windows Update show no updates in the queue, but restarting the Update service then shows there is an update ready to download. Today it was the Adobe Flash removal tool, but previously there were other Quality updates stuck in the pipeline.

    A constant issue since "Feature update to Windows 10, version 20H2".

    Microsoft...PLEASE FIX!

    Same with me. Flash removal tool this time. Usually, it's the previews for .NET that gum up the works. I wish MS employees read this board. My feedback report is "MoUsoCoreWorker.exe holding 3 machines awake when optional .NET update comes out" on Feedback hub. Please upvote and post your own.

    In the meantime, stopping and restarting the Windows Update service, and then clicking retry in the Settings app always works for me as a workaround, but it will install any optional update without asking in resolving the issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-21T16:20:38+00:00

    Back again, restarting the Windows Update service is still the least invasive fix, so I did that.

    21H1 is on the way, we can only hope it fixes this.

    Except when it wrecks Windows to the point you have to do a repair install like I did. Not worth it.

    I had WU install the current update and the computer still doesn't sleep.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-21T16:11:46+00:00

    Back again, restarting the Windows Update service is still the least invasive fix, so I did that.

    21H1 is on the way, we can only hope it fixes this.

    Was this answer helpful?

    0 comments