Non-Intel motherboards typically have an option in the BIOS that lets you clear the TPM.
After the reboot and logon was completed I re-enabled BitLocker.Īnd I believe I was never prompted for the 48 digit recovery key after that point (even after a cold boot)? My recollection is that when I've been prompted for this 48 digit recovery key in the past that after I logged on to Windows I suspended BitLocker and the rebooted (warm boot) the machine. Problem with the Intel DX79TO motherboard? The Intel engineers are quick to point out the DQ67EP has a different chipset than the DX79TO and I agree, but given BitLocker has worked for every other motherboard I've used my suspicion is this is a hardware Most of these were non-Intel motherboards, but I have one other Intel motherboard (DQ67EP) and have been able
I've had about 20 different computers over the years (since BitLocker was first released) and this is the only one I've had this problem with. But two Intel engineers have emailed and their assertion is that the DX79TO motherboard is fine and the problem is with Microsoft (BitLocker). So I can't envision any reason why BitLocker would think there had been a hardware change. I had not made anyĪdditional hardware or software changes. On my PC BitLocker seems to think something has changed in the hardware (and thus the prompt for the 48 digit recovery key)? I double checked the BIOS settings and the few options I changed are still set the same way as before.
#Intel desktop board dq67ep how to#
Has anyone else been able to get BitLocker to work on an Intel DX79TO motherboard? Or any ideas on how to fix this problem? None of the similar problems I've found (when Googling this site or the web in general) have worked for me. Prompted for the 48 digit BitLocker recovery key every time. But I'm having problems in which whenever I shutdown the computer (cold boot) I am A primary reason for choosing this motherboard was the integrated TPM which would allow me to run BitLocker. I recently purchased an Intel DX79TO motherboard.
0 kommentar(er)
