Dear community,
I'm struggling to get Bitlocker working on my HP ProBook 4340s under Win 10 pro (64bit).
setup:
- no TPM module present, but changes made to group policy editor to have Bitlocker working without.
- Windows is newly installed on SSD (crucial MX500 250GB) from UEFI USB Windows setup stick, then updated to 20H2(ok, some settings made with OOShutUp against Microsoft spying, that's all)
- Partitions have been created as standard during install: a) 100 MB EFI System b) 232,26GB NTFS Boot and Basic Data c) 521 MB NTFS recovery
as the Bitlocker option to 'activate' is presented to me this should be ok, otherwise it would complain about wrong partitions, right?
- BIOS set to 'native UEFI' (no CSM) and 'secure boot', I heard that this is mandatory to have Bitlocker working (BIOS ver. F.68 04/11/2019)
Problem:
After activating Bitlocker for C: (the only available anyway) and the necessary reboot, Windows loads normally and gives me the error "BitLocker could not be enabled. The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically. C: was not encrypted."
This message is obviously a result of the pre-encryption 'Bitlocker system check'.
(that check for automatic decryption fails, regardless whether I choose USB-stick or password as unlocking method)
It must have something to do with the startup-sequence, some wrong BIOS settings... but I couldn't figure out which.
Toggling 'secure boot' on or off makes no difference. (one guy here recommended turning it off in his special case)
other people on the web suspect the mistake in some USB settings, but I tried all available settings (and after all, I don't insist on unlocking via USB, would be nice though)
and with even others the problem disappeared by itself and they don't know why...
The craziest thing is that it showed me the password-entry-screen ONE time. (unfortunately, at that time I had to quit with escape because I wanted to save the recovery key before it starts encryption) I could never make this screen appear again since then!
Somebody out there who is familiar with such machine behavior? :-)
Any helpful comment greatly appreciated!
