How to Fix Windows Update Errors

Windows Update errors most often result from a corrupted update cache in the SoftwareDistribution folder that stops new updates from installing. Other frequent causes include stopped Windows Update services, low disk space, corrupted system files, a bad specific update, a driver or third-party conflict, network interruptions, and an earlier update left in a stuck or pending state. Windows reports these failures with a hexadecimal code such as 0x80070002 or 0x800f0922, and reading that specific code narrows the cause before any fix begins.

This guide first lists the exact causes, then gives fixes ordered from the easiest and most common to a manual install. Each fix names the exact tool to use, including the Windows Update troubleshooter, the wuauserv and BITS services, System File Checker, DISM, and the Microsoft Update Catalog. Apply the fixes in order and retry the update after each one, because a single cause usually accounts for the failure. The steps apply to Windows 11 (versions 24H2 and 25H2, which share one update branch) and Windows 10.

What Causes Windows Update Errors?

Windows Update errors are caused by damaged update data, stopped services, or system conditions that block the download and installation. The four most common causes are below, each tied to the codes it produces.

Two further causes are worth noting: a driver or third-party conflict, where antivirus software, a VPN client, or an outdated driver interrupts the installer; and a network interruption, where a dropped connection or a proxy stops the download. Note the full code on the Windows Update page before continuing, then search it on Microsoft Learn to confirm which cause applies.

How Do You Fix Windows Update Errors?

Fix Windows Update errors by working through these steps in order, retrying the update after each one. The list runs from the fastest automatic repair to a manual install, so most failures clear before the end.

• Run the Windows Update troubleshooter. Open Settings, then System, then Troubleshoot, then Other troubleshooters, and click Run next to Windows Update. On Windows 11 versions 23H2, 24H2, and 25H2 this opens the Get Help app, which stops the services, repairs common cache and registry faults, and restarts the services for you. Restart and retry.
• Reset the update components. If the error returns, clear the corrupted cache by stopping the update services and renaming the SoftwareDistribution and catroot2 folders (full commands below). This forces a clean download and clears most stuck updates.
• Free disk space. A feature update needs at least 20 GB free. In Settings, open System, then Storage, clear Temporary files and Windows Update Cleanup, and uninstall unused apps. A full drive returns 0x80070070.
• Run DISM then SFC. For corruption codes such as 0x800f0922, open Command Prompt as administrator and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. DISM repairs the component store that System File Checker draws on, so it runs first.
• Install the update manually. If one specific KB still fails, read its number on the Windows Update page, open the Microsoft Update Catalog at catalog.update.microsoft.com, download the .msu package matching your Windows version and architecture, and run it.

If an update keeps reaching a percentage and failing, the cause is more likely the network or a third-party conflict than the cache. Disable any VPN or proxy, temporarily turn off non-Microsoft antivirus, confirm the connection is stable and not metered, and update storage and network drivers from Device Manager before retrying.

Reset the Windows Update Components

Resetting the update components removes the corrupted cache that causes most repeating Windows Update errors, forcing a clean download. The services must be stopped first so the folders can be renamed safely.

1. Type cmd in Windows Search, right-click Command Prompt, and select Run as administrator.
2. Run net stop wuauserv to stop the Windows Update service.
3. Run net stop bits to stop the Background Intelligent Transfer Service.
4. Run net stop cryptsvc to stop the Cryptographic service.
5. Run net stop msiserver to stop the Windows Installer service.
6. Run ren %systemroot%\SoftwareDistribution SoftwareDistribution.old to rename the cache.
7. Run ren %systemroot%\System32\catroot2 catroot2.old to rename the catalog store.
8. Run net start wuauserv, net start bits, net start cryptsvc, and net start msiserver to restart the services.
9. Restart the computer and check for updates again.

If the services themselves will not start, the registration is damaged. In that case also delete the qmgr*.dat files from the BITS data folder under ProgramData, re-register the update DLLs with regsvr32 on wuaueng.dll, wups.dll, and wups2.dll, and reset the network stack with netsh winsock reset, then reboot.

Run System File Checker and DISM

Running DISM and System File Checker repairs the corrupted system files that break the update installer and produce codes such as 0x800f0922 and 0x80070643. DISM repairs the component store that System File Checker draws on, so it runs first.

1. Open Command Prompt as administrator.
2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to complete.
3. Run sfc /scannow to verify and repair protected system files.
4. Restart the computer when both commands finish.
5. Retry the update from Settings, Windows Update.

The full procedure for these tools, including how to read CBS.log and run them from the recovery environment, appears in the guide to repair corrupt system files with SFC and DISM.

Check the Network and Disable Conflicting Software

Confirming a stable connection and disabling conflicting security software removes the interruptions that cause update timeouts and mid-install failures. VPN clients, proxies, and third-party antivirus tools are the most common offenders.

• Test the connection. Confirm the network is stable and avoid a metered connection, which delays large updates.
• Disable the VPN. Turn off any VPN or proxy during the update, because a routed connection can break the download.
• Pause third-party antivirus. Temporarily disable non-Microsoft security software that may block installer files, then re-enable it after the update.
• Update outdated drivers. A failing storage or network driver can interrupt the installer, so update drivers from Device Manager first. Lingering slowness after a patch is covered in the guide to fix a slow computer.

Install the Update Manually from the Microsoft Update Catalog

Installing the update manually bypasses the failing automatic process when a single specific update refuses to install. The Microsoft Update Catalog hosts every update as a standalone package identified by its KB number.

1. Read the failing update KB number on the Windows Update page.
2. Open the Microsoft Update Catalog in a browser at catalog.update.microsoft.com.
3. Search for the KB number.
4. Download the .msu package that matches your Windows version and the 64-bit or 32-bit architecture.
5. Run the downloaded .msu file and restart when prompted.

Match the architecture and Windows edition exactly, because a mismatched package will not install. On current Windows 11 the June 2026 cumulative update (KB5094126) raises 24H2 and 25H2 to build 26100.8655 and 26200.8655, and because both versions share one base operating system they take the same package. A manual install also confirms whether the fault was the automatic delivery rather than the update itself.

Windows Update Error Codes and Likely Causes

The table maps the common Windows Update error codes and symptoms to their most likely cause and the first fix to try.

Last Thoughts on Windows Update Errors

Windows Update errors are resolved by reading the specific error code, then applying the matching fix in order from the troubleshooter to a manual install. Resetting the update components, by stopping the services and clearing the SoftwareDistribution and catroot2 folders, handles the corruption and stuck-queue cases that account for most failures, while freeing disk space and disabling conflicting software handle the resource and conflict cases. When codes such as 0x800f0922 appear, DISM and System File Checker repair the underlying damage, and a single failing KB can always be installed by hand from the Microsoft Update Catalog.

A failed update that leaves the system unbootable is covered by the guide to recover a computer that is stuck on the loading screen. Update problems are one of the most common entries in the list of common PC problems, where the rest of the everyday Windows faults and their fixes are grouped together.

Key Takeaways:

• Read the error code first. The hexadecimal code on the Windows Update page identifies the cause before any fix.
• Start with the troubleshooter. On Windows 11 it now runs through the Get Help app and repairs the most common cache and service faults automatically.
• Reset the components for repeating errors. Stopping wuauserv, BITS, and cryptsvc and renaming SoftwareDistribution and catroot2 forces a clean download and clears most stuck updates.
• Repair system files when codes point to corruption. Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, for codes such as 0x800f0922.
• Free at least 20 GB on the system drive, because a full drive returns 0x80070070.
• Install manually as a last step. The Microsoft Update Catalog delivers a single failing KB update directly as an .msu package.

Frequently Asked Questions (FAQs)