Mouso core worker process

Ok, here's another example of the MoUSO issue. Core i7-3520M, 2.9GHz-3.6GHz. I'm installing a new Win 10 21H1. I just didn't the 2021-08 Cumulative update and the button for Restart Now is visible. I minimize the Settings window, and when I restore the window MoUSO uses 50% CPU for 24 seconds, I timed it. Every time I restore it, 24 seconds of 50% CPU. And this is on a 3rd gen Core i7 which runs at 3.44GHz for that duration.

I just rebooted, and the update is installed. I open the Windows Update page, and now when I minimize the page and restore it for seconds the 50% CPU usage is split between the Settings process and the MoUSO process. Every time I restore the non-active Windows Update window, 10 seconds of 50% CPU.

Rapidly clicking on the taskbar Settings gear icon results in a very slow minimize and restore of the Windows Update window. When I go to the Settings Home screen, it's not like this. Very very fast minimize and restore of the window. So even as of August 2021, MoUSO is broke and inefficient.

They need to fix what they already have instead of making a new OS that can only be installed on computers manufactured in 2016 or newer. But maybe that IS their fix for the broken MoUSO, buy new hardware.

EDIT: Oh, regarding your PS: above, check your Fast Startup in the power settings. I've seen numerous computer hang on the first, then a power cycle lets it boot properly. This happens after you select Shut Down and then boot up. A Restart shouldn't show the issue, only after a Shut Down. So disable Fast Startup if this applies to you.

I had Windows 10 20H1 and upgraded to Windows 10 20H2. Problem started: "Windows Update" does not work anymore. I get "Er is iets misgegaan. Probeer instellingen later opnieuw te openen" (which means: "something went wrong. Try again later"). How horrible can one program this!??? What went wrong, and why?

I upgraded to Windows 10 21H1. Not solved.

Looking in the event log I often see following error messages:

Naam van toepassing met fout: mousocoreworker.exe, versie: 10.0.19041.1081, tijdstempel: 0xd634e686

Naam van module met fout: ucrtbase.dll, versie: 10.0.19041.789, tijdstempel: 0x2bd748bf

Uitzonderingscode: 0xc0000409

Foutmarge: 0x000000000007286e

Id van proces met fout: 0x20fc

Starttijd van toepassing met fout: 0x01d78dbbde967bfc

Pad naar toepassing met fout: C:\Windows\System32\mousocoreworker.exe

Pad naar module met fout: C:\WINDOWS\System32\ucrtbase.dll

Rapport-id: eb98c71b-87a7-4b48-b4c6-82f837c40f7b

Volledige pakketnaam met fout: 

Relatieve toepassings-id van pakket met fout:

Hence, I believe this MoUsoCoreWorker.exe also caused for me that my Windows Update does not work anymore.

PS: typically my PC does not boot in 1 go. It always "hangs" the 1st time I boot (cold). After reset (pressing power button for 5 secs) and restart, the PC boots fine.

What is going on with Windows?

What is Microsoft doing?

Is there any quality control before releases are issued?

Please fix ASAP

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.

it's not this, but you don't need to try it. It is temporary. It says repair windows update, but I have this problem again. I'm sorry that it can't be solved.

I think you mean the "Windows Update Medic Service" don't you?!