If BitLocker is suspended and Windows reports that the laptop is not TPM compliant, the most likely causes in the available guidance are:
- The TPM is disabled or hidden in UEFI/BIOS.
- Windows is not detecting the TPM correctly.
- The TPM needs to be cleared and reinitialized.
- A firmware or TPM issue occurred after an update.
Recommended checks:
- Open Windows Security → Device security → Security processor troubleshooting.
- Review the TPM error shown there.
- If the page shows TPM is disabled and requires attention, turn TPM back on in UEFI/BIOS.
- If it shows TPM storage is not available. Please clear your TPM, use Clear TPM.
- Caution: clearing the TPM can cause data loss, so back up important data first.
- Check TPM status in firmware.
- Restart the laptop and enter UEFI/BIOS.
- Verify that TPM is enabled.
- If the TPM was disabled, enable it, save changes, and boot back into Windows.
- If Windows still says the device is not TPM compliant, reset detection of the TPM.
- In some cases, disabling the TPM in UEFI/BIOS, booting into Windows, then re-enabling it in UEFI/BIOS allows Windows to detect it again.
- After re-enabling, return to Windows and check tpm.msc or Windows Security again.
- If the TPM still cannot be prepared or detected, clear the TPM.
- This is specifically recommended when TPM initialization fails or TPM storage is unavailable.
- Warning: clearing the TPM can cause data loss.
- If Windows 11 is involved and the device is domain-joined, make sure the device has network access to a domain controller during TPM initialization if policy requires TPM recovery information to be saved in AD DS.
- If Windows Security reports that a firmware update is needed for the TPM, or that the TPM is not compatible with the firmware, check with the device manufacturer for a BIOS/UEFI or TPM firmware update.
For BitLocker specifically:
- BitLocker usually does not require any action for Microsoft Windows updates.
- BitLocker suspension is commonly needed for some non-Microsoft TPM firmware or UEFI/BIOS updates.
- If BitLocker was suspended for a firmware update and the TPM state changed, BitLocker may not resume normally until the TPM is working again.
References: