A Windows Update that’s been parked at 30% for an hour is one of the more nerve-wracking things a PC can do. You can’t tell whether it’s quietly working or hard frozen, and forcing a reboot at the wrong moment feels like asking for trouble.
Here’s the reassuring part: most “stuck” updates fall into two buckets. Either the update is just slow and needs patience, or a download got corrupted and Windows is choking on the bad files. Both have clean fixes. This guide shows you how to tell which one you’ve got, then walks through resetting the update system from the gentlest option to the most thorough.
First: is it actually stuck, or just slow?
Don’t reset anything until you’ve confirmed the update is genuinely frozen. Feature updates move a lot of data and can sit on a single percentage for a long stretch while they work in the background.
Open Task Manager (Ctrl + Shift + Esc) and watch two things over a few minutes:
- Disk activity — steady reads/writes mean it’s installing.
- Network activity — ongoing traffic means it’s still downloading.
Stuck or slow?
| Disk/network shows steady activity | Working — leave it alone |
|---|---|
| Number creeps up slowly over time | Working — large update, be patient |
| Zero activity for 30+ min, number frozen | Likely stuck — start the fixes |
| Stuck at 100% specifically | Usually just needs a restart |
Step 1: Give it time, then restart cleanly
For anything stuck at a high percentage, the first move is the cheapest one: wait a genuine 30 minutes with no activity, then restart.
If the screen says “Working on updates, don’t turn off your computer,” that’s the install phase. Interrupting it can leave Windows mid-patch, so this is the one moment to be patient rather than trigger-happy. Once you’re confident it’s frozen (no disk light, no activity for a long time), a normal restart is the right call and clears a surprising number of cases — especially the classic stuck-at-100%.
If a clean restart doesn’t get you anywhere, move on to the real repair.
Step 2: Run the Windows Update troubleshooter
Before manual surgery, let the built-in troubleshooter try. It automates several of the same fixes and sometimes resolves it on its own.
On Windows 11: Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.
On Windows 10: Settings → Update & Security → Troubleshoot → Additional troubleshooters → Windows Update.
Let it finish, apply anything it suggests, then reboot and check for updates again. If it reports it couldn’t fix the problem — or fixes it but the update fails again — reset the components manually.
Step 3: Reset the Windows Update components
This is the fix that resolves most stuck updates. The idea is simple: stop the update services, clear the cached download folder so Windows can’t keep choking on a bad file, then start everything again and re-download cleanly.
Open an elevated command prompt or PowerShell (right-click → Run as administrator) and run these in order.
Stop the services:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserverClear the download cache and signature store. Renaming rather than deleting is safer — Windows recreates both folders, and you keep the old ones as a fallback:
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.oldSoftwareDistribution holds the downloaded update files and history; catroot2 holds update signature data. Clearing them forces a fresh, verified download.
Start the services again:
net start wuauserv
net start bits
net start cryptsvc
net start msiserverNow reboot, go back to Windows Update, and check for updates. Windows rebuilds the folders and pulls the update down fresh.
Reset checklist
- Command prompt / PowerShell opened as administrator
- All four services stopped before renaming folders
- SoftwareDistribution and catroot2 renamed (not just emptied)
- Services restarted in order
- Rebooted before checking for updates again
Step 4: Repair system files with DISM and SFC
If updates still fail after a clean re-download, the problem usually isn’t the update — it’s that Windows itself has corrupted system files, and the component store can’t apply the patch. Re-downloading won’t help; you have to repair the files first.
Run these from an elevated prompt, in this order:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowDISM /RestoreHealth repairs the underlying component store (the source SFC relies on), and sfc /scannow then fixes protected system files using that healthy store. Running them in the wrong order is a common mistake — SFC can’t do much if the store it pulls from is itself damaged. The full reasoning, log locations, and what to do when SFC reports it couldn’t fix everything are covered in our dedicated guide on using DISM and SFC to repair Windows.
After both finish, reboot and try the update one more time.
When nothing works
If you’ve reset components and repaired system files and the same update still won’t install, a couple of fallbacks remain:
- Install the update manually from the Microsoft Update Catalog. Find the KB number from the failed update, download the standalone package, and run it directly — this skips the Windows Update plumbing entirely.
- Check free disk space. A nearly full system drive can stall updates outright; feature updates in particular want a good chunk of free space to stage.
- Pause and retry later. Occasionally a problematic update is pulled or superseded by Microsoft within days, and the next one installs without complaint.
Wrapping up
Most stuck updates aren’t the disaster they look like. Confirm it’s actually frozen by watching disk and network activity, give a high-percentage update an honest wait, then restart. If it comes back, work down the ladder: troubleshooter, reset the update components by clearing SoftwareDistribution and catroot2, then DISM and SFC if files are corrupt.
The reset in step 3 is the workhorse — it fixes the majority of cases on its own. Reach for the file-repair steps only when a clean re-download still won’t take, since that points at Windows itself rather than the update.
