Windows 11 24H2 brought a new round of update error codes, and the forums filled with the same question in different words: what does this code mean and how do I make it go away. The honest answer is that most codes funnel into the same handful of root causes, and a disciplined repair sequence fixes them without requiring you to become an expert in each hexadecimal.

This guide gives you that sequence, plus a decoder for the most common codes so you can shortcut to the relevant fix when you recognize yours.

The fastest path through this guide is the error-code shortcut: find your code in Update history, match it in Fix 1, and jump to the fix it points at. If your code is not listed or you have no code at all, work the full sequence — it is ordered so the most common causes get eliminated first regardless of the specific error.

Why this happens

  • Corrupted download cache: The leading cause across nearly all error codes.
  • Component store damage: Triggers 0x80073712 and a family of integrity failures.
  • Permission problems: 0x80070005 when the installer cannot access what it needs.
  • Connectivity issues: 0x8024402c and timeouts when the client cannot reach update servers.
  • EFI partition too small: 0x800f0922 on systems with cramped EFI partitions.
  • Outdated servicing stack: Old update clients mishandling new packages.
  • Third-party interference: Antivirus and system utilities blocking operations.
  • Hybrid sleep states: Corrupted hibernation data interfering with the update’s restart phases.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Decode your error code

  1. Find the code in Settings > Windows Update > Update history.
  2. Match it: 0x80070002 = missing files (clear cache); 0x80070005 = access denied (permissions/antivirus); 0x800f0922 = .NET/EFI (see Fix 6); 0x8024402c = connectivity.
  3. Note the KB number alongside the code.
  4. Even without a perfect match, proceed — the sequence below is ordered to catch every common cause.
  5. If multiple updates failed with different codes, fix the oldest failure first — later ones often cascade.
  6. Write down codes before clearing caches, since the history gets cleaned too.
  7. If the same code appears for multiple KBs, treat it as one problem, not several.

Fix 2: Run the troubleshooter and clear the cache

  1. Run the Windows Update troubleshooter from Settings > System > Troubleshoot.
  2. Then in an elevated Command Prompt: net stop wuauserv, net stop bits, empty C:\Windows\SoftwareDistribution\Download, restart both services.
  3. Check for updates and observe whether the code changes — a changed code means progress.
  4. If the troubleshooter itself misbehaves, see our guide on troubleshooter failures .
  5. After the troubleshooter, check its detailed report for the specific repairs it made.
  6. If the code changed after the cache clear, look up the new code — progress deserves recognition.

Fix 3: Repair the component store

  1. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt.
  2. Follow with sfc /scannow, then restart.
  3. This resolves 0x80073712 and the integrity-check failures behind many other codes.
  4. Retry the update. Microsoft’s Windows support pages document both tools.
  5. Let DISM reach 100% — it can sit at intermediate percentages for a long time.
  6. If DISM fails at the same point repeatedly, your install media or source files are the problem.

Fix 4: Fix connectivity errors

  1. For 0x8024402c and timeout codes, run ipconfig /flushdns and restart your router.
  2. Disable VPNs and proxy settings temporarily.
  3. Verify the connection is not metered in Settings > Network & internet.
  4. Try a different network (phone tethering) to isolate ISP or router issues. For the metered angle specifically, see our guide on metered connections blocking updates .
  5. Test with a mobile hotspot to isolate home network issues quickly.
  6. After fixing connectivity, retry the update before changing anything else.

Fix 5: Install the update manually

  1. Search the KB number on the Microsoft Update Catalog .
  2. Download the matching x64 .msu and install it directly.
  3. Manual installation sidesteps the service, the cache, and the download pipeline simultaneously.
  4. If the manual install also fails, the error it shows is usually more informative than Windows Update’s.
  5. Note whether the manual install fails at the same point — matching failures confirm a system cause.
  6. Keep the .msu file; you may need it again if the issue recurs.

Fix 6: Address 0x800f0922 specifically

  1. This code often means the EFI system partition is too small or the .NET installation is damaged.
  2. Check the EFI partition size in Disk Management — under 100 MB free can block updates.
  3. Repair .NET via Settings > Apps > Installed apps > Microsoft .NET repair options, or reinstall the .NET runtime.
  4. Our dedicated 0x800f0922 troubleshooting guide covers the EFI resize procedure in detail.
  5. Back up the EFI partition contents before modifying anything boot-related.
  6. Never delete the Microsoft or Boot folders inside the EFI partition.

Fix 7: Reset components as the final sweep

  1. Stop wuauserv, bits, cryptsvc, and msiserver in an elevated Command Prompt.
  2. Rename SoftwareDistribution and catroot2 with .old suffixes.
  3. Restart all four services and check for updates.
  4. This full reset resolves the stubborn cases where individual repairs were not enough.
  5. After the full reset, run the troubleshooter once more on the clean state.
  6. Give the first post-reset update check extra time — it rebuilds everything from scratch.

Closing

Error codes look intimidating, but they are just labels on a short list of causes: bad cache, damaged store, blocked permissions, broken connectivity. Work the sequence, decode when you can, and install manually when the automated path will not cooperate. On 24H2 specifically, keeping the servicing stack current prevents a whole class of these errors from ever appearing. Error codes are the update client’s way of asking for specific help — learn to read them and troubleshooting gets dramatically faster. Keep this decoder handy for next time.

Frequently asked questions

What are the most common Windows Update error codes on 24H2?
The frequent ones are 0x80070002 (missing update files), 0x80070005 (access denied), 0x800f0922 (.NET or EFI partition issues), 0x8024402c (connectivity), and 0x80073712 (component store corruption). Each points to a different subsystem, but the repair sequence below addresses them in an order that resolves most codes without needing to decode each one.
Do I need to fix the error code or can I just reinstall the update?
Simply retrying rarely works because the underlying condition persists — the same corrupted cache or damaged file will fail the same way. Work the repair sequence instead: clear the cache, repair the store, and install manually. Retrying is only useful after a repair step has changed something.
When should I use the Update Catalog instead of Windows Update?
Use the Catalog when Windows Update repeatedly fails the same KB with download or service errors, when you need the update urgently, or when troubleshooting has stalled. Manual installation is a fully supported path, not a hack — it just moves the download and install outside the automated service.
Can 24H2-specific errors be fixed without rolling back?
Almost always, yes. The vast majority of 24H2 update errors are repairable in place with cache clears, component store repairs, and manual installs. Rollback is reserved for cases where the system is unstable after a partially applied update, not for update errors themselves.