When using either VeraCrypt or BitLocker full system disk encryption for my Windows 10 Pro install, I see the behavior seen in this GIF image. When doing the initial "system check" where I reboot to see if full disk encryption works, I find that I cannot reliably type my password.
A single key press at the boot authentication screen results in multiple characters being added to the password field. The input is distorted. This is not simply a view/display/feedback choice to disguise the password. It's as if the keyboard is too sensitive/fast and multiple keys are input to the box.
With VeraCrypt, if I hit Esc, the screen shows a progress bar then freezes and I have to reboot. The screen locks up at different points in the progress bar when that happens. It's not consistent. 1/50 or so times I'm able to hit Esc and successfully bypass the test boot screen and get back to Windows.
For BitLocker, Esc reliably gets me back to Windows any time I use it.
This issue behaves very similarly for both VeraCrypt and BitLocker, but it is slightly different for BitLocker. In the past, BitLocker behaved almost identically to VeraCrypt, but when I test today I see that BitLocker immediately freezes after I hit any key that is not Esc.
I've tried...
- Different USB ports
- Different keyboards
- PS/2 to USB keyboard adapters
- Using an Arduino device which typed out the password to emulate a keyboard
- Tweaking various BIOS/UEFI settings
- Clearing TPM keys and updating chipset drivers
BitLocker actually did work for me in the past after some troubleshooting. The password prompt was fine then. However, one day after a Windows update ran, this issue cropped up again. I had to try and try until I could get to the recovery tools and manually decrypt the disk. I tested again today with the hope things were magically fine, but no. The preboot authentication process is too finicky for me to trust at this point.
I'm on an Asus AB350 Pro4 with an AMD Ryzen 7 3700X.
It seems I'm not the only person with this issue. Someone even has an identical CPU, and a potential fix of their own with UEFI settings, but it sounds like their "fix" seems not to have fully resolved things.