Why is Windows Update stuck at 0%?

Often disk space, sleep/battery policies, a metered or broken network path, or a wedged download service. Pause/resume, free space, and a single clean restart fix many cases.

Is Windows Update down globally?

Rarely in a way that matches one office PC. Check Windows release health and your Intune/WSUS consoles. One device stuck is usually local.

Should I reset Windows to fix a stuck update?

Not first. Free disk space, repair the component store with DISM/SFC, verify the update ring, and collect the error code before destructive resets.

Why does Intune say not compliant while Update is running?

Compliance policies expect a patch level the device has not reached yet. Fix the update path; do not fight Conditional Access separately until the patch installs.

Guides / Windows Update stuck at work (0% download, pending restart, errors)

Part of: Work PC problems: updates, apps, printers and remote access

Last reviewed 5 Oct 2026 · By Harry

Windows Update stuck at work (0% download, pending restart, errors)

Windows Update hung at 0%, looping restarts, or feature update blocked on a work PC? WSUS, Intune, disk and network checks before you wipe the device.

The laptop has sat on "Downloading 0%" since yesterday. Or it demands a restart every hour and never finishes. Or Feature update deferred forever. Users blame Microsoft. MSPs who jump straight to in-place upgrades without checking disk space, WSUS and Intune rings create second tickets. Work the cheap steps first.

Is it Microsoft?

There is no single public "Windows Update is down" page that maps to your office. Microsoft 365 Service health covers cloud services; Windows client update delivery issues appear in the Microsoft 365 admin centre Message centre / Windows release health when they are widespread. Check Microsoft 365 and Azure only when cloud-delivered features (Autopatch, Intune) are implicated. For one PC stuck at 0%, assume local or on-prem delivery until proven otherwise.

User checks (safe to try)

Disk space. Feature updates want tens of gigabytes free on C:. Less than 20 GB free is a common silent stall. Empty Recycle Bin and Downloads; do not delete Windows folders by hand.
Plugged in and awake. Laptops on battery or sleep pause downloads. Plug in, set power to Performance, keep the lid open.
Network. Try Ethernet or a known-good SSID. Guest Wi-Fi and metered connections throttle or block update downloads. See Wi-Fi connected but no internet if browsing also fails.
Pause and resume updates once in Settings → Windows Update. Cheap reset of a wedged download.
Restart once into a clean boot after saving work. Repeated forced restarts mid-driver install make things worse — one clean attempt, then stop.
VPN. Some firms require VPN to reach WSUS or the update connected cache. Others break Windows Update through full tunnel. Test both states if policy allows.

IT checks

Delivery path. Is the PC getting updates from Windows Update cloud, WSUS, Configuration Manager, or Intune / Autopatch? The fix differs. Check Settings → Windows Update → Check for updates and the company's documented ring.
Intune / Company Portal. Compliance policies that require a patch level will mark the device non-compliant while the update is stuck — see device not compliant and Company Portal apps.
WSUS / ConfigMgr sync. Approve the update, confirm the PC's boundary and collection, and watch UpdatesDeployment.log / WUAHandler.log rather than guessing from the UI percentage.
Component store repair. Elevated: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow. Run these when downloads fail with cryptic 0x800F* errors after disk space is confirmed.
Windows Update troubleshooter / Service restarts. Restart wuauserv, bits, cryptsvc, and msiserver in that order. Rename SoftwareDistribution\Download only when you know the PC can re-download — do not do this blindly on metered links.
Feature update blocks. Safeguard holds, incompatible drivers, and third-party disk encryption can block feature updates while quality updates still work. Read the why in SetupDiag or Intune feature update reports.
Office vs Windows. Users often confuse Microsoft 365 Apps update channels with Windows Update. Confirm which product is stuck.

Error codes worth recognising

0x80070070 is disk full. 0x8024401c / related 0x80244* often mean WSUS / gateway trouble. 0x800f0922 often means reserved partition or connectivity during feature update. Search the exact code in Microsoft's docs after you have disk and network evidence — do not shotgun registry "fixes" from random blogs on a work PC.

When to escalate

Escalate to Microsoft or your patch vendor when many devices in the same ring fail with the same code after WSUS/Intune health looks fine. Escalate to networking when only one site cannot reach the update endpoints. One laptop with 4 GB free on C: needs disk cleanup, not a Severity 1 Windows bridge.

Related status pages

Related guides

FAQ

Why is Windows Update stuck at 0%?: Often disk space, sleep/battery policies, a metered or broken network path, or a wedged download service. Pause/resume, free space, and a single clean restart fix many cases.
Is Windows Update down globally?: Rarely in a way that matches one office PC. Check Windows release health and your Intune/WSUS consoles. One device stuck is usually local.
Should I reset Windows to fix a stuck update?: Not first. Free disk space, repair the component store with DISM/SFC, verify the update ring, and collect the error code before destructive resets.
Why does Intune say not compliant while Update is running?: Compliance policies expect a patch level the device has not reached yet. Fix the update path; do not fight Conditional Access separately until the patch installs.

Did this help?