Info Only- What can trigger bitlocker recovery

Yesterday I encountered a device that was giving me fits with being in a perpetual bitlocker recovery loop despite me entering the correct bitlocker key. Since what I knew about bitlocker would fit into a thimble, I resorted to extensive reading. I still don't know much but more than I did. I thought I'd share some things I found for anyone interested.
Included are : things that can trigger bitlocker recovery and how to get out of a bitlocker recovery loop.

COMMON BUT NOT ALL INCLUSIVE LIST OF THINGS THAT CAN TRIGGER BITLOCKER RECOVERY - Some apply to all devices, some only apply to certain devices dependent on the manufacturer.

1. With TPM 1.2 (NOT TPM 2.0), changing boot order in UEFI bios.
2. Having the CD or DVD drive before the hard drive in the BIOS boot order and then inserting or removing a CD or DVD.
3.Failing to boot from a network drive before booting from the hard drive.1.Docking or undocking a portable computer. (Dependant on manufacturer and bios) If a portable computer is connected to its docking station when BitLocker is turned on, then it might also need to be connected to the docking station when it's unlocked. Conversely, if a portable computer isn't connected to its docking station when BitLocker is turned on, then it might need to be disconnected from the docking station when it's unlocked.
4. Creating, deleting, or resizing a primary NTFS partition.
5. Entering incorrect PIN too many times.
6. Turning off, disabling, deactivating, or clearing the TPM
7. BIOS or UEFI firmware upgrade
8. Forgetting the PIN when PIN authentication has been enabled
9. Upgrading TPM firmware
10. Adding or removing hardware
11. Removing, inserting, or completely depleting the charge on a smart battery on a portable computer.
12. Changes to the master boot record on the disk
13. Changes to the boot manager on the disk
14. Moving the BitLocker-protected drive into a new computer
15. Upgrading the motherboard to a new one with a new TPM
16. Losing the USB flash drive containing the startup key when startup key authentication has been enabled
17. Failing the TPM self-test
18. Pressing the F8 or F10 key during the boot process

BITLOCKER RECOVERY GOES INTO CONTINUOUS REBOOT LOOP

Symptoms - Even after correctly entering a recovery key, the system reboots to Bitlocker recovery again.
I believe Point # 11 above was my culprit.

Workaround – In BL recovery press Esc for more BitLocker recovery options. Click 'skip this drive'. Advanced Options. Select Troubleshoot>Advanced Options>Command Prompt. Type manage-bde -status c:
If the status is returned as locked, you’ll need to use the following command to unlock it using your recovery password: manage-bde -unlock c: -rp <your 48-digit recovery password>

Once the drive is unlocked you'll need to use the following command to suspend protection. manage-bde -protectors -disable c:

Exit and reboot. The computer should now successfully boot Windows. Once there, use the BitLocker control panel to resume BitLocker protection.

Using bitlocker is a personal choice but I strongly suggest you become familiar with the situations that might arise and be prepared for it. Others may have bitlocker turned on even though the user never even chose to use it. Some computers come preset from the factory to turn it on. You can check bitlocker status by opening a command prompt as administrator and typing manage-bde -status

Kind of makes you want to permanently disable Bitlocker.



Other things that can trigger Bitlocker Encryption without the user's permission...

1. Yelling at the computer.
2. Typing on any forum, anywhere, that MS is less than perfect.
3. Even "talking" to MAC or Linux users.
4. Being a participant in any EU vs. MS class action lawsuit.
5. Disabling Telemetry.
6. "Not" using a Microsoft driver.
7. Using the phrase SNAFU or FUBAR, when discussing anything Microsoft.
8. "Not" kneeling down and paying homage to Redmond, Washington at 10am PST every morning.
9. Even "thinking" that Microsoft is less than perfect.

@Ghot Your humor always brightens my day. Yeah, not to get into a pi$$ing match with any BL advocate, I read enough to know that, for me, I made the correct choice to not use it.

glasskuter said:

@Ghot Your humor always brightens my day. Yeah, not to get into a pi$$ing match with any BL advocate, I read enough to know that, for me, I made the correct choice to not use it.

Click to expand...

Same.

Good info!

When in doubt, this is what I do:

Right-click the drive if File Explorer, select Manage BitLocker, then select Suspend protection.

You can now safely makes changes to the BIOS, upgrade your BIOS, etc. without triggering a BitLocker request for the recovery key. Please note that the suspension of BitLocker is valid until the next time you boot into Windows. In other words, if you reboot the system after suspending BitLocker, BitLocker will again be enabled as soon as Windows is booted again.

Ghot said:

Kind of makes you want to permanently disable Bitlocker.

Click to expand...

That is what I have also been doing ever since BitLocker first came to existence, as it just isn't a reliable solution in any way whatsoever. Case in point: