Windows customers who’ve put in a brand new KB5012170 safety update for Safe Boot have encountered varied issues, starting from boots failing with BitLocker Recovery prompts to efficiency issues.
A UEFI bootloader hundreds instantly after a tool is began and is liable for launching the UEFI atmosphere with the Safe Boot characteristic to permit solely trusted code to be executed when beginning the Windows booting course of.
In the course of the August 2022 Patch Tuesday, Microsoft launched the standalone KB5012170 ‘Safety update for Safe Boot DBX’ to resolve vulnerabilities present in varied UEFI bootloaders that risk actors may use to bypass the Windows Safe Boot characteristic and execute unsigned code.
To repair these vulnerabilities, Microsoft added the certificates required to load the weak UEFI bootloaders to the UEFI Revocation Checklist – the Safe Boot Forbidden Signature Database (DBX), thus stopping them from getting used with Safe Boot.
Nonetheless, in case your gadget doesn’t have a legitimate bootloader, making an attempt to put in the KB5012170 update will generate an 0x800f0922 error and stop the set up from finishing, which is an efficient factor as your gadget would not boot in any other case.
Microsoft says you may repair this error by checking for up to date UEFI firmware out of your gadget producer.
KB5012170 causing quite a few issues
Along with the 0x800f0922 error, Windows customers at the moment are reporting issues with Windows after putting in the KB5012170 update.
As first reported by TheRegister, some Windows customers are encountering BitLocker Recovery screens after putting in the update. In response to one in all their readers, 2% of the Windows 11 gadgets confirmed BitLocker recovery screens after putting in the update.
For these affected by the Bitlocker recovery display screen, you may usually discover your recovery key saved in your Microsoft Account. Directions on discover this info might be discovered on this Microsoft help doc.
For enterprise customers, Windows admins can retrieve the Bitlocker recovery key from the Energetic Listing Customers and Computer systems.
Along with the BitLocker recovery issues, BleepingComputer readers have mentioned they’re encountering sluggish boot instances, or their disk configurations modified from RAID to AHCI within the firmware settings.
“I’ve Windows 10 21H1 and after I downloaded the update final week I observed the boot time change to VERY lengthy,” reads a touch upon BleepingComputer.
“Can affirm that. Whats worse, the update modified my RAID mode to AHCI, so I needed to manually put that again on approx 10 gadgets, that bumped into BSOD. All of them. Nearly model new Latitudes 5320 and all behaved the identical. You may see, if the update modified your RAID mode too,” reads one other remark.
Fortunately, customers ought to solely run into these issues as soon as, and they need to go away after you enter the BitLocker recovery key or modify disk configurations.
Nonetheless, it’s strongly suggested that you simply examine for up to date UEFI firmware earlier than making an attempt to put in this update to avoid wasting your self a possible headache.