The error 0x800f0922 is quite common with the January 2026 patches. It usually indicates that your PC is having trouble communicating with the update servers, or more commonly, that there isn’t enough space in the System Reserved Partition to handle the new boot files.
Here is the step-by-step resolution guide:
🛠️ How to Fix Error 0x800f0922
1. Enable the “App Readiness” Service
In many 2026 builds, this service is set to “Manual” or “Disabled,” which blocks the final staging of an update.
- Press
Win + R, typeservices.msc, and hit Enter. - Find App Readiness in the list.
- Right-click it, select Properties, change the Startup type to Automatic, and click Start.
- Try the update again.
2. Clear the Windows Update “Staging” Area
If a previous attempt failed, the corrupted files might still be sitting in your cache.
- Right-click Start and select Terminal (Admin) or Command Prompt (Admin).
- Type the following commands one by one, hitting Enter after each:
net stop wuauserv
net stop bits
rename c:\windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits
- Restart your PC and try the manual
.msuinstaller again.
3. Repair the .NET Framework
Error 0x800f0922 is frequently tied to a broken .NET installation.
- Press
Win + S, type Turn Windows features on or off, and open it. - Uncheck everything related to .NET Framework 3.5 and 4.8. Click OK (this will uninstall them temporarily).
- Restart your PC.
- Go back into the same menu and re-check those boxes. Let Windows download the files again.
4. Check the System Reserved Partition
If you have a very small System Reserved partition (common on older SSDs upgraded to Windows 11), the update will fail because it can’t write the new “Secure Boot” data.
- Right-click Start and select Disk Management.
- Look for a small partition (usually 100MB to 500MB) labeled “System Reserved” or “EFI System Partition.”
- If it shows 0% free space, you may need a third-party tool (like MiniTool Partition Wizard) to expand it to at least 600MB–1GB.
💡 Discussion: Why this is happening in 2026
The KB5078127 update includes heavy security changes to the Windows Kernel to protect against new UEFI-level threats discovered late last year. Because it modifies the very first files your computer reads when it turns on, any tiny error in your disk structure or a blocked service causes the “0x800f0922” safety abort.