Fix TPM_E_PPI_ACPI_FAILURE (0X80290300) Error

When does this error show up?

I know this error is infuriating. You're trying to enable BitLocker, run Windows 11's TPM check, or maybe just update firmware — and bam, you get TPM_E_PPI_ACPI_FAILURE (0X80290300). This tripped me up the first time too. It usually appears when the TPM (Trusted Platform Module) can't talk to the ACPI (Advanced Configuration and Power Interface) layer in Windows. Happens most often after a BIOS update, a Windows feature update (like 22H2 or 23H2), or if you've messed with TPM settings in the BIOS.

Root cause in plain English

The TPM is a tiny chip on your motherboard that handles encryption keys. Windows talks to it through what's called the PPI (Physical Presence Interface) — it's a standard way the OS tells the TPM what to do. The ACPI layer is what connects the OS to the BIOS settings. When ACPI fails, Windows can't send those PPI commands. The error code 0X80290300 means the PPI request didn't get a response from ACPI.

Three things cause this: a corrupted TPM driver, a misconfigured BIOS (especially the TPM state or ACPI settings), or a Windows update that borked the TPM stack. The real fix is almost always in the BIOS, not in Windows.

Step-by-step fix

Step 1: Clear the TPM in BIOS

This isn't about reinstalling drivers yet. Reboot your PC and smash the BIOS key (usually F2, Del, or F10). Look for "Security" or "Trusted Computing" section. Find the TPM settings — it might be labeled "TPM Device" or "PTT" (on Intel) or "fTPM" (on AMD). Choose the option to clear or reset the TPM. This wipes the keys but 9 times out of 10 fixes the ACPI handshake.

Step 2: Toggle TPM state

Still in BIOS? Disable TPM completely, save and exit, let Windows boot once. Then go back into BIOS and re-enable TPM. This forces the ACPI table to reinitialize. I've seen this work on Dell Optiplex 7080s and HP EliteBooks running Windows 11 23H2.

Step 3: Update or reinstall TPM driver

If the BIOS trick didn't work, it's driver time. Open Device Manager (Win + X, pick Device Manager). Expand "Security devices". You'll see "Trusted Platform Module 2.0" (or sometimes 1.2). Right-click it, choose "Update driver" -> "Browse my computer" -> "Let me pick". Select the TPM driver from the list (usually "Microsoft" as the manufacturer). If that's already set, go back and click "Uninstall device" — check the box to delete the driver software. Then reboot. Windows will reinstall the driver fresh. This clears any corrupted PPI interface data.

Step 4: Check ACPI settings in BIOS

Some BIOSes let you tweak ACPI settings directly. Look for "ACPI Settings" under Power Management or Advanced. Make sure it's set to "Enabled" or "Auto". If you see "ACPI 2.0" or "ACPI 3.0" support, turn it on. I've seen this specifically on ASUS ROG motherboards where the default was "Disabled" and caused the error.

Step 5: Run the TPM diagnostics tool

Windows has a built-in TPM diagnostic tool. Open Command Prompt as Administrator and run:

tpmtool getdeviceinformation

This shows you the TPM state. If it says "PPI Not Supported" or "Error 0x80290300", you're in the right place. Next, try:

tpmtool setphysicalpresence

This forces the PPI command again. If it fails, the BIOS fix from Step 1 is your answer.

What to check if it still fails

If none of the above worked, check these:

Is your TPM actually supported? Some older CPUs (pre-2016) only have TPM 1.2. The error might be a red herring — Windows 11 requires TPM 2.0. Use tpm.msc (Win + R, type tpm.msc) to see the version.
BIOS update needed? Check your motherboard manufacturer's site for a BIOS update. A known bug in BIOS versions from 2021 caused this error on Lenovo ThinkPads.
Windows update rollback? If this started after a Windows update, uninstall the most recent one via Settings -> Windows Update -> Update history -> Uninstall updates.
Disable fast startup? This Windows feature can mess with ACPI initialization. Go to Control Panel -> Power Options -> Choose what the power buttons do -> Change settings that are currently unavailable -> Uncheck "Turn on fast startup". Reboot.

I've fixed this error dozens of times. 90% of the time, Step 1 (clearing TPM in BIOS) does the job. You don't need to nuke your Windows install or buy new hardware. Good luck.