You're staring at a black screen with 0X80310005 — it's the TPM failing to measure boot integrity. Annoying, but fixable in 15 minutes.
The culprit here is almost always corrupted or out-of-sync TPM keys. This happens after a BIOS update, swapping drives, or a Windows update that tweaked Secure Boot settings. Don't bother with SFC or DISM — they don't touch TPM state.
The Fix: Clear TPM and Re-Key BitLocker
- Boot into your recovery environment. You'll need a Windows installation USB or the recovery partition. Press F11/F12 during startup to access boot menu.
- Choose Troubleshoot > Advanced Options > Command Prompt.
- Run this to kill the existing TPM keys:
manage-bde -protectors -disable C: manage-bde -protectors -delete C: - Now reset the TPM itself:
— actually that's GUI. In command prompt, do:tpm.msc
tpmtool clear - Reboot. Windows will re-initialize the TPM automatically. You might get a prompt to accept a firmware change — hit yes.
- Once booted into Windows, re-enable BitLocker:
Yep, you'll need your recovery key from your Microsoft account or AD. Have that handy.manage-bde -on C:
That's it. Error should be gone. If it's not, move to the next section.
Why This Works
0X80310005 is code for FVE_E_NO_BOOT_METRIC — the TPM couldn't measure the boot chain (UEFI firmware, bootloader, OS kernel). When those measurements don't match what was stored last time BitLocker encrypted the drive, the TPM refuses to release the key. Clearing the TPM removes that old measurement snapshot. Re-enabling BitLocker creates a fresh one that matches your current boot environment.
Think of it like a lock combination that changed because someone moved the numbers. You're just reprogramming the lock to the new combo.
Less Common Variations
| Symptom | Different Cause | Solution |
|---|---|---|
| TPM is disabled in BIOS | BIOS update reset TPM to off. | Boot into BIOS and set TPM to enabled (usually under Security or Advanced). |
| TPM appears as "not ready" in tpm.msc | TPM driver corrupted. | Uninstall TPM device from Device Manager, reboot. Let Windows reinstall it. |
| BitLocker asks for recovery key every boot | TPM measurements keep changing (e.g., different boot order per boot). | Check BIOS for Secure Boot toggles — set to Standard, not Custom. Also disable Fast Boot in BIOS. |
| Error after installing a new SSD | BitLocker tied to original drive's TPM binding. | Follow the main fix — it works for swapped storage too. |
Prevention for Next Time
- Always suspend BitLocker before making BIOS changes. Run
manage-bde -protectors -disable C:and re-enable after the update. - Keep your recovery key backed up in multiple places — Microsoft account and a USB stick. Trust me, you'll thank me later.
- Don't touch Secure Boot settings unless you know what you're doing. TPM measures Secure Boot state, so changing it without updating BitLocker will break things.
- If you dual-boot, expect this error every time you switch bootloaders. Best practice: disable BitLocker on dual-boot setups.
Bottom line: 0X80310005 is a TPM communication problem, not a hardware failure. Clear the keys, reboot, re-enable. If that fails, check BIOS TPM and Secure Boot state. You'll be back in Windows in under 20 minutes.