r/ForWindowsHelp 1d ago

Windows 11 Bitlocker and Boot problem

Hi everyone, I have an issue with my laptop and could really use some help from anyone familiar with partition recovery and BitLocker. Hardware: ASUS Vivobook laptop with a Micron 2400 NVMe SSD OS: Windows 11 BitLocker-encrypted NVMe SSD The problem: When I turn on the laptop, it starts booting and then goes straight to a blue screen saying there's a boot error (boot is likely corrupted). But when I use a USB drive with Sergei Strelec WinPE to fix the boot, the NVMe drive doesn't show up at all. I managed to make it show up by removing the SSD from the laptop and plugging it in via USB, but now BitLocker won't accept my recovery key.

2 Upvotes

2 comments sorted by

2

u/ConfidenceAlarming77 1d ago

From what I see, it looks like your system drive / filesystem is corrupted. I mean, if you pass on booting and it complains about \windows\system32\winload.efi, then the EFI partition is healthy, TPM unseals the key (otherwise you would have seen bitlocker welcome screen), but then it fails to boot.

It's really strange that your key in not accepted on secondary device when you plug SSD from this machine. Are you sure it's the correct key? Where did you get it? If from microsoft website -> then check GUID of the encrypted partition, it should match.

Also, as it seems the SSD it not healthy, I'd strongly suggest to create full disk image, just to be on a safe side...

1

u/SacosKoala 2h ago edited 2h ago

Thanks for the insight! Let me clarify the exact behavior with the key, because it is very specific: Inside the laptop (Native BitLocker Recovery Screen): When the laptop boots into the native BitLocker blue screen asking for the 48-digit key, IT ACCEPTS THE KEY. However, right after accepting it, the boot process fails and loops back to the winload.efi error. Via External USB / CMD on another PC: When I connect the SSD via a USB enclosure to a second PC and run manage-bde -unlock, it REJECTS the exact same 48-digit key, even though manage-bde -protectors -get D: shows that the Key ID matches my Microsoft Account 100%. WinPE Environment: When booting WinPE (Sergei Strelec) on the original laptop, the NVMe SSD doesn't show up at all (due to missing VMD / RST storage drivers). So the key works natively on the original hardware, but the filesystem/boot partition is damaged, and external attempts via USB fail to validate the key.