Mouso core worker process

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.

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.

6 months later. It's officially ridiculous.

The process is preventing machines form entering S states.

If an update is found - whether optional or recommended - this process perpetually calls powercfg.

There's already a timeclock on force-installing updates. Once that timeclock expires, this behavior might be excusable. But as previously mentioned, this behavior is omnipresent on all updates - irrespective of timeclock on the force-install.

This was fixed and now again it's broke! MS do you have any idea how much power this wastes??!!

FIX IT and keep it FIXED!!!!

Actually its never been fixed.  The problem has gone on for months.  MS sucks.

Yup, the problem keeps returning. Sleep mode can't be relied on, so it's back to shutting down every time. The sleep mode option is more of a false hope now - like taking melatonin with caffeine.