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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-13T18:22:34+00:00

    After the Aug 11 updates (2nd Tuesday monthly), the MoUsoCoreWorker.exe process is no longer showing up under powercfg /requests.  And, if I put my computer into Sleep mode, it stays that way.  But, it still will not GO to sleep after xx minutes idle.  I just tried the KB4568831 fix, but I get a message: This update is not applicable to your computer.

    Update - Aug 18, 2020

    I discovered that when I unplug all USB A/V devices, the computer goes to sleep as expected. With those devices plugged in, powercfg /requests always shows their drivers as active.  This is new behaviour which began with Feature Update 2004.

    I tried (as someone in this thread suggested) powercfg /override, but that did not work for me.  I have to physically unplug the USB devices - really annoying.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-08-14T06:44:15+00:00

    I'd like to update that I had tried the KB4568831 patch prior to August 11's Patch Tuesday with no effect (computer would not sleep by itself, nor stay asleep when manually done). MoUsoCoreWorker.exe continued to show in powercfg /requests .

    But after 3 days since August 11's cumulative patch, my computer has slept and stayed asleep by itself.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-17T18:03:39+00:00

    Sorry to burst all your bubbles but my computer is updated and it still won't sleep and MoUsoCoreWorker.exe is the culprit.

    My other computers never had the issue so it is not effecting everything.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-08-21T09:31:57+00:00

    Should I allow it? I am not so sure if this is good since it's an executable file.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-29T11:43:01+00:00

    I have automatic updates disabled in Group Policies. On August 20 I checked for updates and applied them. Ever since then the system would not go to sleep at the proper idle time interval.

    powercfg requests revealed:

    EXECUTION:

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

    USO Worker

    Update status showed no updates pending and all updates installed completely. Stopping in starting Windows Update Service did not stop the request.

    Issuing the command:

    powercfg /requestsoverride process mousocoreworker.exe execution

    would allow system to once again sleep at idle timeout. However powercfg still showed the request.

    I then ran the Update Troubleshooter which reported no problems, nothing to fix.

    I shutdown the system. Waited a few minutes and restarted.

    powercfg requests showed the request was gone and has remained gone after several restart.

    It appears Update Troubleshooter stopped MoUsoCoreWorker.exe perhaps in combination with powercfg /requestsoverride.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments