TPM drivers
Trusted Platform Module drivers essential for Windows 11.
You might also need
TPM drivers we cover
What does a tpm driver do?
A Trusted Platform Module is a small, isolated cryptographic processor with its own protected storage. It performs a fixed menu of security operations: generating and storing keys that never leave the chip, hashing boot measurements, and signing attestation statements that prove what code the machine booted. The TPM driver, tpm.sys in Windows, is the transport that carries commands and responses between the OS and that processor over the TPM's command interface.
The module comes in three physical forms, and the driver abstracts all of them. A discrete TPM (dTPM) is a dedicated chip soldered to the board or on a header. Intel PTT and AMD fTPM are firmware TPMs, running the same TPM 2.0 command set inside a protected mode of the CPU rather than in separate silicon. To Windows they look alike, because the driver presents one standard interface regardless of the underlying implementation.
Why keeping it updated matters
The tpm.sys driver itself is an in-box Windows component and rarely needs a manual refresh. What genuinely matters is the firmware behind a firmware TPM, and updating that resolves the problems people actually hit. Early AMD fTPM implementations were notorious for periodic stutter, brief system pauses caused by the fTPM stalling the bus while it accessed SPI flash, and the fix arrived as an AGESA BIOS update rather than any Windows driver change.
Firmware revisions also repair attestation and PCR behaviour. A buggy fTPM can compute a PCR value inconsistently across boots, which breaks the BitLocker seal and forces a recovery-key prompt every startup even though nothing about the disk changed. Updated firmware makes the measurement deterministic again, restoring the seal.
Common warning signs of tpm driver failure
- BitLocker demands its 48-digit recovery key on every boot even though the disk and hardware are unchanged
- AMD fTPM causes brief, repeating stutters or audio dropouts during gaming or heavy I/O
- Windows 11 setup reports the PC is unsupported because no TPM 2.0 is detected
- The security processor shows a yellow triangle or 'device cannot start' in Device Manager
- An anti-cheat system refuses to launch a game, citing a missing or non-compliant TPM 2.0
- tpm.msc reports the TPM is not ready, or shows a 1.2 module where 2.0 is expected
How to fix tpm driver problems
Check TPM state in the console
Run tpm.msc from the Start menu and read the Status and TPM Manufacturer Information. Confirm it reports 'The TPM is ready for use' and specification version 2.0; if it shows 1.2 or 'not ready', the issue is configuration or firmware, not tpm.sys.
Enable the TPM in UEFI
If no TPM appears, enter UEFI and enable the security processor: Intel PTT under PTT/Trusted Computing, or AMD fTPM under the security or AMD CBS menu. Save and reboot, then re-check tpm.msc; the module should now enumerate as 2.0.
Fix AMD fTPM stutter with firmware
If you notice periodic stutters on an AMD system, update the board BIOS to a version whose notes cite the fTPM/AGESA fix. This is a firmware change, not a driver reinstall, and it is the only dependable fix for stutter caused by the fTPM stalling the bus.
Stop the recovery-key loop
If BitLocker prompts every boot, enter the recovery key once, then in Windows suspend and resume BitLocker so it re-seals to the current PCR values. If a firmware change altered the measured boot path, this realigns the seal and stops the loop.
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why does BitLocker ask for my recovery key on every boot when my TPM is present?
BitLocker seals its volume key to specific Platform Configuration Register values. If a firmware change or a buggy fTPM computes those PCRs differently each boot, the seal no longer matches and BitLocker falls back to the recovery key. Enter the key once, then suspend and resume BitLocker so it re-seals to the current, stable PCR state.
Why does my AMD fTPM cause stuttering in games and audio?
Early AMD fTPM firmware accessed SPI flash in a way that briefly stalled the bus, producing periodic micro-stutters. Because the fTPM runs in AGESA, the correct fix is a board BIOS update whose notes cite the fTPM repair, not a Windows driver change. Updating firmware for your exact model removes the stall.
Why does Windows 11 say my PC has no TPM 2.0 when the hardware supports it?
Firmware TPMs ship disabled on many boards. Windows sees no module until you enable Intel PTT or AMD fTPM in the UEFI menu, usually under a Trusted Computing or security section. Enabling it and rebooting makes the module enumerate as TPM 2.0, after which the Windows 11 check passes.