How to Check TPM Status in Windows 11
Notifications such as “This PC can’t run Windows 11″ or “Compatible TPM cannot be found” usually mean that Windows cannot locate an active TPM 2.0 security chip. To check TPM status in Windows 11, execute the Win + R shortcut, input tpm.msc, and review the Status and Specification Version fields. When the utility reports “The TPM is ready for use” alongside version 2.0, no further action is necessary.
A Trusted Platform Module (TPM) functions as a dedicated security processor that generates, stores, and protects cryptographic keys. This component may exist as a discrete hardware chip soldered to the motherboard, firmware executing on the main processor, or a security processor integrated directly into the CPU. Within UEFI firmware settings, this firmware capability typically appears as AMD fTPM on AMD architectures or Intel PTT (Platform Trust Technology) on Intel systems.
Services such as BitLocker, Windows Hello, and certain game anti-cheat applications rely on the TPM to protect keys or verify device integrity. Microsoft lists TPM 2.0 as a mandatory minimum system requirement for Windows 11. If the operating system fails to detect an enabled TPM 2.0 module, the device does not satisfy this requirement. Because the security processor is frequently disabled by default, evaluating what Windows currently detects serves as the logical first diagnostic step.
Method 1: The Management Console (tpm.msc)
This verification approach provides a rapid assessment of system security hardware. Executing tpm.msc displays specific fields including the Manufacturer Name, which identifies the builder of the security processor. Because this field alone does not indicate whether the hardware is a discrete chip or a firmware implementation, referencing the motherboard or PC manufacturer specifications remains necessary for precise identification.
Method 2: Windows Security App
This method avoids administrative privileges, making it the preferred approach when guiding an inexperienced user through the check over the phone. A successful evaluation displays a Specification version of 2.0 without any reported problems across status entries such as attestation or storage. The complete absence of a Security processor section indicates that the machine lacks compatible hardware or that the feature remains disabled in UEFI. Users encountering errors can select Security processor troubleshooting to review specific diagnostic messages reported by Windows.
Method 3: Device Manager
Reviewing Device Manager requires confirming the presence of a Trusted Platform Module entry devoid of any yellow warning icons. This technique quickly validates driver integrity and device visibility within the operating system environment.
Method 4: PowerShell (Get-Tpm)
Utilizing PowerShell offers the most robust utility for troubleshooting by detailing each stage of TPM setup independently. The SpecVersion property returns a comma-string combining the Trusted Computing Group (TCG) specification version with revision and errata levels, such as “1.2, 2, 0”. To satisfy Windows 11 compatibility, this specification version must explicitly begin with 2.0. Alternatively, administrators can read the simplified Specification Version field found within the tpm.msc management console.
Evaluating the cmdlet output requires confirming that key operational flags read True on a compatible machine. While individual flags can occasionally vary due to pending restarts, the primary indicators for system readiness are TpmPresent, TpmReady, and the correct version string. Diagnostics rely on these flags to isolate operational failures when security functions fail to execute correctly.
| Property | What it tells you |
|---|---|
| TpmPresent | Whether Windows detects a TPM on the computer |
| TpmReady | Whether the TPM meets Windows’ requirements (Microsoft’s reference defines it as compliance with Windows Server 2012 standards) |
| TpmEnabled | Generally indicates the TPM is turned on (Microsoft’s reference lists it without a definition) |
| TpmActivated | Generally indicates the TPM is activated (Microsoft’s reference lists it without a definition) |
| TpmOwned | Whether the TPM has been taken ownership of. Windows does this automatically, so you never need to create an owner password yourself |
Method 5: System Information and UEFI Firmware
Executing msinfo32 verifies that the BIOS Mode reads UEFI, confirming two core Windows 11 requirements alongside Secure Boot. However, System Information does not confirm that a usable TPM is present and cannot replace the detailed checks performed in the previous methods. Accessing the actual hardware switch requires navigating through UEFI firmware settings. Users can reach this environment via Settings > System > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > UEFI Firmware Settings > Restart.
Firmware menu terminology varies by hardware manufacturer, requiring users to search for entries labeled Security Device Support, TPM State, AMD fTPM, AMD PSP fTPM, Intel PTT, or Intel Platform Trust Technology. The following reference table matches diagnostic outputs to specific operational goals and required follow-up actions.
| What you see | What it means | Windows 11 upgrade | BitLocker / Windows Hello / anti-cheat | Next step |
|---|---|---|---|---|
| “The TPM is ready for use.” | Windows can use the TPM. This message alone doesn’t show the version | Pass only if Specification Version is 2.0 | The TPM part of the requirement is met, but each feature or anti-cheat system can have other requirements | Confirm Specification Version |
| “The TPM is ready for use, with reduced functionality.” | The TPM works, but Windows can’t use all of its features. The cause varies (firmware, provisioning, or a specific feature such as attestation) | Check Specification Version separately | Depends on which feature is affected | Read the message under Windows Security > Security processor troubleshooting, then update BIOS/UEFI (Fix #2) |
| “Compatible TPM cannot be found” | Windows isn’t detecting a usable TPM. Microsoft says the PC may have a TPM that’s disabled | Fails until a TPM 2.0 is enabled | Unavailable until a TPM is enabled | Enable it in firmware (Fix #1) |
| Specification Version 1.2 | Older TPM standard | Fails the official requirement | Varies by feature | Check whether your maker offers a TPM 2.0 firmware update for your exact model (Fix #2) |
| Firmware TPM (AMD fTPM or Intel PTT) | TPM provided by the platform firmware instead of a separate chip | Counts if Specification Version is 2.0 | Treated the same as a discrete TPM of the same version | Nothing to fix |
A status message confirming that the TPM is ready for use verifies functionality but does not confirm the version number. Administrators must always inspect the Specification Version explicitly to ensure compliance.
| Step | Action | Applies To |
|---|---|---|
| 1 | tpm.msc: Status and Specification Version | Everyone |
| 2 | Windows Security > Security processor details | Non-admin users |
| 3 | Device Manager > Security devices | Driver problems |
| 4 | Get-Tpm in an admin PowerShell window | Pinpointing failures |
| 5 | msinfo32 and UEFI firmware | Enabling TPM, UEFI and Secure Boot checks |
Common TPM Fixes
Remediation steps are structured from least to most invasive. Fix #1 applies directly when encountering missing Device Manager entries, missing hardware warnings, or negative presence flags. Menu labels vary across manufacturers, requiring users to locate the relevant setting within their specific BIOS interface.
Fix #2 addresses reduced functionality or legacy version 1.2 implementations. Applying a firmware update provided by the device manufacturer can resolve select support errors. However, updating the BIOS only converts version 1.2 hardware to version 2.0 if the manufacturer has released dedicated firmware for that specific motherboard model. Systems lacking a manufacturer path to version 2.0 generally require compatible motherboard upgrades or replacement hardware to meet official Windows 11 standards.
Fix #3 involves clearing the TPM and should be reserved strictly for personal hardware after exhausting other troubleshooting steps. Administrative clearing becomes necessary when the security processor remains enabled but authentication flags stay false, or when troubleshooting guidelines explicitly mandate it. Users must never clear enterprise or educational devices without direct instruction from an IT administrator.
Executing a reset can trigger data loss by destroying cryptographic keys and protected data such as sign-in PINs or virtual smart cards. Users must secure reliable backups and recovery methods before proceeding. Always execute the clear command through the Windows operating environment rather than directly inside UEFI firmware. Post-reboot, Windows automatically reprovisions the processor, requiring users to reconfigure Windows Hello and supply BitLocker recovery keys if prompted.
FAQ
How do I check my TPM version? Run tpm.msc and examine the Specification Version field under TPM Manufacturer Information to confirm whether it reads 2.0.
What does “Compatible TPM cannot be found” mean? This indicates that Windows cannot detect a usable security processor, frequently because the feature is disabled or hidden inside the UEFI firmware.
Does “The TPM is ready for use” mean my PC is compatible with Windows 11? This message confirms active status but does not guarantee version 2.0 compliance or satisfy anti-cheat application criteria.
What is the difference between TPM 1.2 and TPM 2.0? TPM 2.0 represents the modern cryptographic standard required by Windows 11, whereas older 1.2 hardware fails the official compatibility check.
What are AMD fTPM and Intel PTT? These designations describe firmware-based security processors integrated into platform hardware rather than operating as separate physical chips.
Can I check my TPM status without admin rights? Yes, both the Windows Security application and the tpm.msc utility display status and version metrics without requiring administrative access.
When should I clear my TPM? Clearing functions strictly as an advanced troubleshooting procedure to resolve persistent operational faults, resulting in the permanent loss of keys protected within the module.
Can Windows 11 run without a supported TPM? Operating systems installed on unsupported hardware continue to boot, though Microsoft categorizes them as unsupported despite continuing to utilize active TPM hardware for features like BitLocker.
How do I troubleshoot persistent TPM errors? Running tpm.msc offers rapid verification, while PowerShell commands pinpoint specific stage failures. When checking TPM status in Windows 11 reveals frequent hardware disconnections or unexplained lockouts, users should inspect firmware versions and consult the motherboard manufacturer.
