@Soho88 Not really sure why that worked, because it shouldn't have. Seeing a Recovery Key prompt the FIRST time after a BIOS update is expected because the way BitLocker works with TPMs is that the decryption key is stored in the TPM, but the TPM will only release it if it determines that nothing about the hardware or firmware environment has changed that might indicate an attempt to compromise the key. If it detects certain types of changes -- including a change to the BIOS version -- it will refuse to release the key, which is why you need the Recovery Key at that point. But if you enter the correct key, the system is supposed to "re-seal" against the new hardware/firmware environment and trust it going forward. The fact that you saw it every time suggests that somehow the TPM wasn't getting updated properly. But UEFI Secure Boot has absolutely nothing to do with a TPM. Secure Boot makes sure that the OS bootloader file that your system starts from came from a trusted publisher (like Microsoft) and has not been altered since Microsoft digitally signed it. That is a useful anti-rootkit security mechanism and therefore is something you should leave on unless you need to run an OS that doesn't support Secure Boot -- but Windows has since Windows 8.
Again, I'm not sure why toggling Secure Boot mattered in this case, but I'm also not sure why the persistent Recovery Key prompt occurred either.
But for future reference, the much simpler way to deal with this is to suspend (not disable) BitLocker before performing a BIOS update. If you install a BIOS update through Dell Update, this option is enabled by default specifically to avoid this issue. Suspending BitLocker means that for only the NEXT reboot, it will be possible to decrypt the drive without the TPM having to provide the key, and if the TPM needs to "re-seal" against a different hardware/firmware environment, that will happen automatically during that single boot. So that way you don't even need to enter the Recovery Key that first time after a BIOS update.
jphughan
9 Legend
•
14K Posts
1
February 3rd, 2021 12:00
@Soho88 Not really sure why that worked, because it shouldn't have. Seeing a Recovery Key prompt the FIRST time after a BIOS update is expected because the way BitLocker works with TPMs is that the decryption key is stored in the TPM, but the TPM will only release it if it determines that nothing about the hardware or firmware environment has changed that might indicate an attempt to compromise the key. If it detects certain types of changes -- including a change to the BIOS version -- it will refuse to release the key, which is why you need the Recovery Key at that point. But if you enter the correct key, the system is supposed to "re-seal" against the new hardware/firmware environment and trust it going forward. The fact that you saw it every time suggests that somehow the TPM wasn't getting updated properly. But UEFI Secure Boot has absolutely nothing to do with a TPM. Secure Boot makes sure that the OS bootloader file that your system starts from came from a trusted publisher (like Microsoft) and has not been altered since Microsoft digitally signed it. That is a useful anti-rootkit security mechanism and therefore is something you should leave on unless you need to run an OS that doesn't support Secure Boot -- but Windows has since Windows 8.
Again, I'm not sure why toggling Secure Boot mattered in this case, but I'm also not sure why the persistent Recovery Key prompt occurred either.
But for future reference, the much simpler way to deal with this is to suspend (not disable) BitLocker before performing a BIOS update. If you install a BIOS update through Dell Update, this option is enabled by default specifically to avoid this issue. Suspending BitLocker means that for only the NEXT reboot, it will be possible to decrypt the drive without the TPM having to provide the key, and if the TPM needs to "re-seal" against a different hardware/firmware environment, that will happen automatically during that single boot. So that way you don't even need to enter the Recovery Key that first time after a BIOS update.
VileRebis
1 Message
0
September 13th, 2023 00:20
Thank you so much. You are a lifesaver.