Windows update stuck: how to fix it safely
A Windows update that appears frozen is rarely as broken as it looks, and you almost never need to lose files to fix it. Work through this in order — stop as soon as one step works.
If the quick fix didn’t work
1. Free up disk space, then retry
Updates stall when the drive is too full to unpack. Open Settings > System > Storage, run Cleanup recommendations to clear temporary files, and make sure you have several gigabytes free. Then reboot and let the update try again.
2. Install the update manually
Note the update’s KB number from Windows Update history, then download that exact package from the Microsoft Update Catalog and run it. This bypasses a broken download without touching your files, and it’s the fix that resolves most “stuck at 0%” cases.
3. Repair system files
Open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. These repair the component store and system files that a half-finished update can corrupt. Reboot and retry the update.
4. Reset the Windows Update components
This is the deeper fix, and it’s safe for your documents. In an admin Terminal, stop the update services, rename the caches, and restart the services:
- Stop the services:
net stop wuauserv,net stop bits,net stop cryptsvc - Rename the download caches so Windows rebuilds them: rename the
SoftwareDistributionandcatroot2folders (add.oldto each). - Start the services again:
net start wuauserv,net start bits,net start cryptsvc, then reboot and check for updates.
When it’s a hardware problem
Update failures are almost always software, but two hardware issues masquerade as stuck updates: a failing drive (updates fail repeatedly with disk errors in the logs) and a laptop that overheats and throttles mid-install. If a drive is throwing errors, back up immediately and see our repair-versus-replace guidance rather than fighting the update.
When to stop and get help
If the reset doesn’t work and the machine won’t boot into Windows at all, use the Startup Repair option in the recovery menu, or roll back the update from Safe Mode. If you’re not comfortable at the command line, that’s a fair point to hand it to someone who is — the steps above are safe, but the recovery menu is where mistakes get expensive.
Frequently asked questions
Is it safe to force-restart during an update?
It’s a last resort, not a first move. Wait at least 30 minutes first. If the screen has genuinely not changed and the drive light is dead, a forced restart is usually recoverable — Windows is built to roll back a half-applied update.
Where do I find the KB number?
Settings > Windows Update > Update history. Each entry starts with “KB” followed by digits.
Will any of this delete my files?
No. Everything above resets update machinery, not your documents. Only a full “Reset this PC” with the wrong option removes files, and that’s not on this list.