Skip to main content
Windows Update failures leave systems unpatched and can block feature upgrades, security fixes, and driver updates. The error codes Windows surfaces during a failed update are not arbitrary — each one points to a specific type of failure, whether that is a corrupt download cache, damaged system component store, network issue, or a mismatch between the update and the current OS state. This guide covers the most frequently encountered error codes and takes you through a structured remediation workflow from the simplest fixes to the most thorough repairs.

​
Step 1 — Identify and Understand the Error Code

Before attempting any fixes, locate the specific error code Windows is reporting. Every subsequent step targets a root cause tied to that code, so recording it accurately saves significant troubleshooting time.
1

Locate the error code

Open Settings → Windows Update (Windows 11) or Settings → Update & Security → Windows Update (Windows 10). Failed updates display an error code next to the update name. Note the full hexadecimal code (e.g., 0x80070057).
2

Check the Windows Update log for detail

The Windows Update log provides more context than the Settings UI:
Open the resulting file and search for Error near the timestamp of the failed update attempt.

​
Step 2 — Understand Common Error Codes

Windows Update error codes map directly to specific failure types. Expand the entry that matches your error code to understand what went wrong and which remediation steps apply.
What it means: A required parameter passed to an internal Windows Update component was invalid. This typically results from a corrupt Windows Update data store, a damaged registry key, or a conflict with a third-party application.Fixes to try: Run the Windows Update Troubleshooter, clear the SoftwareDistribution folder, and run DISM to repair the component store.
What it means: Windows cannot read or process a file required for the update — the download package is likely corrupt or the component store contains damaged entries.Fixes to try: Clear the SoftwareDistribution folder to force a fresh download of the update packages, then run DISM /RestoreHealth.
What it means: The update download failed. This is most often caused by a network interruption, a proxy or firewall blocking access to Windows Update servers, or insufficient disk space on the system drive.Fixes to try: Verify internet connectivity, check that Windows Update endpoints are not blocked by proxy/firewall, ensure at least 10 GB free on the system drive, then retry.
What it means: A Windows component or assembly referenced by the update package is missing from the component store. Typically requires a DISM component store repair.Fixes to try: Run DISM /Online /Cleanup-Image /RestoreHealth before retrying the update.
What it means: A post-update configuration task or setup action failed. Often occurs when system reserved partition space is insufficient or when a required component is blocked.Fixes to try: Free disk space on the system reserved partition, disable VPN or third-party firewall temporarily, and run SFC + DISM.
What it means: A file needed by the update installer is locked by another process. Antivirus software is a frequent culprit.Fixes to try: Restart into Safe Mode with Networking and retry the update so that third-party software is not loaded.

​
Step 3 — Run the Windows Update Troubleshooter

The built-in troubleshooter detects and automatically fixes several common update failure conditions including stuck services, misconfigured registry entries, and incorrect file permissions.
1

Launch the troubleshooter on Windows 11

Navigate to Other troubleshooters → Windows Update → Run.
2

Launch the troubleshooter on Windows 10

Go to Settings → Update & Security → Troubleshoot → Additional troubleshooters → Windows Update → Run the troubleshooter.
3

Apply all suggested fixes

Click through any prompts and apply all suggested fixes. The troubleshooter will restart services such as Windows Update (wuauserv), Background Intelligent Transfer Service (BITS), and Cryptographic Services if they are in a failed state.
4

Restart and retry Windows Update

Reboot the machine, then open Windows Update and check for updates again. If the same error persists, proceed to the next step.

​
Step 4 — Clear the SoftwareDistribution Folder

Windows Update stores downloaded update packages in C:\Windows\SoftwareDistribution. If any file in this folder is corrupt or incomplete, subsequent update attempts will fail. Deleting the folder forces Windows to download fresh copies of all pending updates.
You must stop the Windows Update service before deleting this folder. Deleting it while the service is running can cause additional corruption. After clearing it, pending updates will need to be re-downloaded, which may take time depending on connection speed.
1

Stop the Windows Update and related services

Open an elevated Command Prompt:
2

Rename the SoftwareDistribution folder

Renaming rather than deleting preserves the old data as a backup:
3

Restart the stopped services

4

Retry Windows Update

Open Settings → Windows Update → Check for updates. Windows will recreate the SoftwareDistribution folder automatically and begin downloading fresh update packages.
5

Remove the old folder once updates succeed

​
Step 5 — Repair the Component Store with DISM

DISM (Deployment Image Servicing and Management) repairs the Windows Component Store — the repository of OS components that Windows Update draws from when applying patches. A damaged component store is the root cause of many persistent update failures.
1

Check the health of the component store

This is a quick, non-destructive check that reads existing flags. It does not scan for corruption but reports any known issues.
2

Run a full scan

This performs a full scan of the component store and may take 10–20 minutes. It does not repair anything but accurately reports whether corruption is present.
3

Repair the component store

DISM connects to Windows Update servers to download clean replacement files for any corrupt components. This requires an active internet connection and can take 20–40 minutes.
If the machine has no internet access or is behind a proxy, you can provide a local Windows ISO as the repair source:
Replace D: with the drive letter of your mounted Windows ISO.
4

Follow up with SFC

After DISM completes successfully, run the System File Checker to repair any system files that DISM flagged:
5

Restart and retry Windows Update

Reboot and attempt the update again. Most update failures caused by component store corruption are resolved at this stage.

​
Step 6 — Manually Download and Install Updates from the Update Catalog

If Windows Update continues to fail for a specific KB article, you can bypass the update mechanism entirely and install the update package directly.
1

Find the KB number

The failed update entry in Settings → Windows Update → Update history includes a KB number (e.g., KB5034441). Copy it.
2

Search the Microsoft Update Catalog

Open a browser and navigate to:
Enter the KB number in the search box.
3

Select the correct package for your architecture

Filter results by your Windows version (Windows 10 / Windows 11) and architecture (x64 for 64-bit systems, ARM64 for ARM-based devices). Click Download and save the .msu file.
4

Install the update package

Double-click the .msu file and follow the prompts, or install silently from an elevated prompt:
5

Restart and verify installation

Restart the machine and check Settings → Windows Update → Update history to confirm the KB now shows Successfully installed.
If wusa.exe returns error code 0x80096004 (trust failure), the update package’s digital signature cannot be validated. This can happen if the system date/time is incorrect — verify and correct the system clock, then retry.

​
Quick Diagnostic Reference

The entries below cover specific update failure scenarios that require targeted steps beyond the standard remediation workflow.
Stop the wuauserv and bits services, delete the SoftwareDistribution\Download subfolder only (leaving the rest intact), restart both services, and retry. Also check that the Background Intelligent Transfer Service is not blocked by a firewall or Group Policy.
Check whether Windows Update is managed by Group Policy or an WSUS/SCCM server. Run gpresult /h C:\gpresult.html and review the resulting report for Windows Update policies. Contact your system administrator if updates are being deferred by policy.
This phase applies the update to the live OS. Failures here are often caused by insufficient disk space, incompatible drivers, or a corrupt BCD. Ensure 10+ GB is free on C:, run chkdsk C: /f, and retry.
A compatibility block is in place. Open C:\$WINDOWS.~BT\Sources\Panther\CompatData_*.xml for a machine-readable explanation, or run the PC Health Check app for a user-friendly report. Common blockers include incompatible drivers, unsupported TPM version, or insufficient disk space.

​
Escalation Criteria

Escalate to Tier 2 or a Windows administrator if any of the following apply:
  • DISM /RestoreHealth fails with error 0x800f0906 or 0x800f081f and no local install media is available — the component store may be too damaged to repair online.
  • The machine is joined to a domain and Windows Update is controlled by WSUS or SCCM — update failures in managed environments require coordination with the infrastructure team.
  • The system partition has insufficient space and cannot be expanded — escalate for disk management.
  • Updates consistently fail after all remediation steps on a specific hardware model — check the manufacturer’s support site for known compatibility issues and contact Microsoft Support with the CBS log (C:\Windows\Logs\CBS\CBS.log).
  • The machine is on an end-of-life Windows version (e.g., Windows 10 21H2 or earlier) where updates are no longer published — escalate for OS upgrade planning.