Hi @Chris Reyes ,
I think it's a physical problem with computer's mother board.
You can still try to clear the tpm module again and enable it after that.
powershell.exe Initialize-Tpm -AllowClear -AllowPhysicalPresence
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a Dell Laptop that is running Windows 10 Version 21H1. I recently had the mother board replaced. When trying to enable bitlocker, I get the following error:
"Bitlocker Could Not Be Enabled.
The Bitlocker Encryption key cannot be obtained. Verify that the trusted platform module (TPM) is enabled and ownership has been taken."
TPM is enabled. It is version 2.0. I am also running the latest BIOS on the computer. The TPM does show ownership. I have tried disabling/re-enabling. Resetting/clearing the TPM. Uninstalling the TPM from device manager. I have ran SFC Scans and DISM repairs. Yet I still continue to get this error.
Hi @Chris Reyes ,
I think it's a physical problem with computer's mother board.
You can still try to clear the tpm module again and enable it after that.
powershell.exe Initialize-Tpm -AllowClear -AllowPhysicalPresence
Thank you! I did replace the mother board so unless the new one is also bad I have no idea what else to do. I'll give the command you posted a try.
Hi there,
Based on your descriptions this seems to be an hardware issue. Suggest you to get some hardware diagnostic tool from Dell and see if it detects any hardware issues.
You can also try out some additional troubleshooting steps from the below article and see if that helps.
BitLocker cannot encrypt a drive: known TPM issues https://learn.microsoft.com/en-us/windows/security/information-protection/bitlocker/ts-bitlocker-cannot-encrypt-tpm-issues
----------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer--
Thank you everyone! Tried everything suggested, but it did not work. Ended up having to re-image the computer. Guessing it had an OS issue.