How to Fix ‘TPM Device Is Not Ready’ Error in Windows 11

“TPM Device Is Not Ready” means Windows sees your Trusted Platform Module but can’t use it. That’s frustrating, especially when BitLocker or a Windows 11 check fails.

Quick Diagnosis

Fix #1: Confirm the TPM Status

A TPM is a security processor. It protects BitLocker keys, Windows Hello credentials, and other private data. This error may appear in Windows Security, BitLocker setup, or a Windows 11 compatibility check. It can also appear after a BIOS update.

Symptoms:

TPM Management says “The TPM is not ready for use.”
Windows Security shows a security processor warning.
BitLocker can’t use the TPM.
A compatibility tool says TPM 2.0 is unavailable.

Why it happens: Windows sees the processor, but its setup, firmware, or driver isn’t working.

Press Windows key + R.

Enter tpm.msc.

Windows Run dialog containing tpm.msc, with the Open field and OK button highlighted

Select OK.

Read the message under Status in the TPM Management console.

Check TPM Manufacturer Information for the Specification Version.

Trusted Platform Module Management console showing the Status section, manufacturer information, and Specification Version, with unique identifiers blurred

Verify the result: “The TPM is ready for use” confirms Windows can use it. “The TPM is not ready for use” means the chip needs attention. “Compatible TPM cannot be found” often means TPM is disabled in UEFI. The hardware may also be unavailable.

For a second check, right-click Start, select Terminal (Admin), and run:

Get-Tpm

TpmPresent : True means Windows detects the TPM. If you also see TpmReady : False, Windows hasn’t prepared it.

Common TPM Issues and Solutions

Fix #2: Initialize the TPM in PowerShell

Problem: tpm.msc reports “The TPM is not ready for use.” You may also see TpmPresent : True and TpmReady : False in Get-Tpm.

Why it happens: Windows detects the processor, but TPM setup didn’t finish. Its saved state may also be damaged. This fix often handles that exact combination.

Right-click Start.

Select Terminal (Admin).

Approve the User Account Control prompt.

Run:

Initialize-Tpm

Restart the PC if PowerShell or Windows asks you to.

Open tpm.msc again.

Verify the fix: The Status section should say “The TPM is ready for use.” If Initialize-Tpm can’t prepare the TPM, check UEFI next.

Fix #3: Enable TPM, Intel PTT, or AMD fTPM in UEFI

Problem: tpm.msc says “Compatible TPM cannot be found.” The Security processor option may also be missing from Windows Security.

Symptoms:

Get-Tpm shows TpmPresent : False.
TPM 2.0 disappears after a BIOS reset or update.
Windows 11 compatibility checks fail.

Why it happens: The security processor may be disabled in the PC’s UEFI firmware. Intel systems may call it Intel PTT or Platform Trust Technology. AMD systems often call it AMD fTPM or AMD PSP fTPM.

Save your work.

Open Settings > System > Recovery.

Find Advanced startup and select Restart now.

Windows 11 System Recovery settings showing Advanced startup and the Restart now button highlighted

Select Troubleshoot > Advanced options > UEFI Firmware Settings.

Windows Recovery Environment Advanced options screen with UEFI Firmware Settings highlighted

Select Restart to enter UEFI.

Open Security, Advanced, or Trusted Computing. The exact name depends on your PC or motherboard.

Enable TPM, Security Device Support, Intel PTT, Intel Platform Trust Technology, AMD fTPM, or AMD PSP fTPM.

Representative UEFI Security or Trusted Computing page showing a TPM, Intel PTT, or AMD fTPM control, with a note that menu names vary by manufacturer

Save the changes and exit UEFI.

If TPM was already enabled, disable it and save your changes. Restart, return to UEFI, and enable it again. Don’t clear the TPM during this process.

Verify the fix: Run tpm.msc. Windows should detect the TPM and show its maker information.

Secure Boot and TPM both support Windows 11 security, but they’re separate UEFI settings. You can enable Secure Boot while you’re there if the PC supports it. Turning it on won’t repair a TPM that hasn’t been initialized.

Fix #4: Check for TPM 2.0 in Windows Security

Problem: Windows detects a security processor, but you need to confirm it’s TPM 2.0.

Why it happens: Some older systems use TPM 1.2. Windows 11 expects TPM 2.0, so detection alone isn’t enough.

Open Start.

Search for and open Windows Security.

Select Device security.

Windows Security Device security page showing the Security processor section and Security processor details link

Select Security processor details.

Find Specification version.

Security processor details page showing Specification version 2.0 and the Security processor troubleshooting link, with unique device information blurred

Verify the result: Specification version 2.0 is the expected value. If you see 1.2, check UEFI for a TPM 2.0 mode. Check the PC maker’s support page for a firmware update too. Hardware that can’t provide TPM 2.0 may need service or replacement.

Fix #5: Reinstall the TPM Device

Problem: Trusted Platform Module 2.0 has a warning icon in Device Manager. The error may also start after a driver or Windows update.

Why it happens: Windows may have an old or damaged device entry. Reinstalling it gives the built-in driver a clean start.

Right-click Start.

Select Device Manager.

Expand Security devices.

Locate Trusted Platform Module 2.0.

Device Manager with Security devices expanded and Trusted Platform Module 2.0 highlighted

Right-click Trusted Platform Module 2.0.

Select Uninstall device.

Device Manager context menu for Trusted Platform Module 2.0 showing Uninstall device highlighted, with a note that Windows should reinstall it after restart

Confirm the uninstall.

Restart Windows.

This is normally safe. It removes the Windows device entry but leaves the TPM’s stored keys in place. Windows should detect the processor and reinstall its built-in driver after the restart.

Verify the fix: Return to Device Manager > Security devices. Trusted Platform Module 2.0 should appear without a warning icon. If it doesn’t return, check the UEFI setting again.

Fix #6: Install Windows, Driver, and Firmware Updates

Problem: The TPM error continues after initialization and driver reinstallation.

Why it happens: Old UEFI firmware, TPM firmware, or chipset drivers can block TPM communication. Intel Management Engine parts can cause the same problem. Firmware updates need care, but they’re the right next step.

Open Settings > Windows Update.

Select Check for updates.

Install all available security and quality updates.

Open Settings > Windows Update > Advanced options > Optional updates.

Install any available firmware, chipset, security processor, or system driver updates.

Windows Update Optional updates page showing available driver or firmware categories without implying that every PC has an update

Restart the PC.

Visit the official support page for your PC or motherboard maker.

Search with the exact model or serial number.

Install the latest BIOS or UEFI update, TPM firmware, chipset driver, and management-engine driver for your model.

Keep a laptop connected to its AC adapter during firmware updates. Connect a desktop to a reliable UPS if you have one.

Don’t download BIOS or driver packages from third-party driver sites. BIOS files are model-specific. Interrupting an update can stop the PC from starting. Follow the maker’s steps exactly.

Verify the fix: Run Get-Tpm. Both TpmPresent and TpmReady should show True.

Fix #7: Clear and Reinitialize the TPM

Problem: TPM errors remain after repairing Windows, UEFI, drivers, and firmware.

Why it happens: Keys or ownership data inside the TPM may be damaged. I’d save this fix for last because clearing the chip removes TPM-protected keys.

Warning: Save your BitLocker recovery key before clearing the TPM. Clearing removes TPM-protected keys. Windows may ask for the recovery key during startup. Encrypted data could become unavailable without it.

Back up important files.

Confirm that you have a usable BitLocker recovery key.

Open Windows Security.

Select Device security > Security processor details > Security processor troubleshooting.

Review the warning under Clear TPM.

Security processor troubleshooting page showing the Clear TPM control, with an annotation warning readers to save BitLocker recovery keys first

Select Clear TPM.

Restart the computer when prompted.

Complete any maker-specific confirmation shown during startup.

Sign back into Windows and let it initialize the TPM.

Verify the fix: Open tpm.msc and confirm it says “The TPM is ready for use.” Also confirm BitLocker protection is active if you paused it during troubleshooting.

TPM Error Messages Quick Reference

Error or Status	What It Means	Best Starting Point
“The TPM is not ready for use”	Windows sees the TPM but can’t use it yet	Run `Initialize-Tpm`
“Compatible TPM cannot be found”	TPM is disabled, hidden, or unavailable	Enable TPM, Intel PTT, or AMD fTPM in UEFI
`TpmPresent : True`, `TpmReady : False`	The TPM exists but isn’t prepared	Initialize it, then update firmware if needed
`TpmPresent : False`	Windows can’t detect a TPM	Check UEFI and Device Manager
“Security processor troubleshooting” warning	Windows found a TPM health or firmware problem	Install updates before considering Clear TPM
Specification version 1.2	The active TPM mode is older than Windows 11 expects	Check for TPM 2.0 mode or vendor firmware
Device Manager Code 10 or Code 43	The TPM device failed to start or respond correctly	Reinstall the device and update firmware

Windows 11 Configuration Issues

Several UEFI settings can look alike. They aren’t interchangeable, and changing the wrong one wastes time.

TPM versus Secure Boot: Both support Windows 11 security, but they’re separate UEFI settings. Enable each one when required.
Discrete TPM versus firmware TPM: Intel PTT and AMD fTPM provide TPM functions through system firmware. You often don’t need a separate TPM module.
TPM 1.2 versus TPM 2.0: Windows may detect a TPM with the wrong version. Confirm Specification version 2.0 in Windows Security.
Disabled after a BIOS reset: Loading UEFI defaults can turn off PTT or fTPM. Check the security settings after a BIOS reset or motherboard battery replacement.
Wrong firmware package: BIOS files are model-specific. A file made for a similar model can damage the system.

Consider a separate TPM module only if a compatible desktop motherboard lacks firmware TPM support. Check the motherboard manual before buying one. The header and module type must match.

Getting Help and Checking TPM Logs

Contact the PC or motherboard maker if the TPM keeps disappearing or initialization always fails. You should also call if UEFI has no TPM setting or the error returns after all updates. Failures in both Windows and UEFI often point to bad firmware or hardware.

To collect details for support:

Right-click Start.

Select Event Viewer.

Open Applications and Services Logs > Microsoft > Windows > TPM > Operational.

Note repeated event IDs, timestamps, and error text.

Run Get-Tpm in an elevated PowerShell window.

Record the values for TpmPresent, TpmReady, TpmEnabled, and TpmActivated.

Share the PC model, BIOS version, Windows build, TPM maker version, and related event details. Those facts can cut out a long round of basic questions. Microsoft’s official resources explain how to enable TPM 2.0, initialize the TPM, and update TPM firmware.

Prevention Tips

Save BitLocker recovery keys somewhere outside the encrypted PC.
Install Windows and optional driver updates regularly.
Get firmware only from the PC or motherboard maker’s official support page.
Keep the computer on stable power during BIOS and TPM firmware updates. A UPS adds protection for desktops.
Check PTT or fTPM after resetting UEFI settings.
Don’t clear the TPM as routine maintenance.
Create a current backup before changing encryption or firmware settings.

Wrapping Up

Step	Action	Applies To
1	Check `tpm.msc` and `Get-Tpm`	Every TPM error
2	Run `Initialize-Tpm`	TPM present but not ready
3	Enable PTT, fTPM, or TPM	TPM not detected
4	Reinstall the device	Driver warnings
5	Update Windows and firmware	Errors that persist
6	Clear the TPM after backing up keys	Corrupt TPM state

Running Initialize-Tpm or enabling Intel PTT or AMD fTPM fixes the usual cases. If the TPM still disappears after every update, I’d contact the maker. A motherboard or firmware fault is then more likely.