MoUsoCoreWorker.exe - Fix High CPU and PC Not Sleeping (MoUSO Core Worker Process)

Your PC will not go to sleep, or Task Manager shows MoUSO Core Worker Process burning CPU, and the executable behind it is MoUsoCoreWorker.exe. This guide explains what the process is, how to confirm it is genuinely the culprit, and how to fix it without breaking Windows Update.

What MoUsoCoreWorker.exe Actually Is

MoUsoCoreWorker.exe is the worker process of the Update Session Orchestrator (USO), the component of the Unified Update Platform that coordinates Windows Update in Windows 10 and Windows 11. It decides when to scan for updates, what order to install them in, and when a restart is needed. It runs under the Update Orchestrator Service, whose service name is UsoSvc.

Confirm the service exists on your machine:

sc query UsoSvc

Because the process legitimately holds power requests and legitimately spikes CPU during update work, most reports of "MoUsoCoreWorker.exe is broken" are actually reports of a stuck or failing Windows Update. Fix the update and the process behaves.

Is It Malware?

The genuine file is a Microsoft binary. Malware occasionally uses similar names, so verify rather than assume:

1. In Task Manager, right-click MoUSO Core Worker Process and choose Open file location.
2. The legitimate file lives inside a Windows system folder — commonly C:\Windows\System32 on older builds, or under C:\Windows\UUS\ on builds using the unified update stack. Anything running from a user profile, Temp, or Downloads is not legitimate.
3. Confirm the signature in an elevated PowerShell window, substituting the path you found:

Get-AuthenticodeSignature "C:\Windows\System32\MoUsoCoreWorker.exe" | Format-List Status, SignerCertificate

Status should be Valid and the signer should be Microsoft. That check is more reliable than any file path list, because paths vary by build.

Step 1: Confirm It Is Blocking Sleep

Do not fix a problem you have not confirmed. In an elevated Command Prompt:

powercfg /requests

You are looking for something like:

EXECUTION:
[PROCESS] \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe

If MoUsoCoreWorker.exe appears under EXECUTION or SYSTEM, it is holding an active power request. If it does not appear, stop here — something else is keeping the machine awake, and the fixes below will not help. Common alternatives that show up in the same output are audio streams, network drivers, and open media players.

Two related commands worth running:

powercfg -lastwake
powercfg /waketimers

-lastwake reports what woke the machine most recently. /waketimers lists scheduled wakes, and Windows Update legitimately sets these.

Step 2: Finish the Pending Update

This resolves most cases, and it is the only fix that addresses the actual cause.

1. Open Settings > Windows Update.
2. Click Check for updates and let anything pending download and install completely.
3. If it says Restart required, restart — properly, via Start > Power > Restart, not a shutdown from a laptop lid close.
4. After the reboot, re-run powercfg /requests.

The orchestrator holds its power request until the session it started actually completes. A download that finished three days ago but is still waiting on a restart is exactly the state that produces this symptom.

If an update is failing rather than merely pending, that is your real problem. Check Update history for a KB with an error code and fix that update. A failing update retried on a loop is the usual explanation for sustained high CPU.

Step 3: Run the Windows Update Troubleshooter

If updates are stuck rather than simply pending:

Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run

It resets the update components automatically and clears many stuck sessions without manual intervention.

If that does not work, reset the update components manually from an elevated prompt:

net stop wuauserv
net stop bits
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

Windows rebuilds SoftwareDistribution on the next scan. You lose cached downloads and local update history; nothing else.

Step 4: Control Wake Timers

If the complaint is that the machine wakes by itself rather than refusing to sleep, the fix is wake timers rather than the process:

1. Control Panel > Power Options > Change plan settings > Change advanced power settings
2. Expand Sleep > Allow wake timers
3. Set to Disable (or Important Wake Timers Only, which still permits critical system wakes)

You can also review the update-related scheduled tasks under Task Scheduler > Task Scheduler Library > Microsoft > Windows > UpdateOrchestrator. Look at what is actually present on your build rather than following a task name from an older guide, and check the History tab to see which task is firing.

Risk warning: disabling update orchestrator scheduled tasks or wake timers means updates install less predictably, and on a machine that is usually asleep they may not install at all for long periods. On a personal desktop that is an acceptable trade. On a managed or internet-facing device it is not.

What Not To Do

• Do not disable UsoSvc. It drives Windows Update. Disabling it stops security updates installing, and the service is partly protected so it frequently re-enables itself anyway.
• Do not delete MoUsoCoreWorker.exe. It is a protected OS file; forcing the issue breaks servicing and typically requires a repair install.
• Do not reach for powercfg /requestsoverride first. It suppresses the symptom by telling Windows to ignore the request, which can let the machine sleep mid-update. If you use it after everything else has failed, remove it once the underlying update problem is resolved.

Verify the Fix

powercfg /requests

Expected healthy output — every category empty:

DISPLAY:
None.
SYSTEM:
None.
EXECUTION:
None.

Then leave the machine idle past its sleep timeout and confirm it sleeps. Check powercfg -lastwake the next morning if it wakes again; it will name whatever is responsible, which may well turn out to be a network adapter or a scheduled task rather than Windows Update at all.

Prevention

• Restart weekly rather than only closing the lid. Sleep and hibernate never complete pending update sessions.
• Set active hours in Settings > Windows Update so restarts happen when you are away.
• Deal with failing updates when you first notice them — a KB that fails repeatedly is what turns a brief CPU spike into a permanent one.