Windows KB5012170 update causing BitLocker recovery screens, boot issues

Windows 10 bug

Windows users who have installed a new KB5012170 security update for Secure Boot have encountered various issues, ranging from boots failing with BitLocker Recovery prompts to performance issues.

A UEFI bootloader loads immediately after a device is started and is responsible for launching the UEFI environment with the Secure Boot feature to allow only trusted code to be executed when starting the Windows booting process.

During the August 2022 Patch Tuesday, Microsoft released the standalone KB5012170 'Security update for Secure Boot DBX' to resolve vulnerabilities found in various UEFI bootloaders that threat actors could use to bypass the Windows Secure Boot feature and execute unsigned code.

To fix these vulnerabilities, Microsoft added the certificates required to load the vulnerable UEFI bootloaders to the UEFI Revocation List - the Secure Boot Forbidden Signature Database (DBX), thus preventing them from being used with Secure Boot.

However, if your device does not have a valid bootloader, attempting to install the KB5012170 update will generate an 0x800f0922 error and prevent the installation from completing, which is a good thing as your device would no longer boot otherwise.

Microsoft says you can fix this error by checking for updated UEFI firmware from your device manufacturer.

KB5012170 causing numerous issues

In addition to the 0x800f0922 error, Windows users are now reporting problems with Windows after installing the KB5012170 update.

As first reported by TheRegister, some Windows users are encountering BitLocker Recovery screens after installing the update. According to one of their readers, 2% of the Windows 11 devices showed BitLocker recovery screens after installing the update.

Other users on the Microsoft Answers forum, Twitter, and Reddit have also said they are experiencing the same behavior.

**BitLocker Recovery screen**
*Source: The Register*

For those affected by the Bitlocker recovery screen, you can typically find your recovery key stored in your Microsoft Account. Instructions on how to find this information can be found in this Microsoft support document.

For enterprise users, Windows admins can retrieve the Bitlocker recovery key from the Active Directory Users and Computers.

In addition to the BitLocker recovery problems, BleepingComputer readers have said they are encountering slow boot times, or their disk configurations changed from RAID to AHCI in the firmware settings.

"I have Windows 10 21H1 and after I downloaded the update last week I noticed the boot time change to VERY long," reads a comment on BleepingComputer.

"Can confirm that. Whats worse, the update changed my RAID mode to AHCI, so I had to manually put that back on approx 10 devices, that ran into BSOD. All of them. Almost brand new Latitudes 5320 and all behaved the same. You can see, if the update changed your RAID mode too," reads another comment.

Thankfully, users should only run into these issues once, and they should go away after you enter the BitLocker recovery key or modify disk configurations.

However, it is strongly advised that you check for updated UEFI firmware before attempting to install this update to save yourself a potential headache.

Results for “"kb5012170"”

Windows KB5012170 update causing BitLocker recovery screens, boot issues

Windows KB5012170 Secure Boot DBX update may fail with 0x800f0922 error