Furthermore, I read in the mailing list (see Google Group) on from Aboddi that Windows 10 22H2 also received the update.Īs of December 14, 2022, Microsoft then confirmed the 0x800F0922 installation error on the Windows Server 2022 Release Health status page, for example.

Reason: Windows 11 version was not yet released in August 2022, so did not receive the update. In December 2022, the update KB5012170 was then rolled out for Windows 11 22H2 (see Windows 11 22H2: Secure Boot DBX Update KB5012170 (Dec. Revised metadata was probably the cause that the update was offered again in WSUS. I had already addressed this in October, after a reader tip, in the blog post Windows Update KB5012170 (Secure Boot DBX) re-released for WSUS (Oct. But Microsoft must have rolled out revised versions again. Renewed rollouts of KB5012170Īctually, the issue should have been settled with the update KB5012170 since August 2022 after the first rollout. This bug is also listed in the Know Issues of the support article KB5012170. I had briefly mentioned this in the blog post Windows 11 22H2: Secure Boot DBX Update KB5012170 (Dec. The bug is now listed in the Know Issues of support post KB5012170.įurthermore, the installation error 0x800F0922 could occur if an incompatible UEFI was present. Some systems ran into Bitlocker problems, as I described in the blog post Update KB5012170 for Secure Boot DBX causes Bitlocker issues.

The update was supposed to update the signatures of the database, but led to various problems. The Secure Boot Forbidden Signature Database (DBX) prevents UEFI modules from being loaded. The background is that Windows devices with UEFI (Unified Extensible Firmware Interface)-based firmware can be operated with Secure Boot enabled. The reason was a vulnerability that allowed a bypass of Secure Boot. Microsoft released the security update KB5012170 (Security update for Secure Boot DBX) on Aug(see also Windows Security Update KB5012170 for Secure Boot DBX (August 9, 2022)).

0x800f0922 server 2019