My BIOS is apparently corrupt, and won’t allow my computer to boot normally. An update would seem to fix the issue, but when I attempt it, it throws me the warning that I should backup my “Bitlocker recovery key” in my OS. I’ve dug around a bit, and this seems to be a Windows only thing. I do not have Windows installed on my machine. I do use wine and wine-staging for games, but I don’t think anything there is encrypted.
My question is, is it safe to ignore this warning and proceed with the update? Or is there some kind of precaution I should take anyway?
Thanks!
Bart
If you don’t have an encrypted system partition, this is “only a warning”.
Please be aware that, “cryptsetup” provides some support for volumes encrypted with BitLocker:
In addition, cryptsetup provides limited support for the use of loop-AES volumes, TrueCrypt, VeraCrypt and BitLocker compatible volumes.
If, you have an ASUS Mainboard with an AMD CPU then, if you swap out the CPU then, you have to reset the Firmware TPM because of the CPU hardware change – in this case you need to backup the TPM related keys and data …
Thank you for the reply!
I have no encrypted partitions on my system, so I think I’m good.
Yes it’s ASUS, and yes it’s AMD, but I’m not changing the CPU out. However, I’ll keep this in mind, should I need a new CPU in the future!
Again, thank you very much for your help!
Bart
Then, it’s the “AMD fTPM configuration” in the UEFI/BIOS setup:
- If, you set the “Erase fTPM NV for factory reset” to «enabled» then, the warning will appear –
Set it to the default of «disabled».
Short version: I clicked “update BIOS” and everything is now working perfectly (as far as I can tell!).
Long version: The “AMD fTPM configuration” was already set to “enabled”, so when I finally had opportunity, I did set it to “disabled”. And when I began the BIOS update, it still gave me the Bitlocker warning. A friend, who builds and repairs computers, suggested I could ignore that warning, given my circumstances. In the end, I simply don’t have an encrypted system, and pressed the “update” button. It took awhile, but it eventually booted up, and every subsequent shutdown and restart has been uneventful.
Thank you again for the advice!
Bart