Windows 10: Bitlocker Blank blue screen at PIN screen

Our organization requires Laptops to be Encrypted with a PIN #. One of our Laptops is giving me trouble. I have Bitlocker turned on and fully encrypted and have require Startup PIN with TPM in the Require additional authentication at startup in GPEDIT. I also have the Enable use of Bitlocker Authentication Requiring preboot Keyboard input on Slates enabled. When turning on the Laptop Bitlocker comes up with the light blue screen where you enter the PIN but the screen is blank. It doesn't say Bitlocker or have a box to enter the PIN #. Now I can just type the pin # and press enter and it works and loads windows as normal. I obviously can't give this Laptop to a user like this.

Anybody have any suggestions as to a resolution to this issue.
Thank You.

:)

 

Windows 10 Bitlocker won't boot

In case anyone is following this, after looking at SuperUser, I found this MS post that addresses the issue:

http://answers.microsoft.com/en-us/windows/forum/windows8_1-security/bitlocker-pin-pre-boot-screen-empty/f985c4f6-dd71-4586-bd46-50f513432bb3?auth=1

The SuperUser question is
http://superuser.com/questions/1102358/windows-10-bitlocker-on-bootup-presents-just-a-blue-screen-but-no-password-box-o. SuperUser has a couple of potential fixes, but the gist is that you can type your password at the blank screen and it will work.

 

Bitlocker password promptscreen problem after installing update (KB3172985)

I have seen the same issue but it is when Windows 10 asks for the Bitlocker PIN and the screen is a light blue, not black.

 

We have the same issue with one of our Lenovo laptops. Did you ever find a solution?

 

I ended up re-installing windows 10 and deleting all of the partitions. Then it worked fine. I think the partitions were messed up as I received errors turning bit locker on about the partitions were not set the first time. After re-installing Win10 from scratch it has worked great.

 

Thanks for the reply. We're doing the same. Fresh re-install of Windows 10

 

See this page and look for v2012's answer. Please let us know on that board or here if it fixed your issue.

http://answers.microsoft.com/en-us/w...2bb3#LastReply