Should I allow it? I am not so sure if this is good since it's an executable file.
Yes i am looking for the same answer, What did you do.
Did you allow it?
Mouso core worker process
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
317 answers
Sort by: Oldest
-
Anonymous
2021-02-15T18:55:46+00:00 -
Anonymous
2021-02-15T19:15:10+00:00 that process is needed for windows update. you really do not want to block it that way.
-
Anonymous
2021-02-18T17:04:16+00:00 The no-sleep-because-MoUsoCoreWorker problem comes back once a month.
I went to Windows Update Settings, but there was no pending update, no failed update: my previous workaround won't work. (And I don't want to click Check for Updates.)
I paused updates, then right after un-paused. That fixed it. (Maybe that's the same as Check for Updates but hopefully not?)
Windows installed a few updates, then MoUsoCoreWorker.exe disappeared from "powercfg /requests"
(It's weird that Windows found a few updates to install, because earlier "Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.331.1296.0)" and didn't try any other updates but 100 minutes later now it just successfully installed "KB2267602 (Version 1.331.1299.0)" -- same KB, but a newer version -- and also installed KB4577586)
If this is a general-purpose solution, maybe I'll automate it with something like this in my daily maintenance task: https://stackoverflow.com/q/62424065/771768
PS: If you are having some PC sleep problem but "powercfg /requests" doesn't show MoUsoCoreWorker keeping your computer awake, none of the solutions here will help you; kindly post elsewhere.
-
Anonymous
2021-02-19T01:06:45+00:00 Hi - I have the same problem and I may have identified problem area but no fix. Let me explain.
I followed the troubleshoot instructions linked here to discover that my mouse is preventing the system from going into sleep mode.
https://thegeekpage.com/fix-windows-10-sleep-mode-not-working-solved/
Continuing with the instructions, I located the mouse in device manager and access its power management settings. But the setting for sleep mode management is greyed out, which means I am unable to access this setting. I can't say definitively if this is where the problem originates, but it seems likely.
My systems Windows 10 is fully updated.
-
Anonymous
2021-02-19T01:32:29+00:00 I started having this problem after running a Windows update in February 2021. Now this damn MoUsoCoreWorker.exe is keeping my computer from going to sleep unless I end this process. Microsoft, please fix this!