Latitude 5175 Bitlocker issue after update BIOS 1.0.20 -> 1.0.24

In my 5175 (Windows 10 + Creators Update + all updates) the bitlocker was enabled and I updated the BIOS many times without problems. But after upgrading from version 1.0.20 to version 1.0.24, I've got "Preparing BitLocker Recover" and I need to enter a recovery key. I made a downgrade to 1.0.20 but the problem was not solved. I reset the BIOS settings, but it also did not solve the problem.

I just had a situation where the Dell install had disabled Modern Standby.  When trying to find the reason I booted to a Clean Win 10 install and was presented with the Bitlocker message.  Since I have never enabled bitlocker I was a little surprised.by such a message.

But the message gave me an online address to get the key, which worked.  Needless to say, I am no longer using the Dell OEM install or any of the Dell utilities and the Modern Standby is working.

Hello CH0RNIYD00MER,

Bitlocker encryption must be suspended before you begin BIOS flash. If you have not, that is when you are prompted for the recovery key.

When you enable BitLocker, you can create a recovery password (48 characters) and a recovery file. If you saved the recovery file somewhere, use that to unlock and decrypt. Reformatting and reinstalling the operating system is the only go, if you do not have the recovery key.

Please review http://dell.to/2remlwW for more information. This has some helpful links as well.

Hello. As I wrote earlier, I have already updated the BIOS many times during the year and have never had any problems. If this update causes such problems, it was necessary to add a check to it, whether the bitblocker. If it is on, an appropriate message should appear and the installation should become impossible. This is unacceptable when the update makes the tablet inoperable. Dell needs to refine his BIOS updates so that this can not happen.

Hello CH0RNIYD00MER,

A BIOS flash without suspending the bitlocker would always prompt for recovery as the boot configurations is essentially being rewritten and it is TPM's job to protect your data in such scenarios. By blocking access to the drive and only allowing to proceed as long as the recovery key is provided. Hence the published article suggests to suspend bitlocker. Please refer http://dell.to/2rDTbKJ and Scenario 3 at http://bit.ly/2rjjy5M.

Thank you for the feedback, we shall pass this on to our relevant teams for review. You could also provide the feedback here -http://bit.ly/2gkFPti and the relevant team shall review that and contact you if required.

We are glad issue is resolved. Do get back if you have any concerns.