Windows Update Stuck or Failing: Fixes That Actually Work

Windows Update failures have a particular flavor of frustration: the same update downloads, installs to 30%, fails with a hex code, and reappears tomorrow to fail identically. The error codes look random but aren't, and the fixes form a clear escalation ladder — from a two-minute cache reset to the in-place repair that fixes virtually everything. Here's the ladder, in order.

[Personal note placeholder: a sentence about a stubborn update you've fought — which rung of this ladder finally fixed it.]

01 — Before Anything Else: The Boring Checks

  • Disk space. Feature updates want 20+ GB free. Settings → System → Storage; run Disk Cleanup (cleanmgr) → Clean up system files if you're tight.
  • Restart properly. Fast Startup means "shut down" often isn't a real reboot. Use Restart, which always is. Pending operations from a previous update frequently block the next one until a true reboot.
  • Time and date correct? Wrong system time breaks the TLS connections Update relies on.
  • Third-party antivirus has a long history of interfering with feature updates — temporarily disabling it is a legitimate diagnostic step.
  • Patience, once. A feature update sitting at the same percentage for 30–60 minutes can be normal. Sitting overnight is not.

02 — Rung 1: The Built-In Troubleshooter

Settings → System → Troubleshoot → Other troubleshooters → Windows Update. It resets stuck services and clears some corrupted state automatically. Its reputation is poor because people expect miracles; as a first rung it fixes the easy third of cases and takes two minutes.

03 — Rung 2: Reset the Update Components

Windows Update keeps downloads and metadata in SoftwareDistribution. When that cache corrupts, every retry reuses the same broken files — so the same update fails the same way forever. Throw the cache away and let it rebuild:

# Command Prompt (Administrator)
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
 
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
 
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Check for updates again — they'll re-download from scratch. Once everything installs cleanly, the .old folders can be deleted to reclaim space.

💡 Plain English: this is the update system's equivalent of clearing a browser cache. Nothing about your files or settings is touched — only Update's own scratch space, which Windows happily rebuilds.

04 — Rung 3: Repair the Component Store (DISM + SFC)

If resets don't help — especially with errors like 0x80073712 — the component store (the master repository Windows installs updates from) is itself damaged. Repair it, then verify system files against the repaired store, in this order:

# Command Prompt or PowerShell (Administrator)
DISM /Online /Cleanup-Image /RestoreHealth
# (Downloads known-good files from Windows Update; 10–30 minutes,
#  and it routinely sits at 62% for ages — that's normal, let it run.)
 
sfc /scannow

The order matters: SFC repairs files using the component store, so running it before DISM means repairing from a possibly-corrupt source. DISM first, SFC second, then retry the update.

05 — Decoding the Common Error Codes

CodeWhat it usually meansMost effective fix
0x80070002 / 0x80070003Files missing/corrupt in the update cacheRung 2 (component reset)
0x80073712Component store corruptionRung 3 (DISM)
0x800f0922Can't reach update servers (VPN!) or the System Reserved partition is too fullDisconnect VPN; if recurring, the partition issue → Rung 4
0x80070070Out of disk spaceFree 20+ GB
0xC1900101-xxxxDriver problem during a feature updateUpdate/remove third-party drivers, unplug nonessential USB devices, disable AV, retry
0x80240034Download repeatedly failingRung 2; check network/proxy

For anything not listed: Settings → Windows Update → Update history shows which specific update fails. You can fetch that KB number manually from the Microsoft Update Catalog (catalog.update.microsoft.com) and install it directly — manual installs bypass several of the mechanisms that get stuck.

06 — Rung 4: The In-Place Upgrade Repair (The Big Fix)

When updates fail no matter what, this is the fix that actually ends it: reinstalling Windows over itself while keeping every file, app, and setting. It rebuilds the component store, the servicing stack, and the partition structure issues that cause 0x800f0922 — the deep machinery no in-OS tool fully repairs.

  • Download the Windows 11 ISO from Microsoft's official download page (or use the Installation Assistant).
  • Double-click the ISO to mount it, run setup.exe from inside it.
  • When asked, choose "Keep personal files and apps." This is the whole trick — it's a repair, not a wipe.
  • Allow an hour or two. The machine reboots several times.

In years of fixing update-mangled machines, the in-place repair succeeds where everything above fails often enough that I now reach for it after one failed pass through rungs 1–3 rather than burning an afternoon. Back up first as a matter of principle — and if an update has left a machine unable to start at all, that's a different problem with its own playbook: see my Windows 11 won't boot guide [update this link to article #1's URL once published].

07 — Preventing the Next One

  • Keep 20+ GB free on C: permanently — cramped disks are behind a surprising share of update failures.
  • Use Restart, not shutdown, at least weekly.
  • Don't kill the power mid-update, however stuck it looks, unless it's been hours — interrupted servicing is how component stores get corrupted in the first place.
  • Set active hours so updates stop ambushing your workday: Settings → Windows Update → Advanced options.

🔒 Bottom line: escalate in order — troubleshooter, cache reset, DISM+SFC, manual KB install, in-place repair. Each rung subsumes the one before it, the whole ladder touches none of your data, and the top rung fixes the unfixable. There is almost never a reason to clean-install over an update problem.

← Newer Posts Older Posts →