Error 0x800f0922 is associated with insufficient disk space or issues with the component store (WinSxS) and servicing stack; 0x8024a22d is a Windows Update failure during the servicing phase. Given that standard repair and reset steps have already been tried (SFC, DISM /RestoreHealth, /StartComponentCleanup, SoftwareDistribution/catroot2 reset, clean boot, offline .msu, etc.), the remaining supported options are:
- Verify free space and clean component store
- Repair Windows image and system files again in correct order
From an elevated Command Prompt:
- Repair the image:
DISM.exe /Online /Cleanup-image /Restorehealth
Wait for “The restore operation completed successfully” or “The operation completed successfully”.
2) Then run System File Checker:
sfc /scannow
Wait for verification to reach 100%.
3) Reboot and try Windows Update again.
- Check common update-blocking conditions
- Confirm date and time are correct and set to automatic:
- Start > Settings > Time & language > Date & time > enable “Set time automatically” and, if available, select “Sync now”.
- Temporarily disable any third‑party antivirus, VPN, or security software, then retry the update.
- Ensure all third‑party drivers (especially storage, chipset, and GPU) are updated from the hardware manufacturer, then retry Windows Update.
- Manually reset Windows Update components (if not done exactly this way)
From an elevated Command Prompt:
net stop bits
net stop wuauserv
net stop cryptsvc
Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
Ren %Systemroot%\SoftwareDistribution\DataStore DataStore.bak
Ren %Systemroot%\SoftwareDistribution\Download Download.bak
Ren %Systemroot%\System32\catroot2 catroot2.bak
cd /d %windir%\system32
Then restart the PC and run Windows Update again.
- Perform a clean restart and retry the update
- Perform a clean restart so only minimal drivers and startup programs load, which can avoid interference during the servicing phase. See “Perform a clean restart into Windows” and then retry the KB installation from Windows Update.
- If the update still fails: in‑place repair or clean installation
If KB5077241 continues to fail after the above steps, the supported next step is to repair the OS itself:
- Perform an in‑place repair/upgrade using current Windows 11 25H2 media, or
- As a last resort, perform a clean installation of Windows 11 25H2 using the tool from the Windows 11 software download page, then apply all updates again.
These steps address corrupted or missing servicing files, Windows Update component issues, and disk/component store conditions that commonly cause 0x800f0922 and rollback at high completion percentages.
References: