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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-08-02T12:11:42+00:00

    As mentioned on another thread, I installed the optional update KB4568831 which fixes the issue.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2020-08-02T19:44:13+00:00

    This process mysteriously appeared in my task manger after the latest update. I am having multiple sleep issues as well regardless of what power management settings I edit. one of my secondary hard drives is constantly going to sleep now as well. 55 times? I wish , I'm showing over 100 events when I ran that Powershell Command. 

    How can they constantly release bugged updates ? This is starting to feel like Asus Bios updates , updates to fix the updates ...

    Microsoft started to make money on cloud and it shows.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  3. Anonymous
    2020-06-02T15:33:14+00:00

    Check and see if there is any update running on Windows?

    Try run Windows Update and install all updates and restart your PC and see if problem persist?

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  4. Anonymous
    2020-08-03T13:01:24+00:00

    You may be onto something here.

    I likewise restarted the Windows Update service and the Execution hold in Powercfg went away.

    Then I decided to experiment.

    • I ran a manual check for updates. The MoUsoCoreWorker.exe was back in Powercfg.
    • When the update completed, it went away.
    • That seems to be normal.

    When I first hit the Settings | Windows Update dialog, the updater showed an error in checking for the update. I don't know if that's because I had restarted the service, or if it had in fact hit a network error and that held the service open.

    More experimenting to come...

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  5. 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