Microsoft notes that the issue can be mitigated by updating the UEFI version to the latest version from the vendor.īefore attempting to update the DBX revocation list, researchers at Eclipse-recommended organizations check to see if the loaders on their systems are at risk.īootloaders are usually stored in the EFI system partition and can be mounted on Windows and Linux to check their version to determine if they are vulnerable or not. Microsoft says the KB5012170 update will cause the 0x800f0922 error because Windows needs the bootloader to start in Secure Boot on systems that start with one of the three currently excluded bootloaders. Microsoft fixed the problem by adding upper loader signatures to Secure Boot DBX, so vulnerable UEFI modules can no longer be loaded. Last week, security researchers from Eclipsium discovered vulnerabilities in three signed third-party bootloaders that could be used to bypass the Secure Boot feature and infect the system with malicious code. Windows Update Common Problems - And The FixesĪ UEFI bootloader runs immediately after system boot and is responsible for booting the UEFI environment using the Secure Boot feature that allows only trusted code to run when the Windows boot process begins. 0x800f0922 Server 2019Įrror 0x800f0922 is strictly related to KB5012170, a security update for the Secure Boot DBX (Database of Banned Signatures), a repository that stores deprecated signatures for Unified Extensible Firmware Interface (UEFI) bootloaders.

This issue does not affect cumulative security updates, monthly rolls, or security-only updates that Microsoft made available on August 9. 0x800f0922 Server 2019 – Microsoft is warning that users may see error 0x800f0922 when trying to install Windows security update KB5012170 Secure Boot on currently supported consumer operating systems and the enterprise-class server edition.

0x800f0922 server 2019