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-10-03T13:39:10+00:00

    Hi,

    My (currently working but who knows...) solution is to create a task (.cmd file) that is executed at each logon (using the Task Scheduler) and that contains these simple lines :

    @ECHO OFF

    powercfg -requestsoverride PROCESS "MoUsoCoreWorker.exe" SYSTEM

    To make things easier and cleaner, this .cmd file can be converted to an .exe file using the Bat to Exe Converter utility (https://www.majorgeeks.com/files/details/bat_to_exe_converter.html). This will allow to launch the command transparently.

    Anyway, this is an irritating bug because no one can say when MoUsoCoreWorker.exe will re-appear and post a new request. It's obviously related to recently installed or pending Windows updates but I can't find any pattern. MoUsoCoreWorker.exe is launched each time you check Windows Update in the system settings but it stay there afterwards (not necessarily posting a no-sleep request).

    So, Helloooooooooo Microsooooooooft!, time to wake up and fix this.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-03T08:41:44+00:00

    Thanks, I tried that and there is not change,    :-[

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-10-03T07:47:53+00:00

    If you are seeing this problem, the best solution (until an update is provided) is to restart the Windows Update service:

    Start > Run

    services.msc

    (Alternatively: Windows key for search, "Services", run the Services app)

    Scroll down to (or type) "Windows Update"

    Right-click and Restart

    Your computer will now be able to sleep for a while, at least until Windows Update starts pending on the next flight.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-09-04T12:26:36+00:00

    It help's for me for a while, but today (sep. 4th 2020) I've noticed same problem again. I have KB4568831 installed.

    Same for me. I had no updates other than Windows Defender so it could be time/date triggered.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-09-04T12:18:14+00:00

    It help's for me for a while, but today (sep. 4th 2020) I've noticed same problem again. I have KB4568831 installed.

    Like JanezTroha, installing KB4568831 worked for a few weeks with no problems but I rebooted my machine yesterday after the latest updates and it is now being kept awake by MoUsoCoreWorker again!  I will reboot again later, but it seems the problem may be back again!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments