Mouso core worker process

I've come to believe that the MoUSO Core Worker Process is just flawed and not optimized at all. I just installed a brand new Win 10 on a Pentium B960 2.2 GHz laptop with an SSD. I just finished all windows updates. I minimize the Windows Update settings window, and when I restore the window back this process spikes CPU usage to 50% (using one full core) for about 7 seconds. Every single time I restore the window from it being minimized, my CPU spikes with this process, and it's not even doing any updates right now. So between this process and the Settings process, my CPU runs at nearly 100% for 7 seconds.

Right after the last batch of updates it had the Restart button. When I minimized and restored at that time this process took 50% CPU for 20 seconds.

Windows 10 has gotten so bloated throughout the years, no wonder why you need a Core processor or something new just to enjoy it.

Windows Update is the benchmark of any computer. Time how long your CPU is spiked to 100% and you can rate any computer. Celerons are THE WORST at processing updates.

If Microsoft could slim down and fix the processor usage for updates, they'd have one heck of an OS that will run better on ALL CPUs within the last 15 years.

Here is the fix (worked for me at least).

tl;dr [Run the Windows Update Troubleshooter]

1. Open 'Troubleshoot Settings' (Win Key, start typing it, press it)
2. Press 'Additional Troubleshooters'.
3. Press 'Windows Update'.
4. Run the update Troubleshooter.

Mine found errors and resolved them.

5. RESTART.
6. Open CMD in Admin and run 'powercfg -requests' to see if the glitch is still there (mine had gone at this point)
7. Run Windows Update and look for updates. Now, when I opened mine, there was an error shown 'Failed to Install', I think this was the issue causing that exe to run constantly, and it was the Adobe Flash removal update!

Let that update now hopefully run correctly, and when it says update installed, go back to CMD, press the up arrow key to show last command and press enter to see if the exe isn't listed... hopefully it isn't and all is back to normal.

If memory serves this isn't the first time I've had to run this same process to fix an update issues causing sleep errors.

This is the true legit fix right here. After doing so you'll have to fix the power settings for your Ethernet, Wifi and other devices that ask the computer to remain on if used.

I had the same issue back again today. I fixed by going into services, stopping Windows Update Service and restarting again (I guess temporally). Worked in two different computers. I ran windows update, and found a pending patch, I installed, reboot, and powercfg -requests no longer shows mousocoreworker.exe. Hope this helps!

I have automatic updates disabled in Group Policies. On August 20 I checked for updates and applied them. Ever since then the system would not go to sleep at the proper idle time interval.

powercfg requests revealed:

EXECUTION:

[PROCESS] \Device\HarddiskVolume7\Windows\System32\MoUsoCoreWorker.exe

USO Worker

Update status showed no updates pending and all updates installed completely. Stopping in starting Windows Update Service did not stop the request.

Issuing the command:

powercfg /requestsoverride process mousocoreworker.exe execution

would allow system to once again sleep at idle timeout. However powercfg still showed the request.

I then ran the Update Troubleshooter which reported no problems, nothing to fix.

I shutdown the system. Waited a few minutes and restarted.

powercfg requests showed the request was gone and has remained gone after several restart.

It appears Update Troubleshooter stopped MoUsoCoreWorker.exe perhaps in combination with powercfg /requestsoverride.

In my case MoUsoCoreWorker.exe was staying open long after Windows Update had finished. No issues since KB4568831.