Unsolved
1 Rookie
•
18 Posts
0
809
November 23rd, 2021 08:00
Latitude 5490 BIOS Bitlocker Problems
Posting here in the hope that someone can assist or direct me to the proper resources.
We use Bitlocker to encrypt our computers, with the recovery keys stored in Active Directory. Since about July 2021, we've had a problem with our Latitude 5490 computers related to BIOS updates and Bitlocker recovery prompts. We use Dell Command Update to update BIOS on all of our Dell computers, but this is only affecting Latitude 5490's.
What we see is that when DCU detects a BIOS update it will download it and stage it for installation. We have DCU configured to suspend Bitlocker automatically. At some point the computer will reboot. Upon reboot, sometimes the BIOS update will install, sometimes not. But we're also seeing the computer prompt for a Bitlocker key on reboot. Since we have about 70 of these computers, it's difficult to know what is triggering this.
What I do know is that it is only affecting our Latitude 5490 computers.
So, does anyone have any input on what might be causing this? Is it the version of TPM firmware? Is it a specific version of the BIOS? Something else?
Bassman12350
1 Rookie
•
88 Posts
0
November 23rd, 2021 08:00
I wonder if you might be able to avoid the issues with Bitlocker if you set the DCU parameters for manual suspension of Bitlocker when you perform BIOS updates. I realize you have a number of the 5490s and to manually configure Bitlocker each time you update would probably be more time-intensive, but I'd try that if you haven't.
Steve
WCDave
1 Rookie
•
18 Posts
0
November 23rd, 2021 09:00
Well, the hope is that I can automate the process without requiring end users to do anything. Too many units to deal with to rely on the user to suspend Bitlocker.
Claes Wikberg
1 Message
0
June 15th, 2022 08:00
Hi Dave,
I have exactly the same issue, but its affecting some of the Latitude 5480's aswell.
We are trying to update to 1.20.0 and i have over 1200 Latitude 5490s so a manual fix is not on the table... even worse is that i cant replicate the issue on our lab clients...