Error code 0x800f0922 appears when a Windows quality update or feature update fails to install. When Automox reports this code on a patch result, it is being surfaced from the device's own Windows Update engine, not generated by Automox. The same code can come from several unrelated causes, so there is no single fix. Work through the causes below, starting with the most common.
Cause 1: VPN or Connectivity to Windows Update Servers
The most common cause is that the device could not reach the Windows Update servers, which frequently happens when a VPN is active. If the device is connected to a corporate VPN, disconnect from the VPN (and any VPN client software), then retry the update. Confirm the device otherwise has a stable internet connection before retrying.
Cause 2: Insufficient Space on the System Reserved Partition
0x800f0922 can also mean the System Reserved partition (SRP) does not have enough free space for the update to stage. Microsoft's guidance is to free at least 13 MB for a quality update, or 15 MB for a feature update or version upgrade.
The SRP is a small hidden partition and commonly fills up from accumulated language packs or fonts. Freeing space on it, or expanding it, typically requires a partition-management tool. See Microsoft's documentation (linked below) for the supported approach.
Cause 3: .NET Framework
A missing or disabled .NET Framework can also trigger this error. To enable it:
- Search for and open Turn Windows features on or off.
- Enable the checkboxes for .NET Framework (both the 3.5 and 4.x entries, if present).
- Click OK, then restart the device.
- Retry the update.
Cause 4: Corrupt Update Files or System Files
If the update files or system components are damaged, repairing them often clears the error. From an elevated Command Prompt, run:
sfc /scannow
Then run the DISM image repair:
DISM /Online /Cleanup-Image /RestoreHealth
Restart the device and retry the update.
Cause 5: Third-Party Antivirus Interference
Third-party antivirus or security software can occasionally block update components. If the steps above do not resolve it, temporarily disable third-party AV, retry the update, then re-enable it.
If the Error Persists
If none of the above resolves it, the failure detail is logged on the device in the Windows Update logs (CBS.log / WindowsUpdate.log). For full Microsoft troubleshooting guidance, see the reference below, or contact Automox Support with the device details.