Clearing the Windows Update cache can fix an update that repeatedly downloads, remains stuck, or fails because its local package is incomplete or corrupted. The safest method is to stop the update services, rename or clear the cache folder, restart the services, and let Windows download fresh files.
It is not a universal Windows Update fix. A driver conflict, full system drive, unsupported Windows release, damaged component store, or compatibility hold will return after the cache is rebuilt. Check the failed update and its error code first so you know whether cache cleanup fits the symptom.
When Clearing the Cache Is Worth Trying
The Windows Update cache is a strong suspect when:
- A download remains at the same percentage for an unusually long time.
- Windows repeatedly downloads the same KB update.
- An update failed after the download was interrupted.
- The error specifically refers to missing or corrupted update files.
- Windows Update immediately reuses a package that has already failed.
- The update process never moves from downloading to installation.
Cache clearing is less likely to help when:
| Symptom | More likely area to investigate |
|---|---|
| A feature update rolls back after restarting | Drivers, firmware, compatibility, or setup logs |
| The download never begins on any network | Windows Update services, policy, or connectivity |
| Installation fails with the same percentage and code every time | Servicing stack, component store, or the specific KB |
| Windows reports insufficient space | Storage on the system and reserved partitions |
| The PC runs an unsupported Windows release | Upgrade path rather than repeated cache resets |
| The update is actively installing after a restart | Wait and do not delete update files |
Record the KB number and error code under Settings > Windows Update > Update history before changing anything. That information is harder to reconstruct after several repair attempts.
What the Windows Update Cache Contains
The main working folder is:
C:\Windows\SoftwareDistributionIts Download subfolder stores downloaded update data. Other parts of SoftwareDistribution hold Windows Update working information and history used by the client.
Another folder often included in a deeper reset is:
C:\Windows\System32\catroot2catroot2 supports Windows cryptographic and update operations. It is not the same as the catroot folder. Never delete or rename catroot while following a Windows Update guide.
Windows recreates the required cache folders after the services restart. Clearing them does not uninstall updates that are already installed, remove applications, deactivate Windows, or delete personal files. Windows may need to scan and download packages again, so the first update check can take longer.
Before You Remove Any Update Files
Restart Windows once and check for updates again. A restart can finish a pending service transition without altering the cache.
Do not clear folders while Windows displays Working on updates, Installing, or Do not turn off your computer. Interrupting an active installation is different from resetting a failed download and can damage the servicing state.
Also make sure that:
- The PC is connected to power.
- The internet connection is stable.
- The system drive has usable free space.
- You are signed in with an administrator account.
- Important work is saved before services are stopped.
Start with the targeted method below. Use the deeper reset only when Windows Update still fails or the cache folders cannot recover normally.
Clear the Download Cache With File Explorer
This method removes downloaded packages without immediately resetting every Windows Update data folder.
Stop the update services
- Press
Windows + R. - Enter
services.mscand press Enter. - Find Windows Update.
- Right-click it and select Stop.
- Find Background Intelligent Transfer Service and stop it when it is running.
BITS transfers update data in the background. Stopping both services reduces the chance that Windows will lock a file while you clear the download folder.
Remove the downloaded packages
Open File Explorer and enter this location in the address bar:
C:\Windows\SoftwareDistribution\DownloadSelect the contents of the Download folder and delete them. Delete what is inside the folder, not personal files elsewhere on the drive.
An administrator prompt is normal. A “file in use” message usually means an update service is still active. Return to Services and confirm that Windows Update and BITS stopped. Do not change ownership or permissions on the Windows folder to force deletion.
Restart the services and test
Return to Services and start Background Intelligent Transfer Service and Windows Update. Restart the PC, then open:
Settings > Windows Update > Check for updates
Windows should scan and download a fresh copy of the required package. Stop here when the update completes. There is no benefit in performing a deeper reset after the problem is solved.
Reset SoftwareDistribution and Catroot2
Use this method when the targeted download cleanup does not help, the same cache error returns, or Windows Update metadata appears stuck.
Open Start, search for Command Prompt, choose Run as administrator, and approve the prompt.
Stop the relevant services:
net stop wuauserv
net stop bits
net stop cryptsvcRename the two working folders:
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.oldRenaming is safer than immediately deleting the entire folders because the old data remains available until the new cache is proven to work.
When Windows reports that the destination already exists, a previous SoftwareDistribution.old or catroot2.old folder is present. Do not keep repeating the command. Inspect the existing backup and use a different suffix, such as .old2, if you need to preserve it.
Start the services again:
net start cryptsvc
net start bits
net start wuauservRestart Windows and check for updates. New SoftwareDistribution and catroot2 folders should appear automatically.
Keep the .old folders until Windows Update scans and installs successfully. Once the PC is working normally and you do not need them for diagnosis, they can be removed with administrator permission.
Understand Common Command Results
The reset commands do not always return identical messages on every PC.
The service is not started
This means that service was already stopped. Continue to the next stop command. It does not mean the reset failed.
Access is denied
The terminal is probably not elevated. Close it and reopen Command Prompt with Run as administrator.
The process cannot access the file
One of the update services or another servicing process still has the folder open. Recheck the services and restart Windows before trying again. Do not force the operation while an installation is active.
A duplicate file name exists
The .old folder from an earlier reset already exists. Rename the current folder with another unique suffix rather than overwriting an unknown backup.
A service will not start again
Restart Windows. If the service remains stopped, open services.msc, check its startup configuration and record any service error. A disabled service or policy problem needs separate correction.
What to Expect After the Reset
The Windows Update page may appear busy or empty during its first scan because the client is rebuilding local data. Let the scan finish before deciding that the reset failed.
You may notice:
- A longer first update check
- Previously downloaded packages downloading again
- Fresh
SoftwareDistributionandcatroot2folders - Higher temporary network, CPU, or disk activity
- A restart request after the update installs
The reappearance of SoftwareDistribution is expected. Windows needs that folder and creates it again. The test is whether the update now downloads and installs, not whether the folder stays deleted.
When the Same Update Still Fails
Repeatedly clearing the cache after it has already rebuilt adds no value. Use the stage and error code to choose the next check.
Run the Windows Update troubleshooter
Open:
Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run
Let the troubleshooter finish, apply its recommendations, and restart if requested.
Check the update type and error code
Return to Windows Update > Update history. A cumulative KB failure, driver update, and feature upgrade are different problems.
A major upgrade that rolls back with 0xC1900101 usually points toward a driver or hardware compatibility issue. Follow the targeted checks in Install Error 0xC1900101: How to Fix It instead of clearing the cache again.
An old Windows 11 release can also need a version-specific recovery path. The Windows 11 22H2 Won’t Update guide explains why cache deletion alone may not restore an unsupported release.
Repair the Windows component store
Open Command Prompt as administrator and run:
DISM /Online /Cleanup-Image /RestoreHealthAfter DISM completes, run:
sfc /scannowRestart and test Windows Update. These commands address component-store and protected system-file problems, not corrupted downloads, which is why they come after the cache test.
Use Windows 11’s repair reinstall
Current Windows 11 versions can reinstall the same version through Windows Update while preserving applications, files, and settings. Open:
Settings > System > Recovery > Fix problems using Windows Update > Reinstall now
This is a deeper repair for damaged Windows components and should not be the first response to one failed download. The option may be unavailable on managed computers or some older Windows builds. My guide to reinstalling the current Windows version explains the requirements and process.
Mistakes That Can Make the Problem Worse
- Do not clear the cache as routine maintenance. Windows manages it automatically.
- Do not interrupt an update that is actively installing.
- Do not rename the
catrootfolder when the procedure specifiescatroot2. - Do not download unknown “Windows Update reset” scripts.
- Do not disable Windows Update to prevent the cache from returning.
- Do not repeatedly reset the same folders when the error code points to a driver, storage, policy, or compatibility problem.
Cache clearing is most valuable as a controlled diagnostic step. A successful fresh download confirms that the local package was the problem. A repeated failure after a clean rebuild is evidence to stop resetting the cache and investigate the exact update, error code, or Windows component that is failing.
