windows update error 0x800f0922 how to fix

TL;DR

0x800f0922 has two usual roots: the machine cannot reach the Windows Update download servers (VPN, firewall, or a .NET download blocked), or the System Reserved / EFI partition is full so boot files cannot be staged. Check connectivity to the download endpoints first, then check the EFI partition free space with diskpart, and clear old boot fonts or language files if it is nearly full.

windows update error 0x800f0922 how to fix

Use this when

• A cumulative update or .NET update fails with 0x800f0922.
• The failure appears while connected to a corporate VPN.
• An older upgraded machine fails feature updates with this code.

Not for this skill when

• The machine is managed by WSUS and should never contact Microsoft directly. Fix the WSUS approval instead.
• Downloads never start at all and no partition pressure exists. Check the Windows Update service itself.

Steps

1. Disconnect any VPN and retry the update on a direct connection. Verify: the update either installs or the code changes, proving the VPN path was blocked
2. Open Disk Management and check the System Reserved or EFI partition size and free space. Verify: free space is reported; under about 15 MB free is the known danger zone
3. If the EFI partition is full, assign it a letter with diskpart, then delete stale font files in the Fonts folder of the EFI partition as Microsoft documents. Verify: free space rises above 20 MB
4. For .NET updates, download the standalone .msu from the Microsoft Update Catalog and install offline. Verify: the standalone install succeeds without network access
5. Retry Windows Update. Verify: the update installs and no longer reports 0x800f0922

Variant phrasings

0x800f0922 .NET 3.5 install failed

The .NET Framework 3.5 variant, usually a blocked download of the feature payload.

feature update fails 0x800f0922 EFI partition full

The partition-space phrasing for upgraded machines with a 100 MB EFI partition.

windows update cannot connect 0x800f0922

The connectivity phrasing, tied to VPN and firewall filtering.

Compatibility: Compatibility: Windows 10 and 11; EFI partition steps apply to UEFI installs only.

Why it happens

Microsoft uses this code both for download connection failures and for the case where setup cannot write boot configuration because the system partition is full. Machines upgraded through several Windows versions often carry a small EFI partition filled with fonts for many languages, so a feature update that needs to stage new boot files has nowhere to put them.

Edge cases / pitfalls

• Never delete the whole EFI partition or reformat it; only clear the documented font and language files.
• On WSUS-managed fleets, forcing a direct Microsoft download can violate policy; confirm the update source first.
• A .NET 3.5 failure with this code on Server may need the SxS source from install media instead of a download.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstI3Reyc8mChWMl63WFUkJw