Windows 11 KB5095149 June 2026 Install Issues

What is Windows 11 KB5095149?

KB5095149 is the cumulative update for Windows 11 24H2 shipping on June 9, 2026 as the regular Patch Tuesday release. It folds in the permanent EFI System Partition (ESP) install-time fix that was previously delivered as an out-of-band hotfix via KB5089573, raising 24H2 to OS Build 26100.4795. The update is mandatory for security baseline compliance and contains 47 CVE fixes including two actively exploited kernel privilege-escalation issues.

When does it occur?

• Install hangs at 96% then rolls back with 0x800f0922 despite the ESP fix being included
• Wsappx.exe spikes to 100% CPU for 10+ minutes after first reboot post-install
• USB-connected printers (especially HP LaserJet 4xxx and Brother HL series) lose their driver and print blank pages
• Outlook (new) shows "Disconnected" intermittently for 2-3 days post-patch
• BitLocker prompts for recovery key on devices with TPM 2.0 firmware older than version 7.85
• File Explorer right-click "Show more options" menu becomes blank on multi-monitor setups

Common causes

• ESP partition under 100 MB free space (KB5095149 still needs ~37 MB headroom even with the patched installer)
• Pending CBS (Component-Based Servicing) operations from a half-applied earlier KB
• Conflicting third-party shell extensions (NVIDIA App, OneCommander, StartAllBack)
• Corrupted WinSxS store from prior failed rollback of KB5089549
• Out-of-date Intel ME firmware on 12th-gen and earlier chipsets
• BitLocker suspended state expired during install, triggering recovery prompt
• Microsoft Defender real-time protection blocking trustedinstaller.exe during servicing stack swap

Step-by-step fixes

1. Check ESP free space before installing. Open admin PowerShell: mountvol Z: /S then Get-PSDrive Z. You need at least 100 MB free. If under, run bcdedit /enum {bootmgr} and remove orphaned entries with bcdedit /delete <id>.
2. Reset the Windows Update components. Admin CMD: 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.
3. Repair the component store before re-attempting install. Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow. Both must complete with no errors before you retry KB5095149.
4. Suspend BitLocker explicitly. manage-bde -protectors -disable C: -RebootCount 3. This protects against the recovery-key loop on older TPM firmware.
5. Install via the standalone MSU. Download from catalog.update.microsoft.com — search KB5095149 — pick the x64 24H2 variant, then run with wusa.exe windows10.0-kb5095149-x64.msu /quiet /norestart and reboot manually.
6. Manual KB-extract workaround for the 0x800f0922 loop. Extract the MSU with expand -f:* windows10.0-kb5095149-x64.msu C:\KB5095149, then apply the inner CAB: DISM /Online /Add-Package /PackagePath:C:\KB5095149\windows10.0-kb5095149-x64.cab /Quiet /NoRestart. This bypasses the WUSA wrapper that triggers the rollback.
7. Fix printer driver loss post-install. Settings → Bluetooth & devices → Printers → remove the affected printer. Then run Print Spooler service restart: net stop spooler && net start spooler, and re-add the printer using the Universal Print Driver (PCL6) instead of the vendor v3 driver.
8. Roll back if all else fails. Settings → Windows Update → Update history → Uninstall updates → KB5095149. You have 10 days to roll back; after that you must use wusa /uninstall /kb:5095149 from a WinRE recovery prompt.

If it still doesn't work

If KB5095149 keeps rolling back after every retry, pull the CBS log at C:\Windows\Logs\CBS\CBS.log and search for the line ending in HRESULT_FROM_WIN32(ERROR_DISK_FULL) — that confirms the ESP is the root cause and you need to extend it using diskpart with an unmounted recovery USB (see our KB5089573 ESP extend fix guide). If the log shows CBS_E_INVALID_PACKAGE instead, the WinSxS store is corrupted and you'll need an in-place repair using the Windows 11 24H2 ISO from microsoft.com/software-download/windows11, selecting Keep personal files and apps. Confirm the post-install OS build is exactly 26100.4795 via winver; anything lower means the update silently failed.