TPM Device Not Detected: Fix It in Firmware, Then in Windows

Updated: October 2026

A laptop boots to a black screen that says the TPM is missing, or Windows 11 refuses to install because it can't find one. Usually the chip is still there. It's switched off, hidden by firmware, or confused after an update, and the fix order matters because the wrong first move can lock someone out of their own BitLocker drive.

Two Errors, One Missing Chip

A TPM (Trusted Platform Module) is a small security processor that stores keys the machine uses to prove it's itself. BitLocker keeps its drive key there, Windows Hello keeps sign-in keys there, and Windows 11 won't install without one.

"TPM device not detected" shows up in two places, and they point at different layers. On Dell machines, the first is a startup alert before Windows loads: "Alert! TPM device is not detected", with options to press F1, F2 or F5. That's the firmware talking. The second is inside Windows, when tpm.msc says "Compatible TPM cannot be found". That's Windows failing to see a chip the firmware may or may not be exposing.

Figure out which one you have before touching anything. A startup alert is a firmware job. A Windows-only message can be firmware, a driver, or initialization.

Check What Windows Sees First

Three places tell you what Windows can see. Run tpm.msc for the management console, or open Windows Security, then Device security, then Security processor details. For something you can script, run this in an elevated PowerShell window:

powershell
Get-Tpm

Read four lines of the output. TpmPresent says whether Windows can see a TPM at all. TpmReady says whether it's initialized and usable. TpmEnabled and TpmActivated say whether it's switched on.

If TpmPresent is False, go to firmware. If it's True and TpmReady is False, stay in Windows: the chip is there, and initialization is the problem. The cmdlet's properties are documented in Microsoft's Get-Tpm reference.

Fix It in Firmware

Start with the cheapest fix. Dell's own troubleshooting article tells you to drain residual power: on a laptop, unplug the charger and hold the power button for more than 60 seconds, or disconnect the battery if you can. On a desktop, unplug the power cable and do the same. It sounds like folklore, and it's the first step in Dell's own list.

Next, update the BIOS. Dell lists it as the step before any other change, and our guide to BIOS updates covers doing that safely across machines. Suspend BitLocker before you flash, or the next boot will ask for the recovery key.

Then check the TPM is switched on in UEFI. The hard part is finding it, because vendors name it differently. Microsoft's list of labels to look for includes "Intel PTT", "Intel Platform Trust Technology", "AMD fTPM switch", "AMD PSP fTPM", "Security Device Support", "Security Device" and "TPM State". The "f" and "PT" versions are firmware TPMs built into the processor platform, which is why they live next to chipset settings. On Dell business machines, Dell also asks you to make sure TPM On and Activate are checked, along with Attestation Enable and Key Storage Enable.

In this r/Dell thread, a tech responsible for around a thousand Precision laptops gives the order that works for them: disconnect the battery for a few seconds, then make sure both the BIOS and the TPM firmware are current.

Before You Clear the TPM, Save the BitLocker Key

Clearing the TPM is the fix every forum reaches for, and it's the one with a cost. Microsoft's TPM troubleshooting guide is plain about it: clearing loses every key the TPM created, and the data those keys protect, such as a virtual smart card or a sign-in PIN. On a BitLocker drive, that means the recovery key is the only way back in.

So confirm the recovery key is stored somewhere you can reach first: Entra ID, Active Directory, or your management tool. Microsoft's other rules for clearing are worth following as written. Use Windows (tpm.msc or Windows Security) to clear it, not UEFI. And don't clear a work PC without the IT team's say-so, which is a useful line to quote to a user who found the button themselves.

The video below shows both errors on a Dell Latitude, the startup alert and the "Compatible TPM cannot be found" message, and the firmware setting that fixed it.

If BitLocker does ask for the key after a firmware change, our guide to recovery mode covers what the user sees and what to do next.

How to Clear the TPM in Windows 11

With the recovery key saved, the steps are short. You need local admin rights.

1. Open Windows Security and select Device security.
2. Select Security processor details, then Security processor troubleshooting.
3. Select Clear TPM and restart when prompted.

During the restart, the firmware may ask you to press a key to confirm. That prompt proves someone is at the machine, so it can't be scripted away. After the restart, Windows prepares the TPM for use again on its own.

The TPM console does the same job: run tpm.msc and choose Clear TPM in the Action pane. From PowerShell, Clear-Tpm -UsePPI queues the request, and it takes effect on the next restart, which can still ask for that confirmation. Afterwards, run Get-Tpm and check that TpmPresent and TpmReady both read True.

When Windows Still Can't Find It

If firmware shows the TPM switched on and Windows still says it's missing, Microsoft names four causes worth checking.

A non-Microsoft TPM driver can stop Windows loading its own, and BitLocker will then report no TPM. Microsoft's advice is to remove it and let Windows initialize the TPM again. UEFI can also hide the TPM from the operating system while leaving it switched on, so look for a visibility setting next to the enable switch.

The third cause catches domain-joined laptops. If Group Policy requires TPM recovery information to be saved in Active Directory, and the machine can't reach a domain controller, Windows 11 can't finish initializing the TPM. Connect it to the corporate network, or the VPN, and let it initialize there.

The fourth is rare: systems with two TPMs where someone toggled between them. Microsoft says Windows doesn't support switching, and doing it puts BitLocker into recovery. If none of that applies and the alert keeps coming back, you're looking at a board repair, which is where one 2026 r/Dell thread about an XPS ended.

Check TPM Across a Fleet

One machine is a ticket. A fleet is a project, and Windows 11 made it one: the Windows 11 specifications require TPM 2.0.

That stopped being optional when Windows 10 reached end of support on October 14, 2025. Every device without a working TPM 2.0 is now either an upgrade blocker or a replacement.

Run Get-Tpm through your RMM and collect TpmPresent, TpmReady and the spec version, or query the data you already collect. The open-source osquery agent has a tpm_info table that reports whether each device's TPM is enabled, activated and owned, plus its spec version. OpenFrame's endpoint inventory runs on osquery, so that state can come straight from the machines instead of a spreadsheet.

The part to plan for is BitLocker. In this r/sysadmin thread, an admin with 1,600 endpoints and a lot of outdated firmware asks what happens when Secure Boot and firmware updates meet BitLocker. The replies are practical: have the recovery keys ready, and expect some remote devices to land on the recovery screen.

The order that keeps a fleet rollout calm is the same as for one machine: know which devices have a TPM, escrow every recovery key, update firmware in rings, then clear only what still fails.

Find the Layer, Then Fix It

"TPM device not detected" is usually a switch, a stale BIOS or a driver, not a dead chip. Check what Windows sees, fix firmware before Windows, and never clear a TPM until the recovery key is somewhere you can reach.

Firmware is where the fixes start, so our guide to BIOS updates is the next read.