Tried to enable BitLocker, now can't boot

STRESSED · 24 Apr 2020

I got a new Windows 10 1909 PC recently. Just decided to enable BitLocker on the system volume. BitLocker asked me if I wanted to perform a pre-BitLocker check (I can't remember the exact verbiage it used), and I responded in the affirmative.

The BitLocker wizard prompted me to reboot, and I clicked "Reboot now". But since that moment, Windows doesn't boot at all. The BIOS can't even tell the windows volume exists. It tells me to insert the boot device. When I manually select the drive with Windows in the BIOS, it does the same thing.

I created a full system image before doing any of this, but can anyone tell me what may have gone wrong? I really want to enable BitLocker.

sygnus21 · 24 Apr 2020

Are you sure BitLocker isn't asking for an access key? If I remember correctly when you first enable BitLocker on a drive and access for the first time, it will ask for either the BitLocker key or a password if you set one up.

Additionally there's no need to restart the PC when the encryption is finished - Turn On or Off BitLocker for Operating System Drive in Windows 10

Please clarify?

dalchina · 24 Apr 2020

Here's the relevant tutorial which might prompt thought:
Turn On or Off BitLocker for Operating System Drive in Windows 10

STRESSED · 24 Apr 2020

It's definitely not prompting me for an access key. The message is coming from the BIOS, because it can't find a boot device. Encryption hadn't even started; BitLocker was running a pre-encryption check... I guess I failed!

sygnus21 · 24 Apr 2020

BitLocker would NOT prevent the encrypted drive from being seen the the BIOS so that's another issue all together not having to to do with BitLocker.

And I'm not aware of any BitLocker "pre-encryption check" where the system needs rebooting. Something sound odd here.

STRESSED · 24 Apr 2020

It must have changed the boot configuration data (BCD), and something went wrong.

It offered to do a pre-encryption check, and said I would have to reboot before encryption began. I swear I'm not making it up. After I restore, I'll walk through the wizard again and post screenshots.

sygnus21 · 24 Apr 2020

STRESSED said:

It must have changed the boot configuration data (BCD), and something went wrong.

It offered to do a pre-encryption check, and said I would have to reboot before encryption began. I swear I'm not making it up. After I restore, I'll walk through the wizard again and post screenshots.

I'm amending my post above as I'm currently encrypting my current drive as we speak and yes, there is a system check where it states the PC will be restarted before encrypting....

Tried to enable BitLocker, now can't boot-bl-system-check-option.png

I'm going to run this check and get back with you after. Stay tuned....

STRESSED · 24 Apr 2020

That's it! I had "Run BitLocker system check", selected, I clicked "Continue", and then a dialog appeared prompting me to reboot. After clicking "Reboot now" on that dialogue, the trouble began.

I wasn't even able to boot back into Windows, nor was I prompted for a password or recovery key or anything. In fact, my BIOS automatically updated its boot settings to ignore the Windows drive, because it doesn't even seem to see (or recognize?) the boot configuration data for it anymore.

sygnus21 · 24 Apr 2020

STRESSED said:

That's it! I had "Run BitLocker system check", selected, I clicked "Continue", and then a dialog appeared prompting me to reboot. After clicking "Reboot now" on that dialogue, the trouble began.

Yeah, I just did the system check and my PC rebooted fine and now the drive is encrypting as I write this. Starting from the System check....

Tried to enable BitLocker, now can't boot-os-drive-encryption-5.png

After Re-boot....

Tried to enable BitLocker, now can't boot-os-drive-encryption-6.png

All working as expected here.

STRESSED said:

I wasn't even able to boot back into Windows, nor was I prompted for a password or recovery key or anything. In fact, my BIOS automatically updated its boot settings to ignore the Windows drive, because it doesn't even see the boot configuration data for it anymore.

Seems like something else happened or there was already an impending problem awaiting something to tip it over. To clarify, you can't see the OS (C) drive at all in the BIOS?

STRESSED · 24 Apr 2020

The drive shows in the BIOS, but when I select it as the boot device, the BIOS throws an error, telling me to insert the boot media or select another device.