How to Reset Windows Update Components Safely in Windows 11

If Windows Update repeatedly downloads the same files, fails with cache-related errors, or remains stuck after the normal troubleshooter, resetting the update cache can help. The important part is to use the limited Microsoft-documented reset, not the much longer scripts still copied around the Internet.

This procedure renames the Windows Update cache folders so Windows can create clean replacements after a restart.

Before you reset anything

Run the Windows Update troubleshooter first and restart the PC. If the update has a specific error code, note it down. A cache reset is useful for damaged or incomplete update data, but it will not fix every update failure.

Open an elevated Command Prompt

1. Open Start and type cmd.
2. Right-click Command Prompt.
3. Select Run as administrator.
4. Approve the User Account Control prompt.

Stop the update services

Run these commands one at a time:

net stop bits
net stop wuauserv

If a service is already stopped, that message is not necessarily an error.

Rename the update cache folders

Warning: If a rename reports access denied or an existing .bak folder, stop and check the error. Do not delete an existing backup or change service permissions to force the command through. Restart any services you stopped before leaving the procedure.

Now run:

ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\System32\catroot2 catroot2.bak

Renaming is preferable to permanently deleting the folders because you retain a temporary fallback copy until Windows Update is working again.

Restart the services

Run:

net start bits
net start wuauserv

Close Command Prompt and restart Windows. Then open Settings > Windows Update and select Check for updates.

What happens after the reset?

Windows creates new SoftwareDistribution and catroot2 folders automatically. The first update check may take longer because Windows has to rebuild local update information.

You may also notice that some locally displayed Windows Update history information changes. Installed updates themselves are not removed by this cache reset.

What you should not reset casually

Older Windows Update repair guides often include commands that change BITS and Windows Update service permissions, delete downloader databases, reset Winsock, or re-register a large list of system DLLs. Microsoft specifically warns that aggressive service-security resets can overwrite existing ACLs. Those steps are not a sensible first-line repair on a normal Windows 11 PC.

If the reset does not fix Windows Update

Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow. If Windows itself appears damaged, use Settings > System > Recovery > Fix problems using Windows Update when available. That reinstalls the current Windows version while preserving apps, files, and settings.

Why renaming the folders works

SoftwareDistribution stores temporary Windows Update downloads and local servicing data. catroot2 is used by Windows during update package verification. When either cache becomes inconsistent, Windows can repeatedly retry a damaged download or fail before installation begins.

Renaming the folders does not “repair Windows” by itself. It simply forces the update system to rebuild those working folders. That is why this procedure is most useful when the same download or verification problem keeps returning.

Clean up the backup folders later

Once Windows Update has worked normally for several days and you are confident the problem is resolved, the old .bak folders can be removed with administrator permission to reclaim space. Do not remove them immediately after the reset; keeping them briefly makes the change easier to reverse while you verify that servicing is healthy.

Official references