Windows Update can fail because its cache is damaged, its services are stopped, or its component store needs repair. The built-in troubleshooter is often the first step; if that does not fix it, move to the short command reset. Microsoft Support’s Windows Update troubleshooting page, plus Microsoft’s DISM and SFC documentation, cover the repair path this article uses.
What does a Windows Update reset fix?
A Windows Update reset clears the local update cache and restarts the services that move, catalog, and register update files. It can resolve stuck downloads, repeat-fail scans, and stalled installs on Windows 10 and Windows 11 personal PCs. If the failure returns, move to DISM, SFC, or manual KB installation instead of repeating the same reset.
Likely causes
- Corrupted SoftwareDistribution cache files.
- Broken catroot2 data.
- Stopped or blocked BITS, Cryptographic Services, or wuauserv.
- Damaged Windows component store or protected files.
- Policy or permission blocks on managed devices.
If a PC keeps downloading the same cumulative update and then fails again after a restart, that usually points to a damaged cache or stalled service, not to a need for a full reinstall.
If a Windows 11 laptop reaches 100% download but never finishes installation, the local cache or service state is often the part that needs a reset, even when the update payload itself is fine.
Should you use the Windows Update troubleshooter first?
Yes. Start with the built-in Windows Update troubleshooter before command-line resets, because it can repair service state and update database issues without manual folder changes. Microsoft Support’s Fix problems with Windows Update page recommends using the troubleshooter first, and the same Microsoft guidance is the least invasive starting point for Windows 10 and Windows 11.
- Open Settings > System > Troubleshoot > Other troubleshooters on Windows 11, or the equivalent troubleshooting page on Windows 10.
- Run Windows Update.
- Apply any fix it reports, then try Windows Update again.
- If it reports that services were repaired, retry the update before moving on.
If the troubleshooter says it fixed something and the next scan works, stop there. If it still cannot connect, download, or install, move to the command reset.
Which reset steps match the error you see?
Use the shortest command set that fits the symptom. The goal is to clear the specific part of Windows Update that is stuck, while avoiding extra changes on healthy services or folders. Microsoft’s DISM and SFC documentation supports the repair steps when a cache reset alone is not enough, and Microsoft Update Catalog supports manual KB installation when local repair fails.
| Symptom | Minimal command set | What it resets | How to verify success |
|---|---|---|---|
| Download stuck, same update keeps looping | net stop wuauserv net stop bits net stop appidsvc net stop cryptsvc net stop msiserver ren %windir%\SoftwareDistribution SoftwareDistribution.bak net start msiserver net start cryptsvc net start appidsvc net start bits net start wuauserv |
Update cache, app identity policy processing, installer service state, and transfer queue | Windows Update can start a fresh download and no longer reuses the stuck package |
| Install fails during verification or staging | net stop wuauserv net stop bits net stop appidsvc net stop cryptsvc net stop msiserver ren %windir%\System32\catroot2 catroot2.bak net start msiserver net start cryptsvc net start appidsvc net start bits net start wuauserv |
Catalog and signature data | Update checks move past the same verification step |
| Windows Update service will not stay running | net stop wuauserv net stop bits net stop appidsvc net stop cryptsvc net stop msiserver net start msiserver net start cryptsvc net start appidsvc net start bits net start wuauserv |
Service state only | Services show as running in Services or from command output |
| Managed-device policy block | gpresult /h %temp%\gp.html sc query wuauserv sc query bits |
Confirms policy, service control, or WSUS management rather than cache corruption | Policy report shows update control, or services are disabled by management |
| System files may be damaged too | DISM /Online /Cleanup-Image /RestoreHealth SFC /scannow |
Component store, then protected files | Both commands finish without unrepaired corruption |
| Device type | What may block the reset | Best next step |
|---|---|---|
| Windows 10/11 user PC | Usually nothing, if Command Prompt runs as administrator | Use the command reset, then verify and reboot |
| Managed device | Policy, service control, or WSUS settings can block changes | Confirm admin rights, then check whether policy or device management must change first |
How do you reset Windows Update with Command Prompt?
Open Command Prompt as administrator, then stop the update-related services, rename the update cache folders, and start the services again. The sequence below includes wuauserv, bits, cryptsvc, appidsvc, and msiserver. Microsoft’s service and repair documentation supports the use of DISM and SFC after the reset if corruption remains.
wuauserv is the Windows Update service, bits handles background transfers, cryptsvc manages catalog and signature processing, appidsvc supports application identity policy processing, and msiserver is the Windows Installer service. Stopping appidsvc and msiserver matters when update installation or repair is blocked by policy checks or installer activity, especially on systems that are still actively processing package changes.
- Open Command Prompt with Run as administrator.
- Run:net stop wuauserv
net stop bits
net stop cryptsvc
net stop appidsvc
net stop msiserver - Run:ren %windir%\SoftwareDistribution SoftwareDistribution.bak
ren %windir%\System32\catroot2 catroot2.bak - Run:net start msiserver
net start appidsvc
net start cryptsvc
net start bits
net start wuauserv - Open Windows Update and run Check for updates again.
You can usually test before rebooting. If Windows Update opens, begins a new scan, and starts a fresh download, the reset worked well enough to continue. If the same error returns immediately, do not keep renaming the folders again. Move to DISM or manual installation.
Can you reset Windows Update without restarting right away?
Yes, you can check the service restart and retry Windows Update before rebooting. The useful test is whether the scan runs and the download begins. If the error is gone but the install still wants a restart, finish the reboot later. If the service will not stay started, a reboot is the next check.
What commands reset Windows Update components?
The core reset commands are the service stop and start commands, plus the folder renames for SoftwareDistribution and catroot2. Those are the commands that clear the local update cache and rebuild update catalog state. If the reset still fails, Microsoft’s DISM documentation and SFC documentation support the next repair step.
A full reset sequence usually looks like this:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop appidsvc
net stop msiserver
ren %windir%\SoftwareDistribution SoftwareDistribution.bak
ren %windir%\System32\catroot2 catroot2.bak
net start msiserver
net start appidsvc
net start cryptsvc
net start bits
net start wuauserv
Do not rename the folders while the services are still active. That is the part that most often causes file-in-use errors.
What if system files are damaged?
If the reset does not hold, repair the component store first with DISM, then check protected files with SFC. Microsoft’s DISM page for /Online /Cleanup-Image /RestoreHealth and Microsoft’s SFC page for sfc /scannow are the direct references for this repair sequence. DISM comes first because SFC depends on a healthy source of system files.
- Open Command Prompt as administrator.
- Run:DISM /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish completely.
- Run:sfc /scannow
- If either tool reports that files were repaired, restart the PC.
- Run Windows Update again after the reboot.
If DISM reports that a restart is required, do that before rechecking Windows Update. A no-reboot retry can hide a repair that has not been applied yet.
When should you install the update manually?
Use the Microsoft Update Catalog when the same KB keeps failing after a clean reset, or when the machine needs a specific patch faster than repeated command attempts can get it installed. Microsoft Update Catalog is the direct source for matching KB packages by number and architecture, which makes it the most precise fallback when the local update engine is not the problem.
- Open Microsoft Update Catalog.
- Search for the exact KB number shown in Windows Update history or the error details.
- Download the package that matches the system architecture.
- Run the downloaded .msu file.
- Restart if the installer asks for it.
If the manual KB install works, the update engine problem was likely local rather than with the patch itself.
What if Windows Update still fails after resetting it?
If the reset, DISM, SFC, and manual KB install all fail, the next step is usually a deeper repair or an admin-managed change. On managed PCs, policy or WSUS can block service changes, folder renames, or update source changes. On a personal PC, the next tier is often a repair install or Reset This PC.
- Check whether the device is managed by your organization.
- Confirm whether Windows Update policies or WSUS settings are set by admin control.
- If policy is not the issue, run a deeper repair path such as Reset This PC from Settings > System > Recovery on Windows 11, or Settings > Update & Security > Recovery on Windows 10.
- Choose Keep my files if you need to preserve user data.
- Use Cloud download or Local reinstall if the reset path is the chosen fix.
Let Windows Update finish each cycle before forcing shutdowns. Interrupted installs are one of the easiest ways to leave the cache and catalog in a broken state.
What are the most common Windows Update questions?
How do I manually reset Windows Update?
Open Command Prompt as administrator, stop wuauserv, bits, cryptsvc, appidsvc, and msiserver, rename %windir%\SoftwareDistribution and %windir%\System32\catroot2, then start the services again. That is the shortest manual reset for the cache and catalog components.
How do I reset Windows Update with Command Prompt?
Use an elevated Command Prompt and run the stop-rename-start sequence in that order. After the services come back, return to Windows Update and run a fresh scan. If the same failure remains, move to DISM before repeating the reset.
What commands reset Windows Update components?
The core commands are net stop wuauserv, net stop bits, net stop cryptsvc, net stop appidsvc, net stop msiserver, the two ren commands for SoftwareDistribution and catroot2, and then the matching net start commands. For file repair, add DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow.
How do I completely reset Windows Update?
Stop the update services, rename the cache folders, restart the services, then verify the update scan. If the update still fails, add DISM and SFC. A full reset does not mean a reinstall; it means clearing the local update cache and repairing system files if needed.
What if Windows Update still fails after resetting it?
Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, and if that still does not help, install the KB manually from Microsoft Update Catalog. On managed devices, ask whether policy or WSUS is blocking the reset or the update source.
Sources
- Microsoft Support: Fix problems with Windows Update.
- Microsoft Learn / Docs: DISM operating system image servicing, including /Online /Cleanup-Image /RestoreHealth.
- Microsoft Support / Docs: System File Checker (sfc.exe) and
sfc /scannow. - Microsoft Update Catalog.