Record the update symptom before resetting anything
| What you see | Best first evidence |
|---|---|
| Download is stuck at 0% or 100% | Internet connection, free storage, restart and Windows Update troubleshooter |
| Install fails with an error code | Write down the exact code and KB number before changing components |
| Update downloads but fails after restart | Update history, available space, driver compatibility and system-file health |
| Only one KB keeps failing | Check whether Microsoft documents a known issue and whether the correct package applies to your build |
Start with the low-risk checks
1Restart and retry once
Save your work and restart Windows. Then open Settings → Windows Update and check again. A restart clears pending processes without changing the update database.
2Check connection and storage
Make sure the PC has a working internet connection and enough free space for the update. If the same percentage has not changed for a long time, note the percentage and the update name instead of repeatedly forcing shutdowns.
3Run the Windows Update troubleshooter
Use Settings → System → Troubleshoot → Other troubleshooters → Windows Update. If it reports a specific issue, use that result to decide the next step.
If you have an error code, keep it attached to the problem
Error codes such as 0x8007000d, 0x800705b4, 0x80240034, 0x800f0922 or 0xC1900101 do not all mean the same thing. Search the exact code together with the KB number and Windows build before applying a generic reset.
Open Windows Update → Update history and record the failed KB. That is much better evidence than “Windows Update is broken.”
If system corruption is plausible, repair Windows files before resetting the update cache
Open an Administrator terminal. Microsoft recommends DISM before SFC in this repair sequence.
DISM.exe /Online /Cleanup-image /RestorehealthInspect this DISM command in Tools →
sfc /scannowInspect this SFC command in Tools →
Wait for each command to finish, restart Windows, then retry the original update. Do not call the issue solved only because DISM or SFC completed successfully; the update itself must install.
Advanced: reset Windows Update working folders only when the simpler checks fail
This step requires an Administrator Command Prompt and temporarily stops Windows Update services. It renames the update working folders so Windows can create clean copies. Save work first and do not use this as the first fix for every update error.
net stop bits
net stop wuauserv
ren %systemroot%\softwaredistribution softwaredistribution.bak
ren %systemroot%\system32\catroot2 catroot2.bak
net start bits
net start wuauservRestart the PC after the commands finish, then check for updates again. If a service refuses to stop/start or the folders cannot be renamed, stop and investigate that error instead of stacking more commands.
When one update still fails
- Check the exact KB in Microsoft Update history/support for known issues.
- If the failure is driver-related, update the affected device from the PC/device manufacturer rather than installing unrelated drivers.
- If Windows Update remains broken after DISM/SFC and a supported component reset, consider an in-place repair path before a clean reinstall.
Verify the repair
- The failed KB moves from Failed to Successfully installed, or Windows reports no applicable update.
- Windows Update completes a new scan without immediately returning the same error.
- The PC restarts normally and the update history matches the installed build.
- If you renamed update folders, new SoftwareDistribution/catroot2 working data is created automatically.
What came from the older ITFixLab archive
The archive contained a Windows Update error guide and a separate repair-command builder. This page keeps the strongest sequence—troubleshooter → DISM/SFC → update-component reset—but removes the old one-error focus so it can serve broader “stuck/failed” searches. The old command-builder idea stays parked for the Legacy Asset Recovery objective.
Frequently asked questions
Should I reset Windows Update components first?
No. Start with the exact error/KB, restart, storage/connection checks and the Windows Update troubleshooter. Resetting working folders is an advanced step for persistent update-component problems.
Should I run DISM or SFC first?
For the standard Windows image-repair sequence, Microsoft recommends DISM first and SFC after it.
Will renaming SoftwareDistribution delete my personal files?
The standard reset targets Windows Update working data, not your Documents or Photos, but you should still back up important work before advanced system repair.
Sources and review notes
Troubleshooting order was reviewed against Microsoft: Troubleshoot problems updating Windows · Microsoft: DISM and SFC. Hardware, driver and menu names can vary by PC, accessory and Windows build.