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-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.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-09-11T20:15:38+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-12T16:21:30+00:00

    I closed MoUsoCoreWorker.exe from taskmanager however I'm unsure if i've shutdown/restarted the computer with in that time.  I can say right now its not showing in the Command Prompt.  So first restart Windows Update Service then close MoUsoCoreWorker.exe from taskmanager.  Give Windows a restart and let us know if this solves your problem.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-02T14:01:15+00:00

    Same here. Happening monthly.

    This month it happened with "KB4576945 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10"

    It happened with another .NET update, KB4570721, last month.

    Killing MoUsoCoreWorker from taskmgr and rebooting, sometimes multiple times, gets the .NET update to appear in Windows Update and eventually install.

    Otherwise, it can't get past that update and MoUsoCoreWorker stays hung and continues to keep the computer awake.

    Here's the update history. The updates eventually took by doing the task kill reboot thing until they took.

    So it happened on 9/4 and 10/2 over this particular update.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-02T15:29:04+00:00

    Same here. Happening monthly.

    I concur, a lot of electricity is being wasted unnecessarily here. Can Microsoft please do something about this issue?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments