Windows & BSOD · high

How to fix0x800f0922

Windows Update Error 0x800f0922 (Secure Boot / Space Issue)

What this error means

Windows servicing reported an installer failure (0x800f0922). The failed package and servicing log are needed to identify the actual cause.

Applies to
Windows 11; Windows 10 interfaces may differ
Difficulty
Beginner to intermediate
Before changes
Some checks require restart or system changes

Documentation checked: 2026-09-28 · Editorial guide checked against the linked documentation; not tested on every hardware configuration.

Before you begin

Back up important files. Save your work and record the exact message before changing anything. If Windows cannot start, see the startup guide.

Work through these checks

0 of 4 complete
01Record the failing operation
  1. Open Settings → Windows Update → Update history. Note the failed KB number and full error message.
  2. Run winver from Start and note your Windows version and build. Record whether failure occurs during download, installation, or restart.
What to expect

You have a specific update and failure stage to investigate.

If it does not help

If this happened in an application installer rather than Windows Update, use that application’s support instructions.

Browse related errors
02Look up the exact failed update
  1. Use the KB number and Windows build to open the matching Microsoft support article.
  2. Check whether it describes the same installation stage and symptoms.
What to expect

You can distinguish a documented package issue from a generic failure.

If it does not help

A fix for another Windows version or package may not apply.

Browse related errors
03Collect the servicing evidence
  1. Note the time of the failed installation.
  2. Ask a support technician to correlate that time with the CBS servicing log and identify the failing installer.
What to expect

The error can be traced to a more specific operation.

If it does not help

Avoid generic partition, registry or Secure Boot changes without a matching diagnosis.

Browse related errors
04Prepare a focused support request
  1. Collect the KB number, Windows build, failure time, and checks already tried.
  2. Use the support link for that specific update or contact your organisation’s IT team if the computer is managed. Share logs privately only after checking them for personal data.
What to expect

Support can distinguish this incident from unrelated failures with the same numeric code.

If it does not help

Keep the backup and the original error details; avoid undocumented registry or partition changes.

Browse related errors

Possible causes

  • Insufficient space in the System Reserved Partition (SRP).
  • Secure Boot is enabled in UEFI but the update's boot files cannot verify signatures.
  • Proxy/VPN connection blocking access to Microsoft's validation servers.

Sources & further reading