Suspend bitlocker before updating bios

I found that odd because it prompted me to save this password or print it (there wasn't an option not to), but it made no reference of a recovery password, nor did it back this password up to AD.

suspend bitlocker before updating bios-32

you forgot to suspend Bitlocker before the BIOS update and now you are stucked with Bit Locker requiring key at every startup... Some way some how, a user's machine couldn't get read the bitlocker password off of the TPM chip, and I had to enter the recovery key (stored in AD) to get in.For example, Bit Locker can use an existing Active Directory Domain Services (AD DS) infrastructure to remotely store Bit Locker recovery keys.How Bit Locker works with fixed and removable data drives Bit Locker can also be used to protect fixed and removable data drives.We have full disk encryption using MS Bitlocker setup on all of our Lenovo laptops.

Whenever I go and update my BIOS, I sometimes forget to suspend Bitlocker first, and then that results in my having problems during reboot and I have to enter that long Bitlocker recovery key.No big deal, but once in the machine, I tried to suspend bitlocker per recovery documentation, and got an error message about the TPM not being initialized.I knew the TPM was on and activated in the BIOS, but Windows still made me reinitialize the TPM chip, and in the process it created a TPM owner password.When used with data drives, Bit Locker encrypts the entire contents of the drive and can be configured by using Group Policy to require that Bit Locker be enabled on a drive before the computer can write data to the drive.Before updating BIOS or doing changes to the BIOS on a computer that has Bit Locker enabled, suspend Bit Locker encryption before you update the BIOS.I understood why this was happening, because Bitlocker saw the BIOS update as something changing (possibly in the HAL) of the system...