Windows

Windows Update error codes, decoded

What the common Windows Update error codes actually mean — 0x80070643, 0x800f0922, 0x80073712, 0x80070003, 0x80070070 and more — mapped to the real cause and the fix, for Windows 11 24H2/25H2.

Evidence from the screen

Reference images and diagrams. Click any image to view full resolution.

Diagram mapping common Windows Update error codes into four root-cause buckets — component-store corruption (0x80073712, 0x800f0831; fix with DISM RestoreHealth then SFC), out of disk space (0x80070070, 0x800f0922; free space), damaged update cache (0x80070003; reset the update components), and download or connection failure (0x8024a205, 0x80240034; check network and the update service) — with 0x80070643 noted as a generic install failure. — Original concept diagram (not vendor copyright). Most update codes fall into four buckets — decode the code to its bucket, then run the one matching fix.

Problem summary

I'm here because Windows Update failed with a hex error code and I want to know what it actually means instead of guessing. Good news: most of these codes map to a small number of real causes — a corrupted component store, not enough disk space (including the tiny EFI System Partition), a damaged update cache, or a download/connection failure — and each has a documented fix. Below, the common codes are decoded to their symbolic name, the real cause, and the next action. The two repairs that resolve the majority are DISM `/RestoreHealth` + `sfc /scannow` (for corruption codes) and freeing disk space (for the space codes). If the update is stuck rather than erroring, see Windows Update stuck; to check whether your code is a known build issue, see is it the build?.

Operator snapshotEvidence first

First proof

Write down the exact code and where it appeared (Windows Update, a feature upgrade, or a specific component like .NET).

Screen to open

DISM /Online /Cleanup-Image /RestoreHealth → sfc /scannow

Expected signal

You can map the code to its symbolic name and bucket.

Stop boundary

Don't manually resize partitions without a backup.

Layer path

1A Windows Update hex code is not random — it encodes a component and a reason. Decoding it to its symbolic name (e.g. 0x80073712 = ERROR_SXS_COMPONENT_STORE_CORRUPT) tells you the real cause, and most codes collapse into four buckets: component-store corruption, insufficient disk space (including the small EFI System Partition), a damaged download cache, and a download/connection failure.

2Because the buckets are few, the fixes are few: corruption codes are cleared by DISM /RestoreHealth + sfc; space codes by freeing disk (or the ESP); cache codes by resetting the update components; download codes by fixing connectivity and the update service. Reading the code first means you apply the one fix that matches instead of trying everything.

3Some codes are a symptom of a known build issue rather than a local fault — the May 2026 0x800f0922 ESP-space case (introduced by one KB, resolved by another) is the model. So when a code lines up with a release-health entry, the resolving KB is the fix, not endless local repair.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Identify the code and its bucket

Check: Record the exact code and map it: corruption, space, cache, or download.

Expected result: You know which single repair to run.

If not: If the code is component-specific (.NET, a driver), repair that component, not Windows.

Run the matching repair

Check: Corruption → DISM+SFC. Space → free disk. Cache → reset components. Download → fix connectivity + reset components.

Expected result: The matched fix clears the error and the update installs.

If not: If the first matched fix doesn't help, the code may have a second cause — try the next most likely bucket.

Handle the space/ESP cases carefully

Check: For 0x80070070 free ~20 GB on C:. For 0x800f0922, check the EFI System Partition specifically and install the latest cumulative (disconnect VPN).

Expected result: The update finalizes once there's room and you're on a fixed build.

If not: If C: is roomy and 0x800f0922 persists, it's the ESP — follow Microsoft's documented fix, don't keep retrying.

Safe stop: Don't manually resize partitions without a backup.

Check release-health for a known issue

Check: Search the 24H2/25H2 release-health page for the code or KB.

Expected result: You find whether a resolving KB exists (e.g. the May 2026 0x800f0922 → KB5089573).

If not: If it's a known issue, install the resolving KB instead of more local repair.

Escalate only if repairs fail

Check: If the matched repair, component reset, and DISM+SFC all fail, install the KB by hand from the Microsoft Update Catalog, or plan an in-place repair-install.

Expected result: The update installs directly or via a repair-install that keeps your files.

If not: If even a manual install fails, recheck disk/ESP space and component-store health.

Safe stop: Reset → Keep my files preserves data; Remove everything erases it.

Decision tree

If: 0x80073712 or 0x800f0831.

Then: Component-store corruption.

Action: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, reboot, retry.

If: 0x80070070, or 'we need space'.

Then: Disk full (ERROR_DISK_FULL).

Action: Free ~20 GB on C: (Storage Sense / Disk Cleanup / remove Windows.old), retry.

If: 0x800f0922.

Then: Install couldn't finalize — often a full EFI System Partition, sometimes .NET or a VPN.

Action: Install the latest cumulative (the May 2026 case was fixed by KB5089573), disconnect VPN, run DISM+SFC.

If: 0x80070003, or repeated cache failures.

Then: Damaged update cache / missing path.

Action: Reset the Windows Update components (rename SoftwareDistribution and catroot2), reboot, retry.

If: 0x8024a205 or 0x80240034.

Then: Download didn't complete (download-manager/connection).

Action: Check network/VPN, confirm the Windows Update service runs, run the troubleshooter, reset components.

If: 0x80070643.

Then: Generic 'fatal error during installation' — often .NET or a recovery-partition (WinRE) update with no room.

Action: Repair via DISM+SFC and retry; for the WinRE case, give the recovery partition more space first.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
0x80073712 / 0x800f0831 on a cumulative update.	Whether DISM/SFC report and repair corruption.	Component-store corruption.	DISM /RestoreHealth + sfc /scannow, reboot, retry.
0x80070070 / 'needs space'.	Free space on C:; size of Windows.old.	Disk full.	Free space, then retry; remove Windows.old if stable.
0x800f0922 mid-install, rolls back ~35%.	EFI System Partition free space; VPN state; build vs release-health.	ESP space / finalize failure (a known build case in May 2026).	Install the latest cumulative, disconnect VPN, DISM+SFC.
0x8024a205 / 0x80240034, download never completes.	Network/VPN; Windows Update service state.	Download/connection failure.	Fix connectivity, ensure the service runs, reset components.

Reference

Commands and settings paths

Repair corruption codes

DISM /Online /Cleanup-Image /RestoreHealth → sfc /scannow

Where: Elevated terminal (reboot after)

Expected: Repairs the component store and protected system files, clearing 0x80073712 / 0x800f0831 / many 0x800f0xxx codes.

Failure means: If DISM can't find a source, point it at a mounted known-good image with /Source.

Safe next step: Reboot and retry the update.

Reset components for cache/download codes

net stop wuauserv && net stop bits → ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak → ren %systemroot%\System32\catroot2 catroot2.bak → net start wuauserv && net start bits

Where: Elevated Command Prompt (reboot after)

Expected: Rebuilds a clean update cache, clearing 0x80070003 and many 0x8024xxxx download/cache codes.

Failure means: If renames fail, the services didn't stop — stop them and retry.

Safe next step: Reboot and retry; the update re-downloads fresh.

Free disk for space codes

cleanmgr → Clean up system files (or Settings → System → Storage → Storage Sense)

Where: On the affected PC

Expected: Reclaims space so 0x80070070 / a full-disk 0x800f0922 can complete.

Failure means: If C: is already roomy but 0x800f0922 persists, the EFI System Partition (not C:) is the constraint.

Safe next step: For the ESP case, install the latest cumulative or follow Microsoft's partition fix.

Hardware boundary

Hardware and platform boundary

Change only when

Free or add system-drive space if space codes (0x80070070) recur — the cheapest, most common real fix.
Keep the servicing-stack update current, since SSU problems surface as cryptic install codes.

Evidence that matters

A healthy component store (DISM /AnalyzeComponentStore clean) and adequate free space on C: and the ESP.
The latest cumulative installed, since many codes are fixed by a later build.
A stable connection with VPN paused during updates.

Evidence that does not matter

'Error-code fixer' downloads — they don't decode anything Microsoft's reference and DISM/SFC can't.
Headline hardware upgrades — update error codes are almost never a too-slow CPU.

Avoid

Applying a random 'fix' for the wrong bucket (e.g. resetting components for a disk-space code).
Manually resizing the EFI/recovery partition without a backup.
Disabling the Windows Update service or pagefile to 'clear' an error.
Repeatedly retrying an update that release-health lists as a known issue.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Device setup troubleshooter

Last reviewed

2026-06-02 · Reviewed by HomeTechOps. Reviewed against Microsoft's Fix Windows Update errors page, the Windows Update error reference (symbolic names), the DISM corruption-repair guidance, and the 0x80070070 disk-space article; groups codes by root cause, maps each to one fix, and uses the first-party May 2026 0x800f0922 → KB5089573 case as the 'known issue, here's the resolving KB' example.

Sources/assumptions

Assumes Windows 11 24H2/25H2 consumer updates; the symbolic error names and fixes follow Microsoft's Windows Update error reference, the corruption-repair (DISM) guidance, and the disk-space error article current to mid-2026.
Codes are grouped by root cause (corruption, disk space, cache/download). A given code can occasionally have more than one cause; the page leads with the most common one and the repair that covers it.
The May 2026 0x800f0922 EFI-System-Partition example (KB5089549 → resolved by KB5089573) is used as a concrete, first-party-documented case and may age out as builds advance.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Microsoft Support: Fix Windows Update errorsUsed as the consumer hub for triaging Windows Update failures and decoding common update error codes.Microsoft Learn: Windows Update error referenceUsed as the authoritative decoder mapping Windows Update error codes to their symbolic names (e.g. 0x8024a205 WU_E_DM_NOTDOWNLOADED, 0x80240034 WU_E_DOWNLOAD_FAILED).Microsoft Learn: Fix Windows Update errors by using the DISM or System Update Readiness toolUsed for the component-store corruption error table (0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT, 0x800f0831 CBS_E_STORE_CORRUPTION) and the DISM /RestoreHealth + sfc repair path.Microsoft Learn: Troubleshoot Windows Update error 0x80070070Used for the disk-full update error (0x80070070 ERROR_DISK_FULL) and the recommendation to free space on the OS drive before retrying.Microsoft Learn: Windows 11 version 25H2 known issues and notificationsUsed as the live known-issue tracker for the current shipping 25H2 build (26200.x); paired with the 24H2 status page since the two share a servicing branch.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

What does 0x80073712 or 0x800f0831 mean?

Both are component-store corruption codes — 0x80073712 is `ERROR_SXS_COMPONENT_STORE_CORRUPT` ('the store is in an inconsistent state') and 0x800f0831 is `CBS_E_STORE_CORRUPTION` (a missing/!damaged package in the store). The fix for both is to repair the store: in an elevated terminal run `DISM /Online /Cleanup-Image /RestoreHealth`, then `sfc /scannow`, then reboot and retry the update. If DISM can't find a source, point it at a known-good Windows image.

What does 0x80070070 (or 'we need more space') mean?

That's `ERROR_DISK_FULL` — not enough disk space to download or stage the update. Free space on the system drive (aim for ~20 GB), then retry: use Storage Sense, Disk Cleanup → Clean up system files, or remove a stale Windows.old — see C: drive full after an update. On a very small drive you can even update via an external USB drive.

What does 0x800f0922 mean?

`CBS_E_INSTALLERS_FAILED` — the update couldn't finalize. The common consumer causes are insufficient free space on the EFI System Partition (ESP), a .NET/component problem, or a VPN blocking the connection. In May 2026 this code hit some PCs installing KB5089549 (ESP space) and was resolved by KB5089573 — so install the latest cumulative, disconnect any VPN, and run DISM+SFC. If it persists, check Microsoft's release-health page for your build.

What about 0x80070003, 0x8024a205 or 0x80240034?

These are cache/download problems. 0x80070003 (path-not-found family) usually means a corrupted update cache — reset the Windows Update components (rename `SoftwareDistribution`/`catroot2`). 0x8024a205 is `WU_E_DM_NOTDOWNLOADED` and 0x80240034 is `WU_E_DOWNLOAD_FAILED` — the download didn't complete, typically a connection issue: check your network/VPN, run the troubleshooter, confirm the Windows Update service is running, then reset the components.

And 0x80070643 — the 'fatal error during installation'?

0x80070643 is a generic *'fatal error during installation.'* Historically it shows up on .NET Framework updates, and more recently on a recovery-partition (WinRE) update that fails when the small recovery partition doesn't have enough free space. Re-run the update after a DISM+SFC repair; for the recovery-partition case, the documented fix is to give the WinRE partition more room before retrying. If it only fails on one optional component, that component — not Windows itself — is the thing to repair.