Windows 11 TPM Not Showing Up? Step-by-Step Troubleshooting Guide for BitLocker and Windows Hello

What it means when Windows 11 says TPM is not detected

When Windows 11 reports that a TPM device is not detected, it usually indicates one of two situations: either the system firmware (BIOS/UEFI) has TPM disabled or the operating system cannot communicate with the TPM hardware. This error matters because many security features rely on TPM, including BitLocker drive encryption and Windows Hello (for hardware-backed authentication).

TPM issues are commonly caused by configuration mismatches between firmware settings and Windows requirements, outdated chipset or TPM drivers, or a Windows security workflow that was started before TPM became available.

Before starting: confirm the Windows view of the TPM

Before making changes, it helps to check what Windows currently reports.

• Open Device Manager and look under security-related categories for TPM references (names can vary by vendor).
• Open Windows Security and review security processor and device security status.
• Check BitLocker status in Settings if encryption was previously attempted. If BitLocker cannot initialize, TPM is often the missing dependency.

If Windows continues to show TPM as unavailable, the next sections focus on the most common root causes.

Step 1: Enable TPM in BIOS/UEFI

The most frequent fix is enabling TPM in firmware. On many systems, TPM may be disabled by default, or it may require a specific mode selection.

1. Restart the computer and enter BIOS/UEFI (often by pressing Del, F2, or another setup key during boot).
2. Locate a settings page related to Security, Trusted Computing, or TPM.
3. Enable TPM or select an option such as TPM 2.0 (wording varies by manufacturer).
4. Save changes and reboot.

Important: Some platforms require switching from an older TPM mode to a newer standard. Choosing an incompatible mode can lead to persistent detection failures.

Step 2: Verify firmware and TPM mode compatibility

If enabling TPM does not resolve the issue, the next target is consistency. Certain systems require that firmware and TPM configuration align with Windows expectations.

• Confirm the TPM version selection (commonly TPM 2.0) in BIOS/UEFI.
• Check whether the firmware offers a choice between Discrete TPM and Firmware TPM (fTPM). Use the mode recommended by the device vendor.
• If there are security options such as secure boot interactions, ensure they are not blocking TPM initialization.

After any firmware change, a full reboot is necessary. Avoid partial restarts when validating TPM availability.

Step 3: Update chipset and TPM-related drivers

Even with TPM enabled in BIOS/UEFI, Windows may fail to communicate with the device if drivers are outdated. This is especially common after hardware changes, OS upgrades, or long intervals without driver updates.

• Install the latest chipset drivers from the PC or motherboard manufacturer.
• Update TPM or security firmware utilities if provided by the vendor.
• Update any storage controller drivers if BitLocker initialization repeatedly fails after TPM becomes available.

After driver updates, reboot and check Windows again for TPM availability and security processor status.

Step 4: Address BitLocker when TPM becomes available

BitLocker depends on TPM and may have a partially configured state if encryption was attempted while TPM was missing. Once TPM is detected, BitLocker may need reconfiguration.

Typical remediation actions include:

• Open BitLocker settings and verify whether drive encryption is in an error or suspended state.
• Follow the on-screen prompts to resume or restart setup after TPM is detected.
• If recovery key prompts appear, store the key securely and complete the encryption workflow again.

When TPM settings change, BitLocker can require recovery key verification. This is expected behavior to protect against unexpected security changes.

Step 5: Repair Windows Hello and device security workflows

Windows Hello uses security hardware to support hardware-backed authentication. If TPM was not detected during setup, Windows Hello configurations may fail or remain disabled.

When TPM becomes available:

• Recheck Windows Security to confirm the security processor status.
• In Sign-in options, review whether Windows Hello shows errors or requires re-enrollment.
• Remove problematic Windows Hello credentials only if prompted by the system, then re-set up authentication.

Step 6: Consider TPM clearing and vendor firmware tools

Some environments benefit from resetting TPM state when configuration changes occur, such as switching TPM modes or after major firmware updates. Clearing TPM can resolve stale states, but it may also trigger BitLocker recovery and other security re-initialization steps.

Before clearing TPM:

• Ensure BitLocker recovery keys are available.
• Confirm a reliable backup of any dependent security configuration (especially enterprise-managed systems).
• Use TPM reset or clear functions provided by the OS or vendor tooling when available.

Common troubleshooting checklist

• TPM enabled in BIOS/UEFI with TPM 2.0 (or the correct recommended mode).
• System rebooted after firmware changes.
• Chipset and TPM/security drivers updated.
• BitLocker restarted or resumed after TPM detection.
• Windows Hello re-enrolled if it previously failed due to missing TPM.

Conclusion

A “TPM device not detected” message on Windows 11 is typically resolved by enabling TPM in BIOS/UEFI, confirming compatible TPM mode settings, and updating relevant drivers. After TPM becomes available, BitLocker and Windows Hello setups may need reconfiguration to reflect the newly detected security hardware. Following the steps in order reduces downtime and minimizes repeated security prompts.