Windows 10: Bitlocker inputs multiple characters in the password field

Hello, I have been using BitLocker for a long time now and in conjunction with Windows 10 for 3 months and today something weird happened. When I tried to insert my password at boot, when I pressed the Shift key in combination with any other key, it inserted tens of characters at once. Valid with any character I press while Shift is also pressed. I tried a different keyboard, same result. I removed Bitlocker and reinstalled it, same result. Reboots, etc. I tried it all.

Now the only way to input the password is to press Insert so I can see the characters, press CapsLock for the capital letters and delete all the additional 30+ characters that appear when shift is pressed.
Has anyone come across such a thing? Is there a fix to it?




Thanks,


:)

 

BitLocker key repeat when using shift.

On a fresh re-install last night, on the first reboot after enabling BitLocker I encountered something strange. When entering my password at boot, the entire password field box filled with stars very fast. By pressing 'insert' to see what I was typing,
it showed the key I had pressed over and over again 20+ times.

I rebooted a few times, and tried a few things, and it is reproducible. Any time you are holding down shift, and press a key, it acts like that key was held down. If you are not holding shift, it types fine. I did a install a few weeks ago on this exact
same hardware and did not have this issue.

It looks like I'm not the only one either: Bitlocker inputs multiple characters in the password field Solved - Windows 10 Forums

Any help?

 

Inputting and IME password for Wifi not allowed?

My friend's wifi password requires Japanese IME characters to join. However language input does not allow you to directly input these characters. I have tried to copy paste the password too but it does not work either. It simply gets instantly declined as
"The network security key is incorrect".

Using multiple laptops on Windows 10.

 

Same here... it started a few days ago after a win 10 update... i bet MS pushed an updated to bitlocker that causes it... no solution found by me so far except the one you have with the insert key... (and to get things more interesting i have connected my HDMI to my TV and the DP cable to the monitor and the Nvidia bios selects the hdmi output on boot so i have to switch the tv on to see the error and remove the extra characters) i have tried with 2 different keyboards and the issue is still there. if you find a solution please share it *Smile

 

Had this happen to me last night as well, never seen it before. On a fresh install, new hardware. I'll be trying again tonight, we'll see if a fix has come through before then.

 

I have made a BIOS update today and by magic the problem disappeared. So you could try that, my MB is Gigabyte H77-DS3H and even if it already had the latest version, I wrote it again to the chip. So in my case it is solved.

 

Let me just add my case here. I have the same issue with USB keyboards while entering the Bitlocker password: One Shift+Letter keystroke produces 30+ characters. MB is an ASrock 990FX Fatal1ty Killer (BIOS: 1.60; Jan. 14th, 2016); Win 10 Pro latest upgrades installed. In Windows applications the same keyboards work without issues. I had to go back to my old PS2 keyboard to enter the Bitlocker password.

 

Have you tried my workaround to rewrite the BIOS? Also, if you remove Bitlocker from your drive and do a clean Windows 10 install then put back Bitlocker it should work as well.
Best of luck,

 

Yes, it's the most up to date BIOS available for my board (released only a few days ago). I'd rather not wipe my system since I think it's a software bug and I am not willing to waste one or two days to reset my system. I guess I'll just use my PS2 keyboard at login until there is a fix.

Thanks anyway.

 

This is why I'm asking about the BIOS, maybe this happened because of the update you made.Roll back to a previous version, see if it works that way then put back the latest one. If problem reappears, it's clearly a BIOS bug, like in my initial case.

 

The BIOS update was what I did after I found your post here *Wink

So the previous 1.50 version had this issue and now the brand new version has it, too.

I'm wondering if the bug is caused by Microsoft's Bitlocker or by the BIOS software, since the keyboards work, once Windows is started. The keyboards themselves are pretty much out of my focus since both are made by completely different manufactures and one was very cheap and the other one pretty expensive.

But thanks again for your suggestions! Much appreciated.