Windows Update errors are almost always fixable without reinstalling Windows. The right sequence matters, though. Start with the two-minute checks before touching anything in the command line.
This guide covers every reliable fix, ordered easiest to hardest, including the exact commands you need for the terminal steps.
Run the Built-In Windows Update Troubleshooter First
Microsoft ships a dedicated troubleshooter that catches the most common failures automatically. Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update and Security > Troubleshoot > Additional troubleshooters (Windows 10), then select Windows Update and hit Run.
The Windows Update Troubleshooter checks service states, clears the download cache, and resets stuck components. It resolves roughly 40% of update failures on its own.
After it finishes, restart your PC and try the update again before moving further.
Free Up Disk Space
Feature updates, especially the annual Windows 11 releases, need 8 to 20 GB of free space to stage properly. If you are running low, the update will silently fail or loop forever.
Open Settings > System > Storage and use Storage Sense to clear temporary files. Alternatively, search for Disk Cleanup, select your C: drive, and check Temporary files, Delivery Optimization Files, and Windows Update Cleanup. Delete those before retrying the update.
Restart the Windows Update Services
Update services sometimes stall after a failed download or a hard shutdown. Restarting them and clearing the local update cache clears out whatever the process got stuck on.
Open Command Prompt as Administrator. Run these commands one at a time:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
Now rename the two cache folders so Windows recreates them fresh:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old
Then restart the services:
net start wuauserv net start cryptSvc net start bits net start msiserver
The SoftwareDistribution folder holds all downloaded update files. Renaming it (not deleting it) forces Windows to rebuild it from scratch without risking data loss. The catroot2 folder holds cryptographic signatures for update packages; it gets corrupted more often than most people realize.
Restart your PC after running these commands, then check for updates again.
Run SFC and DISM to Repair System Files
A corrupted system file is one of the more stubborn causes of update failures. Two built-in tools handle this: SFC scans and repairs Windows system files from a local cache, while DISM repairs the Windows image itself, which is what SFC pulls from.
Run them in this order. Open Command Prompt as Administrator.
First, run DISM:
DISM /Online /Cleanup-Image /RestoreHealth
This contacts Windows Update servers to pull a known-good image and can take 10 to 30 minutes. Let it finish completely.
Then run SFC:
sfc /scannow
If SFC reports it found and repaired corrupted files, restart and try the update again. If it reports it could not repair some files, the DISM step should have already addressed the underlying image, so a second sfc /scannow pass often succeeds after that.
Pause and Re-Enable Updates
Sometimes a specific update package gets corrupted mid-download and Windows keeps trying to install the same broken file. The fix is simple: pause updates for a week, then resume them.
Go to Settings > Windows Update > Advanced Options > Pause Updates. Set a pause date. Then come back and resume. Windows will re-download the update files fresh instead of retrying the corrupted cache.
Install the Update Manually via Microsoft Update Catalog
If a specific KB number is stuck, skip the automatic process entirely. Go to catalog.update.microsoft.com, search for the KB number showing in your error, download the correct version for your architecture (x64 for most modern PCs), and run the installer directly.
This bypasses every Windows Update service component. It works reliably for stuck quality updates and security patches, though it does not work for feature (version) upgrades, which need the full update pipeline.
Disconnect External Peripherals
This sounds too simple, but some driver-level conflicts genuinely block update installs. USB hubs, older docking stations, certain webcams, and generic HID devices have all caused update failures that disappeared the moment they were unplugged.
Before running a major update, disconnect everything except keyboard and mouse. Reconnect after the reboot.
Common Windows Update Error Codes and What They Mean
Error codes narrow down what actually went wrong. Three show up constantly:
- 0x80070002 (File not found): The update file is missing or the download was incomplete. Renaming the SoftwareDistribution folder and re-downloading usually fixes this.
- 0x800f0922 (VPN or proxy interference, or insufficient disk space): Either disconnect from VPN before updating or free up more space on the system partition.
- 0x80073712 (Component store corruption): Run the DISM command above followed by SFC. This code specifically points to a damaged Windows component store.
If your error code is not listed here, search the Microsoft Support site with the exact code. Microsoft documents all of them, including specific fixes per code.
If you are dealing with an app that silently auto-renews without clear disclosure, that is a separate problem worth tracking down. Reading about how to cut AI subscription costs is one way to audit what your software is actually charging you behind the scenes.
In-Place Upgrade or Reset as a Last Resort
If nothing above works and the update still fails, the last option before a clean reinstall is an in-place repair upgrade. Download the Windows 11 (or Windows 10) Installation Assistant from Microsoft’s site and run it. It reinstalls Windows over itself, keeping your files and apps, and replaces any corrupted system components in the process.
This is more thorough than SFC or DISM because it replaces every system file, not just the ones the tools flagged.
If you want a full reset instead, go to Settings > System > Recovery > Reset this PC. Choose “Keep my files” if you want to preserve personal data. This takes longer but leaves you with a genuinely clean Windows install.
Choosing between software tools for troubleshooting tasks follows the same logic as evaluating automation tools like n8n vs Zapier: pick the one that actually matches the problem, not the most popular option.
FAQ
The most common causes are corrupted download files in the SoftwareDistribution folder, damaged system files that the update process depends on, insufficient disk space, stalled update services, and occasionally a conflict with a VPN or third-party security software. Running the Windows Update Troubleshooter first identifies which of these is at play.
Stop the four update services (wuauserv, cryptSvc, bits, msiserver) via Command Prompt as Administrator, rename the SoftwareDistribution and catroot2 folders, then restart those services. This effectively resets the entire update pipeline without touching your personal files or installed apps.
The SoftwareDistribution folder at C:\Windows\SoftwareDistribution is where Windows temporarily stores downloaded update files before installing them. If that folder gets corrupted or a download fails mid-transfer, the update cannot complete. Renaming the folder forces Windows to create a clean one on the next update check.
Yes, with one caveat. You need to stop the Windows Update service first, otherwise Windows will reject the deletion. Once stopped, you can rename or delete the folder entirely. Windows recreates it automatically. You will not lose installed updates, personal files, or activation data. The only cost is that previously downloaded (but not yet installed) update files will need to be re-downloaded.
Force a shutdown (hold the power button for 5 seconds), boot back into Windows, then open Command Prompt as Administrator and run the service stop and SoftwareDistribution rename sequence above. If the update resumes and gets stuck again at the same point, download it manually from the Microsoft Update Catalog using the KB number shown in Settings > Windows Update > Update History.
Yes. Aggressive antivirus tools, certain VPN clients, and firewall software sometimes block the connections Windows needs to verify update packages or contact Microsoft’s servers. Try temporarily disabling your security software during the update, or set the VPN to exclude Microsoft’s update endpoints. If this is not a direction you want to take regularly, some people compare software tools the same way they evaluate other software service reviews before committing.
