When Windows Update won’t install, free space, run the troubleshooter, repair files, and reset update components to finish the install.
If a Windows update refuses to go in, you’re not stuck. Most blocked installs boil down to storage gaps, paused services, damaged system files, device-specific blocks, or flaky network caches. This guide gives you a tight checklist and proven fixes that clear those roadblocks without guesswork. Start at the top; stop when the update completes.
Windows Update Won’t Install: Fast Checklist
- Check storage: Keep at least 20–25 GB free for feature upgrades; smaller patch days still need headroom.
- Reboot once: A pending restart can lock files the installer needs.
- Disable third-party antivirus temporarily: Some suites hook into drivers and block setup.
- Run the Windows Update troubleshooter: It resets services and clears stuck jobs.
- Repair system files: Use DISM, then SFC, to restore the component store.
- Reset update components: Stop BITS and Windows Update, rename SoftwareDistribution and Catroot2, then start services.
- Unplug extra USB gear: Leave only keyboard, mouse, and network to reduce driver tangles.
- Check known issues: Some updates are paused for certain hardware or apps.
- Install offline: Use the standalone .msu or the Installation Assistant when the in-place method fails.
Quick Fix Matrix
| Symptom | Likely Cause | Fast Fix |
|---|---|---|
| Stuck at 0–20% | Services paused or cache jammed | Run troubleshooter; reset components |
| Error 0x800f0922 | Low system reserved partition or space | Free space; expand system reserved if needed |
| Error 0x8007000E | Low RAM or storage during staging | Close apps; free disk; try offline |
| Error 0x80070422 | Windows Update service disabled | Enable and start the service |
| Error 0x80070002/3 | Missing temp files or catalog entries | Reset components; run SFC |
| Error 0x800F081F | Missing .NET or component store files | Run DISM then SFC |
| Download loops | BITS queue corruption | Clear SoftwareDistribution; restart BITS |
| Install finishes then rolls back | Driver or security tool conflict | Remove recent drivers; disable AV temporarily |
Before You Start: Basics That Save Time
Back up your files. Keep the device on AC power. Use a wired link if Wi-Fi is wobbly. Sign in with an admin account so commands have the rights they need.
Storage matters. Feature releases can swell during staging and rollback. Aim for a roomy C: drive to keep temp work files and Windows.old from choking the process.
Run The Windows Update Troubleshooter
Windows ships with a tool that finds and fixes stuck queues, paused services, or policy remnants. Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) and run Windows Update. Let it apply fixes, reboot, and try the update again.
Need the official steps? See the Windows Update troubleshooter guide. If the tool reports changes, run it twice; follow-up passes often clear lingering items.
Repair System Files With DISM And SFC
Damaged component store files block patching. Open an elevated Terminal or Command Prompt and run the health restore command, then a file scan:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Wait for each step to finish. Reboot after SFC, then retry the update. Microsoft outlines both tools here: Use System File Checker and DISM.
Reset Windows Update Components
If downloads loop or installs stall, reset the update pipeline. In an elevated Command Prompt run these lines in order:
net stop bits
net stop wuauserv
net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\System32\catroot2 catroot2.bak
net start cryptsvc
net start wuauserv
net start bits
This flushes cached jobs and catalogs, then restarts the services clean. Try the update again.
Check Release Health For Known Blocks
Microsoft sometimes holds an update for certain chipsets, drivers, or apps. Review the current notes on the Windows release health page. If your device matches a safeguard hold, wait for the fix or update the flagged driver before retrying.
Free Up Space And Remove Roadblocks
Low space causes many failures. Empty Downloads and Recycle Bin, clear temporary files in Settings > System > Storage, and uninstall big apps you no longer need. Move videos or VMs to another drive. Aim for double-digit gigabytes free so the installer can stage and roll back safely.
If a third-party antivirus or a recent driver update coincides with the failure, pause or remove it during the install. Re-enable after the system is current.
Try An Offline Or Assisted Install
When the in-place route fails repeatedly, grab the standalone package or use the assistant. Search the Microsoft Update Catalog for the KB number and download the .msu that matches your build. For version upgrades, the Installation Assistant can bring a stuck PC forward without a full wipe.
Command Cheat Sheet
| Task | Command | When To Use |
|---|---|---|
| Health restore | DISM /Online /Cleanup-Image /RestoreHealth | When update errors cite missing components |
| File scan | sfc /scannow | After DISM; repairs protected files |
| Stop services | net stop bits & wuauserv & cryptsvc | Before clearing caches |
| Clear caches | Rename SoftwareDistribution and catroot2 | Break download/verification loops |
| Start services | net start cryptsvc & wuauserv & bits | Bring update pipeline back online |
Confirm Device Readiness
If a feature update won’t offer itself, the PC might not meet version rules. Check CPU generation, TPM, and boot mode against the published requirements. Microsoft lists them on the Windows 11 specifications. If the device is out of scope, stay on the supported version or plan a hardware refresh.
Clean Finishes And Post-Update Checks
After a successful run, clear old restore points that are no longer needed, then create a fresh one. Review Device Manager for yellow marks, verify your backup still runs, and confirm activation is intact. Give the system a day to pull any follow-up patches.
When Nothing Works
If failures persist across fresh boots, offline installs, and the full reset, capture the error code and search the official list of upgrade and installation errors. A repair install using the latest ISO can refresh Windows while keeping files and apps. As a last resort, a clean install solves persistent corruption, so keep backups current.
Repair Disk Errors And Image Sources
File-system hiccups can break the installer’s path. Open an elevated Terminal and run a quick disk check, then reboot if asked:
chkdsk /f C:
If DISM reports that source files can’t be found, try the health restore again after a restart. Keeping the Windows image healthy prevents patch chains from failing mid-way and rolling back. Once storage and the file system are clean, retry Windows Update from Settings.
Clean Boot Or Safe Mode Install
Background services from third-party tools can hook into drivers and block upgrade steps. Use msconfig to run a clean boot: open System Configuration, choose Selective startup, uncheck Load startup items, and on the Services tab choose Hide all Microsoft services then click Disable all. Reboot, run the update, then restore normal startup afterward.
If that still fails, boot to Safe Mode with Networking and try the standalone package. Safe Mode keeps only core drivers, which trims many conflicts without a full wipe.
Refresh Network And Delivery Settings
Broken caches can stop downloads cold. In an elevated Terminal, reset name resolution and sockets, then restart the PC:
ipconfig /flushdns
netsh winsock reset
Open Settings > Windows Update and resume the download. If the connection is marked as metered, lift that flag so large packages can flow. Pausing and resuming updates can also kick a stuck queue back into motion.
If you plan a clean install, export browser data, back up app keys, and keep drivers on a USB stick so first boot goes smoothly with network and graphics ready.