Additional Microsoft Defender tools and services that provide security across various platforms and environments
Device health attestation isn't supported on this device means Windows does not receive enough information from the device to determine why TPM may not be working properly. Clearing the TPM does not fix this specific condition in all cases.
Use this troubleshooting path:
- Verify the TPM is present and the version is correct.
- Open Windows Security > Device security.
- Confirm the Security processor section is present.
- Select Security processor details and check Specification version.
- For Windows 11, TPM 2.0 is required.
- Check whether the device meets health attestation hardware requirements.
- Press Win + R, run
tpm.msc, and confirm the Specification Version. - Open an elevated Command Prompt and run
msinfo32. - In System Summary, verify:
- BIOS Mode = UEFI
- PCR7 Configuration = Bound
- Open an elevated PowerShell window and run:
Confirm it returns True.Confirm-SecureBootUEFI - Run:
Verify the drive is protected by PCR 7.manage-bde -protectors -get $env:systemdrive
- Press Win + R, run
- If TPM-related errors also appear in Security processor troubleshooting, follow the message-specific action.
- If Windows says a firmware update is needed, install the TPM or motherboard firmware update from the device manufacturer.
- If TPM is disabled, enable it in BIOS/UEFI.
- If Windows reports general TPM problems, restart the device and recheck.
- If the message remains after the checks above, contact the device manufacturer.
- Microsoft’s guidance for this exact message is that the device does not provide enough information to determine the cause.
- If problems continue after addressing the visible TPM error messages, manufacturer support is the next step.
Important: clearing the TPM can cause data loss because TPM-protected keys and data can be removed. Use Windows tools such as Windows Security or tpm.msc for TPM operations, not direct UEFI clearing.