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 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 article first lists the exact causes of Windows Update errors, then gives step-by-step fixes ordered from the easiest and most common to manual installation. 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.

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 process. The causes below are ranked from most to least common, and the error code shown alongside each failure points to one of them.

• A corrupted update cache. Damaged files in the SoftwareDistribution folder cause downloads to fail or repeat, often shown as 0x80070002 or 0x80073712.
• Stopped Windows Update services. When the Windows Update service (wuauserv) or Background Intelligent Transfer Service (BITS) is stopped, updates cannot download or install.
• Low disk space. Feature updates need several gigabytes of free space, and a full system drive returns errors such as 0x80070070.
• Corrupted system files. Damaged protected files break the update installer and produce codes such as 0x800f0831 and 0x800f0922.
• A driver or third-party conflict. Antivirus software, VPN clients, and outdated drivers interrupt the installer mid-process.
• Network interruptions. A dropped connection or a misconfigured proxy stops the download and returns timeout-related codes.
• A stuck or pending update. An earlier update left half-installed blocks every later one until the pending state is cleared.

Note the full code on the Windows Update page or in the failure message before continuing. Search that code on Microsoft Learn to confirm which of the causes above applies.

Run the Windows Update Troubleshooter

Running the Windows Update troubleshooter is the fastest fix, because it stops the update services, repairs common cache and registry problems, and restarts the services automatically. The troubleshooter is built into Windows and resolves many cases without manual commands.

1. Open Settings, then System, then Troubleshoot, then Other troubleshooters.
2. Find Windows Update in the list.
3. Click Run next to Windows Update.
4. Allow the troubleshooter to detect and apply fixes.
5. Restart the computer and retry the update from Settings, Windows Update.

The troubleshooter reports each problem it found and whether it was fixed. If the same error code returns afterward, move to the targeted fixes below.

Free Disk Space for the Update

Freeing disk space resolves update errors caused by a full system drive, because feature updates need free room to download, expand, and install. Keep several gigabytes free on the drive that holds Windows.

1. Open Settings, then System, then Storage.
2. Click Temporary files and remove Windows Update Cleanup, the Recycle Bin, and thumbnails.
3. Turn on Storage Sense to clear temporary data automatically.
4. Run Disk Cleanup as administrator and select Clean up system files.
5. Uninstall unused applications, then retry the update.

A feature update typically needs at least 20 gigabytes of free space. Move large media files to another drive if the system drive remains full after cleanup.

Clear the SoftwareDistribution and catroot2 Folders

Clearing the SoftwareDistribution and catroot2 folders removes the corrupted update cache that causes most repeating Windows Update errors, forcing Windows to download a clean copy. 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 ren %systemroot%\SoftwareDistribution SoftwareDistribution.old to rename the cache.
6. Run ren %systemroot%\System32\catroot2 catroot2.old to rename the catalog store.
7. Run net start wuauserv, net start bits, and net start cryptsvc to restart the services.
8. Restart the computer and check for updates again.

Windows rebuilds both folders on the next update check. The renamed .old folders can be deleted later once updates install correctly.

Run System File Checker and DISM

Running System File Checker and DISM repairs the corrupted system files that break the update installer and produce codes such as 0x800f0922. 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 Recovery, appears in the guide to repair corrupt system files with SFC and DISM.

Reset Windows Update Components

Resetting Windows Update components returns the services, security descriptors, and cache to a clean state when the troubleshooter and cache rename do not clear the error. This procedure stops every update-related service, clears the queue, and re-registers the required files.

1. Open Command Prompt as administrator.
2. Stop the services with net stop wuauserv, net stop bits, net stop cryptsvc, and net stop msiserver.
3. Delete the qmgr*.dat files from the BITS data folder under ProgramData.
4. Rename SoftwareDistribution and catroot2 as shown in the previous fix.
5. Re-register the update DLLs by running regsvr32 on wuaueng.dll, wups.dll, and wups2.dll.
6. Reset Winsock by running netsh winsock reset.
7. Restart the four services and reboot the computer.

Resetting Windows Update components addresses errors that survive a cache rename, such as a damaged service registration. Use it after the simpler fixes above have failed.

Pause and Retry the Update

Pausing and resuming Windows Update clears a stuck or pending state and lets the download restart from the beginning. A half-finished update often blocks every later one until the queue is reset this way.

1. Open Settings, then Windows Update.
2. Click Pause updates and select a one-week pause.
3. Restart the computer to clear any pending installation.
4. Return to Windows Update and click Resume updates.
5. Click Check for updates and allow the download to restart.

A pause followed by a restart removes partial download data. If an update repeatedly reaches a percentage and fails, the network or a third-party conflict is the more likely cause.

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.

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 package that matches the 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. A manual install confirms whether the fault was the automatic delivery rather than the update itself.

Windows Update Error Codes and Likely Causes

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. The built-in Windows Update troubleshooter repairs the most common cache and service problems automatically.
• Clear the cache for repeating errors. Renaming SoftwareDistribution and catroot2 forces a clean download.
• Repair system files when codes point to corruption. DISM and System File Checker fix installer failures such as 0x800f0922.
• Install manually as a last step. The Microsoft Update Catalog delivers a single failing KB update directly.

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. Clearing the SoftwareDistribution cache and resetting update components handle the corruption cases, while freeing disk space and disabling conflicting software handle the resource and conflict cases. When codes such as 0x800f0922 appear, the steps to repair corrupt system files resolve the underlying damage.

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, and keeping Windows current depends on the system software described in the explanation of what an operating system is.