Windows 11 Update Fails With Error 0x800f0922, Microsoft Confirms

Key Takeaways

• Microsoft has acknowledged a critical installation failure for its Windows 11 May 2026 cumulative update, KB5089549.
• Affected users are encountering error code 0x800f0922, primarily due to insufficient space in the EFI System Partition (ESP).
• This mandatory security update is crucial for applying the latest security fixes and significant Secure Boot infrastructure changes.
• Microsoft is currently deploying a fix for the issue, with administrators advised to monitor the Windows Release Health Dashboard.

Windows 11 Update KB5089549 Fails with Error 0x800f0922

Microsoft has confirmed a widespread installation failure impacting its May 2026 Patch Tuesday cumulative update for Windows 11, identified as KB5089549. Users attempting to install the update are frequently met with error code 0x800f0922, with some also reporting additional error messages such as 0x80240069 and 0x80240031.

The software giant officially acknowledged this known issue by adding it to the update’s change log on May 15, 2026, merely three days after the patch’s initial release.

Mandatory Update for Windows 11 Versions

Released on May 12, 2026, KB5089549 is a compulsory cumulative update targeting Windows 11 versions 25H2 and 24H2. Its successful installation advances the operating system builds to 26200.8457 and 26100.8457, respectively. The update is comprehensive, bundling the latest May 2026 security fixes, non-security quality improvements from April’s optional preview release (KB5083631), and vital Secure Boot infrastructure modifications.

Given its classification as a required security update, Windows automatically attempts to install it, making the current installation failures particularly disruptive for affected devices and their users.

Root Cause Identified: Insufficient ESP Space

Microsoft has pinpointed the primary cause behind error 0x800f0922: insufficient free space within the EFI System Partition (ESP). The ESP is a critical, typically low-capacity partition on a device’s storage drive, responsible for storing essential boot files.

The KB5089549 update introduces substantial Secure Boot infrastructure enhancements. These include the creation of a new SecureBoot folder under C:Windows on eligible devices, alongside sample automation scripts designed to assist IT administrators in managing certificate updates across large enterprise fleets. These new additions expand the volume of files written to the ESP during the installation process, leading to installation failures on systems where the partition lacks adequate free space.

A significant component of this update is the phased deployment of new Secure Boot certificates. This process incorporates high-confidence device targeting data to broaden the coverage of eligible devices, ensuring new certificates are only deployed after a device demonstrates sufficient successful update signals, thereby maintaining a controlled rollout. Furthermore, the update provides example scripts within the new SecureBoot directory, empowering IT professionals in Active Directory environments to automate Secure Boot certificate deployment through secure, phased mechanisms.

Other Critical Fixes in This Update

Beyond the Secure Boot improvements, KB5089549 delivers resolutions for several other critical issues:

• BitLocker Recovery Loop Fixed: The update addresses a known problem where devices running April 2026’s KB5083769 could enter a BitLocker Recovery state after boot file updates, particularly affecting systems with invalid PCR7 (Platform Configuration Register 7) TPM validation settings.
• Boot Manager Reliability: Enhancements to startup reliability ensure devices boot normally after boot file updates, preventing unexpected entry into recovery mode.
• SSDP Service Stability: Reliability improvements for Simple Service Discovery Protocol (SSDP) notifications mitigate issues where the service could become unresponsive.
• Daylight Saving Time: The update incorporates support for the 2023 Daylight Saving Time change that impacted the Arab Republic of Egypt.

What You Should Do

• Monitor Official Channels: System administrators and users should regularly check the Windows Release Health Dashboard for the latest information on remediation status and official guidance from Microsoft.
• Enterprise Management: Organizations managing enterprise environments can leverage the new Secure Boot automation scripts, available after the update’s installation, to monitor certificate update status and manage phased deployment via Active Directory.
• Incremental Updates: Users who have previously installed prior cumulative updates may experience reduced ESP space requirements, as only incremental changes are downloaded.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.