How to Reset Windows Update Components and Fix Stuck Updates

Share
A laptop displays the Windows Update page in Windows Settings.

Resetting Windows Update components can fix updates that are stuck, repeatedly failing, or using damaged cache data. The repair stops the update services, renames the `SoftwareDistribution` and `catroot2` folders, restarts the services, and lets Windows rebuild clean working folders; it does not delete personal files or installed programs. Use it on Windows 10 or Windows 11 after checking for low disk space, a pending restart, an update policy, or a broader system failure.

Is resetting Windows Update the right fix?

A component reset is appropriate when Windows Update remains stuck at a percentage, repeatedly retries the same update, fails with changing installation errors, or reports that update files are missing or damaged. It is also a reasonable next step when the Windows Update troubleshooter has not repaired the problem and the failure began after an interrupted download or shutdown.

Common symptoms include:

Windows Update is stuck downloading or installing an update
Updates fail, then appear again on the next check
Windows Update repeatedly retries the same update
The update cache appears to contain incomplete or corrupted downloads
Symptom

These symptoms can appear after an interrupted download or shutdown, but they do not prove that the cache is the cause. Resetting the components will not repair a failing hard drive or SSD, create free disk space, correct an incompatible driver, bypass an organization’s update policy, or solve an update blocked by unsupported hardware. It also will not make an update install if Microsoft has paused or withdrawn that update.

If the error appears only for a particular driver, feature, or application, investigate that item first. If the computer cannot start reliably, shows disk errors, or has severe system-file corruption, repair those problems before rebuilding the update cache.

A laptop shows a Windows Update error message in the Settings app.

What to check before changing anything

The procedure applies to supported editions of Windows 10 and Windows 11. You need an account with Administrator rights because the commands stop protected services and rename system folders. Save open work before starting; you will restart Windows after the reset.

Before opening Command Prompt, check these items:

  • Record the current Windows Update error code and the name or number of the update that fails. A code such as 0x800f081f or 0x8024a105 can point to a different fix if the reset does not work.
  • Restart the computer once if Windows says a restart is pending. A pending restart can prevent a new update transaction from starting.
  • Check that the system drive has enough free space for the update and its temporary files. Open File Explorer, select This PC, and inspect the free space on the Windows drive.
  • If the computer contains unusually important local files, make sure they are backed up. The reset normally affects only update working data, but a backup is a sensible safeguard before system maintenance.
  • If the computer is managed by an employer or school, check with the administrator before changing update services. Policy can intentionally prevent updates or control their source.

Do not delete the cache folders at this stage. Renaming them is safer because Windows can build new folders while the old data remains available until you decide it is no longer needed.

Reset Windows Update components step by step

Run the procedure in an elevated Command Prompt, not in a normal Command Prompt window. The commands stop Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and Windows Installer. They then rename the two working folders that Windows will recreate.

Do not close Command Prompt halfway through the procedure or restart the computer while services are stopped. If a command reports that a service is not running, continue; if Windows says a folder is in use, review the service-stop results before proceeding.

  1. Open the Start menu, type Command Prompt, right-click it, and select Run as administrator. Approve the User Account Control prompt.
  2. Stop the services that can hold the update files open.
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver
Command Prompt (Run as Administrator)

Each service should report that it was stopped successfully. If a service was already stopped, continue. If a service refuses to stop, do not rename its folder yet; restart Windows and repeat the procedure, or investigate the service error first.

  1. Rename the update download and signature-cache folders. Renaming keeps the old folders as a fallback and avoids permanently deleting data during the reset.
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old
Command Prompt (Run as Administrator)

A successful command returns to the prompt without an error. If Windows reports that the file or folder is in use, one of the services is still holding it open. Recheck the stop commands, then try again. Do not rename catroot; the folder to rename is specifically catroot2.

  1. Start the services again in the same elevated window.
net start msiserver
net start cryptsvc
net start bits
net start wuauserv
Command Prompt (Run as Administrator)

Each service should report that it started successfully. If a service fails to start, copy the exact message and error code. The reset is not complete until the services needed by Windows Update can start normally.

  1. Close Command Prompt and restart Windows. The first update check can take longer than usual because Windows must create fresh SoftwareDistribution and catroot2 folders and rebuild its local update data.

The .old folders can remain temporarily. After you confirm that updates work, Windows usually no longer needs them. You may remove them later from an elevated Command Prompt if they occupy substantial space, but do not remove them while an update is installing or while troubleshooting the reset.

A Windows computer displays the SoftwareDistribution folder associated with Windows Update in File Explorer.

How to confirm Windows Update is working again

After the restart, check for updates through Settings.

Windows 11: Settings > Windows Update
Windows 10: Settings > Update & Security > Windows Update
Settings path

Select Check for updates, then allow the scan and installation to finish without forcing a shutdown.

A successful reset normally produces one of these results:

  • Windows finds and downloads the pending update instead of remaining stuck at the previous point.
  • The update installs and requests a restart.
  • Windows reports that you are up to date after completing a fresh scan.

The first scan can take longer than a routine check while Windows recreates the cache. That alone does not indicate another failure. Restart again if Windows requests it, then check the update history to confirm the update shows as installed.

If the same error code appears immediately, the reset did not address the cause. Record the code and the update’s knowledge base number, if shown. If Windows Update now scans successfully but one update still fails, the problem is more likely tied to that package, a prerequisite, a driver, system files, or servicing-stack state than to the general update cache.

The Windows Update settings page shows the Check for updates control.

What to do when the reset does not fix the error

Start with the exact error code rather than repeating the reset. Search Microsoft’s support documentation for that code and the update’s knowledge base number. Codes related to insufficient space, a missing source file, a blocked connection, or unsupported hardware each require different repairs. Repeating the cache reset will not correct those conditions.

Check system files from an elevated Command Prompt. Run the servicing command first, let it finish, and then run System File Checker:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc.exe /scannow
Command Prompt (Run as Administrator)

DISM may use Windows Update as a source, so it can fail if the update system or network source is unavailable. If it reports that source files cannot be found, use a matching Windows installation source according to Microsoft’s documented repair procedure rather than choosing a random image.

If the computer is managed, inspect update policies under Settings > Accounts > Access work or school and ask the organization’s administrator about its update server or deferral rules. Avoid deleting policy entries or registry values without knowing who controls them.

For errors that mention storage, run the drive manufacturer’s diagnostic tools and check Windows Event Viewer for disk warnings. For driver-specific failures, update or temporarily remove the affected driver through the manufacturer’s supported process.

If Windows still cannot install updates after system-file repair and the hardware and policies are sound, use a Windows repair installation that keeps personal files and apps, when that option is offered for your edition and installation media. A clean installation is a later measure, not the normal next step for a damaged update cache. Back up your files before any repair installation and verify that the installation media matches the installed Windows edition and language.

Conclusion

Run one fresh update check after the restart. If it still fails, use the recorded error code to choose the next repair instead of repeating the cache reset; keep the `.old` folders until the update installs successfully, then remove them only if you need the disk space. If system-file repair and hardware and policy checks do not resolve the issue, consider a repair installation before wiping Windows.

Frequently Asked Questions

Will resetting Windows Update delete my files or programs?

No. The procedure stops update services and renames Windows Update’s working folders; it does not target personal files or installed applications. Save open work and keep a current backup before making system changes.

Can I delete SoftwareDistribution and catroot2 instead of renaming them?

Renaming is the safer first choice because it preserves the old folders temporarily. After updates work and no rollback is needed, you can remove the `.old` folders from an elevated Command Prompt. Do not delete or rename the folders while their services are running.

What if Windows says a folder is in use?

A service still has an open file handle. Confirm that `wuauserv`, `bits`, `cryptsvc`, and `msiserver` stopped successfully, then try the rename again. If the lock remains, restart Windows and repeat the commands from an elevated Command Prompt.

Read more