Mouso core worker process

I'm as frustrated as everyone else with this. Running Windows Update had solved my problem with this issue, but only temporarily. Maybe they're setting us up for requiring proof of getting Bill Gates' COVID vaccine in order to make the issue go away.

TL;DR the problem keeps coming back. Retrying the Windows Update from Settings fixed the MoUsoCoreWorker.exe power request.

I've had this problem intermittently for a long time. I have a script that wakes up my machine at 4AM to update apps to the latest version. Last time 11/10 I fixed the problem by stopping the service, but it came back today 12/03. 

I checked whether a reboot was pending (reg key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired) and it wasn't. I opened the Windows Update menu in Settings, and it said last updates were fine. (A lie!!!) (Also, I don't want to Check for updates, because IIRC that puts beta software on your PC.) After messing around for a while with powershell using Microsoft.Update.Session COM object and Get-WindowsUpdate for 60 minutes and not seeing why updates were required, and I went back to Windows Update dialog and there was a big red image and now it said there was an error at 4:02 AM, and I should retry.

After clicking retry, KB2267602 and KB4586876 installed, and the PC wanted to schedule a reboot 15 minutes out. I rebooted, and now MoUsoCoreWorker.exe doesn't show up with p owercfg /requests. Horray!

In Event Viewer I see WindowsUpdateClient updates starting at 4:02AM, and no errors, just downloading and installing updates. Weirdly, last night at 8:50 the last thing windows update did was "successfully install" KB2267602. That was while I was playing a Steam game remotely over Steam Link, and it was a whole 40 minutes later that the computer went to sleep. But when I clicked the Windows Update button to Retry, I see it again installed KB2267602 this morning (??).

Problem solved for now, until a month from now when another update fails and I need to manually poke Windows Update again to fix it. When I find some powershell that can automate this, I'll update the thread.

Scripting can never be a solution to this problem. This is a failure of an integral part of the OS.

While everybody who posted on this thread agrees the behavior is undeniably flawed, making the assumption that it's a failure rather than by design seems unlikely. This issue has persisted for over 6 months without even an iota of acknowledgement on Microsoft's part.

The process only continues calling when there's an uninstalled Recommended or Optional Update.

Uninstalled Driver Updates are not subject to perpetual powercfg request.

At this point, it stands to reason the the process is functioning as intended.

As I mentioned in my post of the 10th Nov it does appear to be some sort of issue with Windows Updates getting stuck and I agree it entirely makes sense that it will keep trying to get recommended/optional updates with the unfortunate consequence of waking windows from sleep.

Going through the steps I mentioned in my post of the 10th Nov, has resulted in my PC going into standby without fail since, as it always used to. My PC has received updates in the meantime without further problem and I report back again in early Jan, given others have suggested the issue might return at some stage.

I suspect there are several different flavours of this issue within this thread, but hopefully at least some can be fixed by getting stuck updates downloaded as I did.

I do backup my PC image using Acronis to a NAS regularly so do not have the concern that stopping/starting the WU service would cause windows update to fail for whatever reason; it's only dependency is RPC. Stopping/starting services is a common practice when troubleshooting issues. I note that Microsoft introduced Windows Update Medic Service (WaaSMedicSVC) in Windows 10 circa Oct20. The entire purpose of this service is to fix any damages suffered by the Windows Update components.

R. Hanson 690 mentioned problems after installing the KB4586853 update Preview and I would comment that unless fixing a specific issue that a user has encountered, it is not really necessary to install these preview patches as they are issued as part of the mandatory Patch Tuesday release further down the line. I noticed that my problem might have occurred after installing KB4580364 (a different preview patch).

It would be interesting to get confirmation that users with the Windows 10 20H2 update and Windows Update Medic Service installed also see the issue?