Windows Update is one of those background systems you barely notice—until it stops working. When updates get stuck at 0%, fail with cryptic error codes, loop endlessly, or refuse to install, the problem is often caused by damaged update cache files, stalled services, or corrupted download data. Resetting Windows Update components manually clears those problem areas and gives Windows a fresh path to download and install updates again.
TLDR: Manually resetting Windows Update means stopping update-related services, clearing the update cache, renaming key system folders, and restarting the services. This process can fix many common Windows Update errors without reinstalling Windows. You should run the commands from an elevated Command Prompt or Windows Terminal. Always restart your PC afterward and try Windows Update again.
Why Windows Update Components Sometimes Need a Reset
Windows Update depends on several moving parts working together. It uses background services, temporary download folders, cryptographic verification files, and network communication with Microsoft’s servers. If any of these components become stuck, outdated, or corrupted, the update process may fail.
Common symptoms include:
- Updates stuck on “Downloading” or “Installing”
- Repeated failed update attempts
- Error codes such as 0x80070002, 0x80070003, 0x8024402c, or 0x800f081f
- Windows Update saying your device is missing important fixes
- Update history showing the same failed update again and again
- Microsoft Store apps failing to update because background update services are broken
The good news is that a manual reset does not remove your files, apps, or settings. It mainly clears temporary update data and restarts services that Windows uses to find, download, verify, and install updates.
Before You Begin
Although this process is safe when followed carefully, it does involve system services and protected folders. Take a moment to prepare before running commands.
- Use an administrator account. Standard accounts cannot stop system services or rename protected folders.
- Save your work. You will restart the computer at the end.
- Keep your device plugged in. If you are using a laptop, avoid running out of battery during repairs.
- Check your internet connection. Windows will need to download fresh update files later.
- Consider creating a restore point. This is optional, but it gives you a safety net.
To open the right tool, click Start, type cmd or Windows Terminal, then choose Run as administrator. If a User Account Control prompt appears, select Yes.
Step 1: Stop Windows Update Related Services
The first step is to stop the services that may be using update files. If these services are still running, Windows may prevent you from renaming or clearing update folders.
In the elevated Command Prompt or Terminal window, run these commands one at a time:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserverHere is what those services do:
- wuauserv: The main Windows Update service.
- BITS: Background Intelligent Transfer Service, which downloads files efficiently in the background.
- cryptsvc: Cryptographic Services, used to verify update signatures and certificates.
- msiserver: Windows Installer service, used during some software and update installations.
If you see a message saying a service is not started, that is usually fine. It simply means that particular service was already stopped.
Step 2: Rename the SoftwareDistribution Folder
The SoftwareDistribution folder stores temporary Windows Update files, including downloaded update packages and update history data. If the contents become corrupted, Windows may keep trying to install bad or incomplete files.
Instead of deleting the folder outright, it is better to rename it. Windows will automatically create a new one later.
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldThis command preserves the old folder as a backup. After Windows Update begins working again, you can delete SoftwareDistribution.old later if you need the disk space. Keep in mind that renaming this folder may clear the visible update history in the Settings app, but it does not uninstall updates that are already installed.
Step 3: Rename the Catroot2 Folder
The Catroot2 folder is another important Windows Update component. It stores catalog files used to validate update packages. When this folder contains damaged or mismatched data, updates can fail during verification.
Run this command:
ren C:\Windows\System32\catroot2 catroot2.oldDo not confuse catroot2 with catroot. You should only rename catroot2. Windows will rebuild it automatically when the cryptographic service starts again.
Step 4: Reset the BITS Queue
BITS handles background file transfers, including Windows Update downloads. Sometimes a stuck or broken transfer job can block new updates from downloading properly.
Use this command to clear existing BITS jobs:
bitsadmin /reset /allusersYou may see a message confirming that transfer jobs were canceled. That is expected. If the command says there are no jobs, you can continue.
Step 5: Re-register Important Windows Update Files
On many modern Windows 10 and Windows 11 systems, the previous steps are often enough. However, if Windows Update is deeply broken, re-registering certain system files can help restore update-related functions.
Run the following commands one at a time:
regsvr32 /s atl.dll
regsvr32 /s urlmon.dll
regsvr32 /s mshtml.dll
regsvr32 /s actxprxy.dll
regsvr32 /s jscript.dll
regsvr32 /s vbscript.dll
regsvr32 /s scrrun.dll
regsvr32 /s msxml3.dll
regsvr32 /s wuapi.dll
regsvr32 /s wuaueng.dll
regsvr32 /s wucltui.dll
regsvr32 /s wups.dll
regsvr32 /s wups2.dll
regsvr32 /s wuwebv.dll
regsvr32 /s qmgr.dll
regsvr32 /s qmgrprxy.dll
regsvr32 /s wucltux.dll
regsvr32 /s muweb.dll
regsvr32 /s wuwebv.dllThe /s switch runs each registration silently, so you may not see confirmation pop-ups. That is normal. If one or two commands fail on a newer version of Windows, continue with the remaining steps; Microsoft has changed or removed some older Windows Update components over time.
Step 6: Reset Network Configuration
Windows Update also depends on reliable network communication. Proxy settings, DNS issues, or a damaged Winsock catalog can prevent your device from reaching Microsoft’s update servers.
Run these commands:
netsh winsock reset
netsh winhttp reset proxy
ipconfig /flushdnsThe first command resets the Windows networking socket catalog. The second clears WinHTTP proxy settings, which Windows Update uses separately from your browser. The third clears saved DNS records so Windows can request fresh address information.
Step 7: Restart the Services
Now that the cache folders have been renamed and the transfer queue has been reset, start the update-related services again:
net start wuauserv
net start bits
net start cryptsvc
net start msiserverIf all goes well, the services should start successfully. Windows will recreate the missing update folders in the background as needed.
Step 8: Restart Your Computer
Even if the commands complete successfully, do not skip the reboot. Restarting clears locked files, reloads services, and allows Windows to rebuild update databases cleanly.
After restarting, go to:
- Settings
- Windows Update
- Check for updates
The first scan may take longer than usual because Windows is rebuilding its update cache. Be patient. If updates begin downloading again, the reset worked.
Optional: Run DISM and System File Checker
If Windows Update still fails after a manual reset, the issue may be deeper than the update cache. Corrupted Windows system files can prevent updates from installing correctly. Two built-in repair tools are especially useful: DISM and SFC.
Open an elevated Command Prompt or Windows Terminal and run:
DISM /Online /Cleanup-Image /RestoreHealthWait for the process to complete. It can take several minutes and may appear to pause at certain percentages. After it finishes, run:
sfc /scannowDISM repairs the Windows component store, while SFC checks and repairs protected system files. Together, they can fix problems that a standard Windows Update reset cannot.
What If the Folder Rename Fails?
If you receive an “Access is denied” or “The process cannot access the file” message, one of the services may still be running. Try stopping the services again:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserverIf that still does not work, restart the computer and immediately open Command Prompt as administrator before checking for updates. Then repeat the commands. In stubborn cases, booting into Safe Mode can help because fewer services and background processes are active.
Should You Delete the Old Folders?
After the reset, you may notice SoftwareDistribution.old and catroot2.old. These are backup copies created during the process. If Windows Update works properly for a few days, you can delete them to recover space.
However, there is no need to rush. Keeping them temporarily is useful in case you want to compare logs or confirm that Windows has recreated the new folders correctly.
When a Manual Reset Is Not Enough
A manual Windows Update reset fixes many update failures, but not all of them. If updates still fail, consider these possibilities:
- Low disk space: Feature updates may require many gigabytes of free space.
- Third-party antivirus interference: Security software can sometimes block update files.
- Damaged Windows image: DISM and SFC may be required.
- Driver conflicts: Outdated storage, graphics, or chipset drivers can interrupt updates.
- Microsoft server issues: Occasionally, the problem is not on your device.
- Unsupported hardware: Some older PCs may not support the latest Windows feature updates.
You can also use the built-in Windows Update troubleshooter from Settings. While it is not as thorough as a manual reset, it can detect simple configuration problems automatically.
Final Thoughts
Manually resetting Windows Update components may look technical, but the logic behind it is straightforward: stop the services, clear the broken temporary data, reset transfer and verification systems, then start fresh. It is a practical repair method because it targets the areas where Windows Update most often gets stuck.
If your PC has been failing updates for days or weeks, this process can feel like opening a jammed door. Once the update cache is rebuilt and the services are restarted, Windows often returns to normal without a full reinstall or major repair. Take the steps carefully, restart when finished, and let Windows Update perform a fresh scan. In many cases, that clean start is exactly what your system needs.
