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
    2021-02-25T06:02:52+00:00

    I have found a simple steps to troubleshoot this issue. Works on my 4 different PCs.

    (I'm not sure about the English names of Settings app...)

    1. Settings=>Windows Update=>Other options=>Set delay of Windows Update on max days
    2. Close Setting
    3. Wait some time (~1 min)
    4. Open Settings again=>Windows Update=>click on Resume Windows Update button at the right
    5. That's all.

    Sorry, I have only Pro version. I don't know if the Home version has an option to pause updates.

    Just writing to confirm that this solution has worked (so far) in my case too. The update troubleshooter did not find any problems. But when I did this here what happened is that KB4577586 (remove flash player) was installed and MoUsoCoreWorker.exe is now gone from powercfg -requests. And Windows goes into sleep mode again. Hope this will last.

    I tried to fix hitting check for updates several times but never showed any. I tried this trick, waited 1 min resume and it comes back with KB4023057 downloaded and installed, UNF****** believable.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-25T05:58:28+00:00

    thats when problem started for me. KB4577586 (remove flash player)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-25T05:56:39+00:00

    STILL a problem Feb 25 2021. I can't get MoUsoCoreWorker.exe to stop with the restart windows update. There is no updates. Another crappy patch from MS now ruined something else. When they fix this problem, most likely will break something else.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-24T10:18:55+00:00

    I have found a simple steps to troubleshoot this issue. Works on my 4 different PCs.

    (I'm not sure about the English names of Settings app...)

    1. Settings=>Windows Update=>Other options=>Set delay of Windows Update on max days
    2. Close Setting
    3. Wait some time (~1 min)
    4. Open Settings again=>Windows Update=>click on Resume Windows Update button at the right
    5. That's all.

    Sorry, I have only Pro version. I don't know if the Home version has an option to pause updates.

    Just writing to confirm that this solution has worked (so far) in my case too. The update troubleshooter did not find any problems. But when I did this here what happened is that KB4577586 (remove flash player) was installed and MoUsoCoreWorker.exe is now gone from powercfg -requests. And Windows goes into sleep mode again. Hope this will last.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-24T10:15:45+00:00

    Thanks House 24. This was simple and worked great. Same flash uninstaller problem!

    Was this answer helpful?

    0 comments