How to Reset Windows Update Components Safely (2026 Updated Guide)

Quick answer

Resetting Windows Update components means stopping the update services, deleting their working folders, re-registering the underlying DLLs, and starting the services again. It’s a heavy-handed fix that works when nothing else does — but it’s also the wrong first step for most update errors. Try the built-in troubleshooter and a manual KB install before you reset components. When you do reset, the procedure is the same on Windows 11 24H2 and 23H2, with one folder-name difference noted below.

Before you start

  • This procedure resets all queued Windows Update activity. Any updates currently downloading will need to be downloaded again. That can mean several gigabytes.
  • You will need administrator rights for every command in this guide.
  • This is not a malware fix, a performance fix, a “speed up Windows” fix, or a generic troubleshooting fix. If someone has told you to reset Windows Update components for any reason other than a specific Windows Update problem, get a second opinion.
  • Do not paste random batch files from forum posts and run them. The procedure below is the version Microsoft has documented in their own support content. There are public scripts that automate it; they are mostly fine but they are also where most of the people who break their systems are getting their commands.
  • If the affected device is a work or school laptop managed by your employer, see If you are on a work or school device before doing anything.

What “resetting Windows Update components” actually means

Windows Update is not a single thing. It’s a small ecosystem of services, working folders, registry entries, and supporting DLLs. When that ecosystem gets out of sync — usually because an update was interrupted, a service crashed mid-write, or a third-party tool corrupted a file — the whole thing can stay broken until it’s reset.

Resetting components does five things, in order:

  1. Stops the four Windows Update-related services so files can be modified.
  2. Deletes (or renames) the SoftwareDistribution folder, which stages downloaded updates.
  3. Deletes (or renames) the catroot2 folder, which stores update signature catalogs.
  4. Re-registers the BITS and Windows Update DLLs in case any have decoupled from the registry.
  5. Restarts the four services and refreshes Windows Update.

It is a heavy intervention. The next time you check for updates, Windows has to redownload anything it had been working on, re-fetch the signature catalogs, and rebuild the local update index. That can take 20–60 minutes on a slow connection.

When this is the right move

Reset Windows Update components when:

  • A specific Windows Update error code persists after running the built-in troubleshooter and trying a manual KB install. The most common candidates are , , and .
  • Windows Update has been stuck at “Checking for updates” for more than 24 hours.
  • The Update History shows multiple failed updates with mismatched dates and codes — a signal that the local update database is corrupted.
  • DISM and SFC have completed cleanly but Update is still failing.

When this is the wrong move

Don’t reset if:

  • You haven’t run the Windows Update troubleshooter yet. It’s been genuinely improved over the past two years and resolves a substantial fraction of cases automatically. Skipping it is wasted effort.
  • Your only symptom is one update failing with one error code on first attempt. That’s normal Windows behavior. Try again, and only reset if the same update fails repeatedly.
  • The PC is on metered or slow internet. Resetting forces a redownload of pending updates, which on a slow connection is a multi-hour ordeal you may not want.
  • The error is 0x80070005 (access denied) on a managed device. That points to permissions or Conditional Access policy, and resetting components changes nothing about either. See 0x80070005 access denied.

If none of the cases above describe your situation, this is the right procedure.

The procedure

The procedure below is the documented Microsoft method, with the elements clarified one by one. Run every command from an elevated Command Prompt: press Win, type cmd, right-click Command Prompt, and select Run as administrator.

Step 1 — Stop the Windows Update services

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

What each one is:

  • wuauserv — the Windows Update service itself. Orchestrates everything.
  • cryptSvc — Cryptographic Services. Verifies update signatures.
  • bits — Background Intelligent Transfer Service. Handles the actual file downloads.
  • msiserver — Windows Installer service. Used during package installation.

If any service refuses to stop, it’s almost always wuauserv stuck in the middle of an operation. Wait two minutes and try again. If it still refuses, restart the PC and try once more from the beginning.

Step 2 — Rename the SoftwareDistribution and catroot2 folders

Renaming rather than deleting means Windows treats the folders as missing and rebuilds them, but you keep a recovery option if anything goes wrong.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

If you get “Access is denied” on either rename, one of the services from Step 1 is still running. Confirm with sc query wuauserv (and the others). Wait for them all to be in STOPPED state before proceeding.

Step 3 — Re-register Windows Update DLLs (optional but worth doing)

This step is the one most public scripts skip, and it’s the one that makes the difference for the hardest cases — particularly machines that have been imaged, restored from backup, or migrated. Run this whole block as a single block:

cd /d %windir%\system32
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
regsvr32.exe /s shdocvw.dll
regsvr32.exe /s browseui.dll
regsvr32.exe /s jscript.dll
regsvr32.exe /s vbscript.dll
regsvr32.exe /s scrrun.dll
regsvr32.exe /s msxml.dll
regsvr32.exe /s msxml3.dll
regsvr32.exe /s msxml6.dll
regsvr32.exe /s actxprxy.dll
regsvr32.exe /s softpub.dll
regsvr32.exe /s wintrust.dll
regsvr32.exe /s dssenh.dll
regsvr32.exe /s rsaenh.dll
regsvr32.exe /s gpkcsp.dll
regsvr32.exe /s sccbase.dll
regsvr32.exe /s slbcsp.dll
regsvr32.exe /s cryptdlg.dll
regsvr32.exe /s oleaut32.dll
regsvr32.exe /s ole32.dll
regsvr32.exe /s shell32.dll
regsvr32.exe /s initpki.dll
regsvr32.exe /s wuapi.dll
regsvr32.exe /s wuaueng.dll
regsvr32.exe /s wuaueng1.dll
regsvr32.exe /s wucltui.dll
regsvr32.exe /s wups.dll
regsvr32.exe /s wups2.dll
regsvr32.exe /s wuweb.dll
regsvr32.exe /s qmgr.dll
regsvr32.exe /s qmgrprxy.dll
regsvr32.exe /s wucltux.dll
regsvr32.exe /s muweb.dll
regsvr32.exe /s wuwebv.dll

The /s flag suppresses the success popup for each DLL. You can omit it if you want to see exactly which ones registered cleanly. Errors here are almost always benign — some DLLs are not present on every Windows edition (notably some Windows Server SKUs).

Step 4 — Reset the BITS and Windows Update queues (optional)

netsh winsock reset
netsh winhttp reset proxy

The first command resets the network sockets. The second clears any custom proxy that’s been configured on the WinHTTP service — relevant only if your machine has been on a corporate network with a proxy and is now somewhere else.

Skip this step if you are on a work device using a corporate proxy you need to keep. The proxy reset can break your connection until the proxy is configured again.

Step 5 — Restart the services

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Step 6 — Check for updates

Open Settings → Windows Update and click Check for updates. The first check after a reset is slower than usual — Windows is rebuilding its local catalog. Allow it 5–15 minutes before assuming it’s stuck.

Windows 11 24H2 versus 23H2 differences

The procedure above is identical between 24H2 and 23H2, but two details have shifted:

  • The DeliveryOptimization folder. On 24H2, the equivalent of SoftwareDistribution for peer-to-peer update content lives at C:\Windows\SoftwareDistribution\DeliveryOptimization rather than the older C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization. The procedure above handles both because it operates on the parent SoftwareDistribution folder. There’s nothing extra you need to do.
  • The Windows Update Medic Service (WaaSMedicSvc). On 24H2, this service is more aggressive about restoring Update components automatically. If you find that wuauserv keeps starting itself back up before you can rename folders, stop the Medic service first using sc stop WaaSMedicSvc. It will start itself back up later — that’s intended.

Advanced: when the reset itself fails

If renaming SoftwareDistribution returns an access denied error even after the services have stopped, the underlying cause is usually one of:

  • Antivirus software has the folder locked. Temporarily disable it.
  • A pending file rename operation from a prior failed update is still queued. Restart the PC and run the procedure again from the beginning.
  • The folder is corrupted at the filesystem level. Run chkdsk C: /scan (read-only) and review the output for filesystem errors. Don’t run chkdsk /f or chkdsk /r unless you understand the consequences and have a backup.

If the reset completes but updates still fail, the next stop is DISM and SFC — see How to run DISM and SFC safely. After that, the only remaining step is an in-place repair install of Windows from current installation media.

If you are on a work or school device

The standing rule applies: don’t run a reset on a managed device without coordinating with your administrator. Windows Update on enterprise devices is typically driven by WSUS, Microsoft Intune, or Configuration Manager, and resetting components on the client side can interact unpredictably with the management infrastructure. The “missing” updates may not actually be missing; they may simply not be approved yet.

If you’re the de facto IT person managing devices for a small business, the right place to start is the admin checklist for new M365 sign-in failures — it covers the equivalent admin-side flow for diagnosing fleet-wide update problems.

When to stop

Stop the reset and consider other options if:

  • Your services won’t stop after multiple attempts and reboots. Something else on the system is preventing service control. Antivirus is the most likely culprit; tampering protection settings on Microsoft Defender can also do it.
  • The reset completes cleanly but updates still fail with the same code. The component reset isn’t going to fix what’s actually broken — move to DISM/SFC, then to a repair install.
  • You’re seeing different error codes each time you try to update. The instability is in the system, not in Windows Update specifically. Address the underlying problem.
  • The PC is over six years old, has been imaged repeatedly, or has been migrated between vendors and OS versions. The fastest path to clean Update behavior on these machines is often a fresh install rather than escalating troubleshooting.
  • Windows Update error 0x80070643 — the most common reason to need a components reset.
  • Windows Update error 0x80070002 — when reset is genuinely indicated for missing-file errors.
  • Windows Update error 0x800f081f — for source-file errors that don’t always benefit from a reset.
  • Windows Update stuck at 0%, 33% or 100% — the symptom-led companion to error-code articles.
  • How to run DISM and SFC safely — the next step when reset alone isn’t enough.

Official references

FAQ

Will resetting Windows Update components delete my installed updates? No. The reset clears pending and downloading updates only. Updates that have already been installed remain installed. The procedure does not roll the system back.

Do I need to back up SoftwareDistribution before deleting it? The procedure above renames it rather than deletes it, which gives you a recovery path. After 30 days of clean update behavior, the renamed SoftwareDistribution.old folder can be safely deleted to recover disk space.

Can I just download a script from a forum that does all this? You can, and many of the popular ones work fine. The risk is that you can’t see what they’re doing without reading them line by line — and the population of users who have broken their systems with bad copy-paste scripts dwarfs the population who have been hurt by running the procedure manually. If the manual procedure feels like too many steps, save it as a .bat file you’ve reviewed.

Why does Windows Update need a reset this often? For most Windows users, it doesn’t. The procedure exists for the small minority of cases where the local update infrastructure has gotten out of sync. If you find yourself running this every other month, the underlying issue isn’t Windows Update — it’s whatever keeps corrupting the state. Look at antivirus software, disk health, and any “PC cleaner” tools (uninstall any of those — they routinely break Update).

Will this fix Windows Update on Windows 10? Yes. The procedure works identically on Windows 10 22H2, the only supported Windows 10 version in 2026. Windows 10 reaches end of support on October 14, 2025 for the consumer editions; if you’re reading this on Windows 10 in 2026, you should also be planning your move to Windows 11 or your enrollment in Extended Security Updates.

↑ Back to top