OK, I never set up bitlocker on this laptop, and I never set up a Microsoft account... I only set up a local login. An automatic update kicked off yesterday. It didn't really ask me, it just did it.
Now I can't log into my laptop, because it comes up to a bitlocker recovery screen. I don't have the key, and there is no key saved anywhere, since I never set up a Microsoft account and never did anything with Bitlocker.
In other threads here on the Dell Community, I saw that some other people have had luck with reinstalling the previous Bios and then getting back into the laptop.
However, when I look at notes with the last BIOS update, it says the following:
Important Information
- Once the BIOS is upgraded to version 2.5.1 or later, you cannot downgrade the BIOS to version 2.4.2 or earlier. BIOS downgrades are restricted when there are security updates and important fixes with earlier versions that impact the functionality of the system.
Am I even going to be allowed to downgrade back to what I had before?
Any other advice on how to get back into my files? I'd rather not lose all of my data.
Bios 2.5.1 was sufficiently old enough I was able to get back in.
I disabled secure boot, pressed F12 to get to boot options, flashed BIOS to 2.5.1 (which I had saved to a usb), re-enabled secure boot, logged into my PC, and printed the bitlocker recovery key.
I then rebooted computer. It immediately reinstalled the BIOS update that originally caused the problem, but I had a printed recovery key. Yay!
@pastacode , I'm having the same problem with the same model dell (9360). For me, after I go into the F12 one-time-boot menu, click the flash update option, select the XPS_9360_2.5.1.exe from my thumbdrive, and click "Begin Flash Update" the machine immediately reboots and I'm taken back to the bitlocker recovery key screen. How were you able to start the flashing process??
Now here's something truly odd: I just rechecked (as in: it being the first thing I did yesterday when the problem began and in since having checked several times while trying to fix the issue) using the link you posted, and voila! now all the recovery keys are there. So am back in!
I have been using another laptop to access info and of course checked that one straight away yesterday too. Bitlocker function had been activated (not by me...) with no recovery key in the microsoft account (as said, did check several times). And now, it's been activated (not by me) and this time the recovery key is listed in the microsoft account. Hope this is not confusing....certainly weird.
So first, thank you so much for your help, and posting the www.onedrive.com/recoverykey link which made me go check one more time. Maybe it's specifically using the onedrive access rather than just logging on to the microsoft account that has made the difference.
For others out there with the recovery key problem, there is hope. And really great help here on this forum. Thanks again.
I am running into the same issue of being locked out by bitlocker after the BIOS update, I never set up bitlocker and was in fact unaware of its existence at all until this issue arose, consequently I don't have a recovery key and one doesn't exist when I check my microsoft account etc.
Regarding the potential fix of downloading an old BIOS version and installing it through a USB drive, do I need a program installed on the USB drive to do this or will it be able to run the downloaded BIOS from the USB drive by itself. Thank you for any help you can provide. I am only semi computer literate when it comes to unexpected issues like this. I need access to my files on my laptop etc and reinstalling windows and wiping my hard drive are not an option.
pastacode
2 Posts
2162
0
Posted August 22nd, 2021 15:00
Bios 2.5.1 was sufficiently old enough I was able to get back in.
I disabled secure boot, pressed F12 to get to boot options, flashed BIOS to 2.5.1 (which I had saved to a usb), re-enabled secure boot, logged into my PC, and printed the bitlocker recovery key.
I then rebooted computer. It immediately reinstalled the BIOS update that originally caused the problem, but I had a printed recovery key. Yay!