Windows 11 KB5089549 Install Error 0x80240069 Download Fail

What is KB5089549 Install Error 0x80240069?

KB5089549 is the Windows 11 cumulative update shipped on Patch Tuesday, May 13, 2026 for versions 24H2 and 25H2. When it fails with 0x80240069 — or its close cousin 0x80240031 — the problem is on the download and servicing-stack path, not the disk. The update either never finishes downloading, stalls at a fixed percentage (often 0%, 20%, or 96%), or the **Windows Update service host (svchost.exe_wuauserv) crashes with an access-violation fault** mid-download.

This is a different failure from the EFI System Partition cause behind 0x800f0922 — if you hit that one instead, use our [KB5089549 0x800f0922 EFI partition guide](/en/errors/windows-11-kb5089549-install-error-0x800f0922). The 0x80240069 path is driven by a corrupt local update store or an out-of-date servicing stack. Microsoft has acknowledged that a broken servicing-stack component can crash wuauserv during this rollout, especially where updates are delivered through WSUS or SCCM/Intune.

When does it occur?

• The download bar sticks at 0%, 20%, or 96% and then errors out
• "There were problems installing some updates" with code 0x80240069 in Windows Update
• The Windows Update service stops and restarts repeatedly during the download
• On managed PCs receiving the update via WSUS, SCCM, or Intune
• After a previous cumulative update left a half-written package in the local store
• When the installed servicing stack update (SSU) is older than the May 2026 rollup expects

Common causes

• Corrupt SoftwareDistribution download cache holding a half-downloaded package
• Damaged catroot2 cryptographic catalog store breaking package signature checks
• Out-of-date servicing stack update (SSU) that can't process the new combined SSU+LCU package
• wuauserv (Windows Update service) crashing from the broken servicing-stack code path
• WSUS/SCCM delivering a package that fails local signature validation
• Corrupt component store (CBS) left over from a prior interrupted update
• Third-party "update blocker" / debloat tools that disabled or renamed update services

Step-by-step fixes

1. Run the built-in troubleshooter first — Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It resets BITS and clears stuck queues, which is enough to fix mild cases on its own.
2. Reset the Windows Update components manually (the core fix) — open an elevated Command Prompt and run:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

Reboot, then retry the update — Windows rebuilds both folders cleanly.

1. Repair the component store — in the same elevated prompt run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow. A corrupt CBS store makes the package fail no matter how many times you redownload it.
2. Install the latest standalone Servicing Stack Update (SSU) — search the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/) for the newest SSU for 24H2/25H2, download the .msu matching your architecture (x64/ARM64), install it, and reboot before retrying KB5089549.
3. Install KB5089549 manually from the Update Catalog — search "KB5089549" at catalog.update.microsoft.com, download the cumulative .msu for your edition (24H2 build 26100, 25H2 build 26200), double-click to run the standalone installer, then reboot. This bypasses the WSUS/BITS download path entirely.
4. Re-register the Windows Update DLLs if the service keeps crashing — from the elevated prompt run regsvr32 /s wuaueng.dll and regsvr32 /s wups2.dll, then restart wuauserv.
5. Apply Microsoft's Known Issue Rollback (KIR) on managed fleets — on Pro/Enterprise, import the KIR Group Policy MSI from the Update Catalog via gpedit.msc → Computer Configuration → Administrative Templates → (imported KIR node) → Enabled, then gpupdate /force. Home edition receives the KIR automatically server-side.
6. Pull the update directly from Windows Update on a single managed device — temporarily set Settings → Windows Update → Advanced options → so the PC checks Windows Update instead of WSUS, install the patch, then restore management. This sidesteps the WSUS sync defect entirely.

If it still doesn't work

If 0x80240069 survives a full component reset, check C:\Windows\Logs\CBS\CBS.log and the Windows Update log (generate it with Get-WindowsUpdateLog in PowerShell) for the exact package that fails signature validation — a single bad catalog entry will block the whole rollup. As a last resort, perform an in-place upgrade repair: download the matching Windows 11 ISO from Microsoft, mount it, and run setup.exe choosing Keep personal files and apps. This rebuilds the servicing stack and component store while preserving your data, and almost always clears persistent 0x8024xxxx download failures.

For the disk-space variant of this same patch, see our [KB5089549 EFI partition full fix](/en/errors/windows-11-kb5089549-efi-partition-full-fix); for the broader 0x800f0922 family across Windows 11 builds, see [Windows update error 0x800f0922](/en/errors/windows-update-error-0x800f0922-windows-11).