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-12-01T18:43:01+00:00

    Reliably now, for the third or fourth month in a row, the Cumulative Update Preview for .NET Framework (today's was KB4586876) has caused MoUsoCoreWorker to hang and hold the machine awake.

    The KB4586853 Update Preview was sitting there as an optional update. I installed that, and then rebooted, and the .NET update just magically appeared, as it always does. Once that installs, MoUsoCoreWorker functions normally.

    Now I have to go through my entire house and unfreeze all the machines. Thanks a lot.

    There is something going on with the .NET previews. Fix it already, Microsoft.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-01T19:32:53+00:00

    This was fixed and now again it's broke! MS do you have any idea how much power this wastes??!!

    FIX IT and keep it FIXED!!!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-02T14:05:20+00:00

    Yup, the problem keeps returning. Sleep mode can't be relied on, so it's back to shutting down every time. The sleep mode option is more of a false hope now - like taking melatonin with caffeine.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-02T14:11:55+00:00

    This was fixed and now again it's broke! MS do you have any idea how much power this wastes??!!

    FIX IT and keep it FIXED!!!!

    Actually its never been fixed.  The problem has gone on for months.  MS sucks.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-03T01:33:17+00:00

    6 months later. It's officially ridiculous.

    The process is preventing machines form entering S states.

    If an update is found - whether optional or recommended - this process perpetually calls powercfg.

    There's already a timeclock on force-installing updates. Once that timeclock expires, this behavior might be excusable. But as previously mentioned, this behavior is omnipresent on all updates - irrespective of timeclock on the force-install.

    Was this answer helpful?

    0 comments