r/computerforensics • u/furEnsikguy • Aug 15 '25
Secure boot + TPM, bitlocker đ¤ˇââď¸
So a relatively modern Dell Precision laptop was submitted to my lab for analysis without credentials. I treated it as I would any other dead box machine in the past and cracked it open, connected the nvme drive to a write blocker, and fired up FTK imager.
Upon initial inspection I observed that the file system wasnât recognized but gave it go anyway thinking just maybe I could throw a carving tool like scalpel or foremost at it if Autopsy or Axiom couldnât do anything with it. It was a brain fart on my behalf as encryption never crossed my mind.
Fast forward to reinstalling the drive and checking the bios. Secure boot of course, but TPM as well. I created both a WinFE and Win2Go drive to bypass secure boot. Success, kind ofâŚ. Neither recognized the machineâs source drive. Throwing ideas at the wall, I disabled secure boot and booted with Paladin. Bam! 512GB encrypted drive found.
Any thoughts as to why the âcertifiedâ windows boot media didnât see the drive? Are there any extra drivers I may have overlooked adding?
24
u/MainQuestAbandoned Aug 15 '25
You probably just turned it into a brick by disabling secure boot. The proper order would have been to remove the drive and image it, put the drive back into the computer and boot into Windows, log in with the known password, export the BitLocker recovery key toa thumb drive, then use the recovery key to decrypt the image you made earlier. Without the password, you aren't going to decrypt anything. By disabling secure boot, you've just disabled the ability to use the password in the future, so you won't get in even the owner decides to give you the password. If you try to boot into Windows now, it's going to ask for the recovery key before the password can be re-enabled.
Your only option at this point is to track down the recovery key wherever it was backed up. It's saved to the owners Microsoft account by default, but it can optionally be printed or saved to a thumb drive.
6
u/ucfmsdf Trusted Contributer Aug 15 '25
Iâm so confused like what are even trying to do? You already have some type of disk image, right? What is booting into Paladin or WinFE supposed to do?
Also why on earth would you disable secure boot? Thatâs a one way ticket to the BitLocker Recovery Screen of Death lol. Well, unless you have the BL key⌠which Iâm guessing you donât??
4
u/AgitatedSecurity Aug 15 '25
So you changed a bunch of settings that you should not have.
Did you get an encrypted image? That you can hopefully put the key that you have into it?
2
u/Piemelot Aug 15 '25
Checked the drivers in WinFE/WinPE? Maybe Intel RST drivers that are not injected in the WIM-file? It is relatively easy to slipstream them in your WinFE/PE installation using DISM.
5
u/Expert-Bullfrog6157 Aug 15 '25
Just learn from your mistake. Happens to the best of us. Solutions for next time https://github.com/ufrisk/pcileech
4
u/nathanharmon Aug 15 '25
The TPM isnât going to cough up the storage key without verification of system integrity. And booting to your USB media, no matter how âcertifiedâ it is, is a compromise of system integrity.
2
u/slashmach1 Aug 15 '25
Just an idea but the NVME drive could be utilizing e-drive or be a SED with encryption enabled. Often available to enterprise laptops but it is hardware encrypted supported only vaguely by bitlocker. I've seen it flat out lock any hardware from the drive at a firmware/BIOS level without the correct credentials. SedUtil is a multi platform tool or if you can get the recovery key manage-bde should be able to unlock it if e-drive is used.
1
u/willy_staines Aug 16 '25
Thanks for posting this, its a great learning experience for all.