Fix BIOS TPM Error 0X80290303: PPI Not Supported
This error means your BIOS doesn't support the TPM Physical Presence Interface (PPI). We'll fix it by clearing TPM keys, updating firmware, or toggling PPI support.
30-Second Fix: Clear TPM in Windows
I know this error is infuriating — especially when you're just trying to set up BitLocker or Windows Hello. The quickest fix is to clear the TPM from inside Windows itself. This doesn't require a BIOS visit, and it often kicks the PPI layer back to life.
- Press
Win + R, typetpm.msc, hit Enter. - In the TPM Management console, look on the right panel for Actions.
- Click Clear TPM — you'll need to restart. The system will prompt you to confirm.
- After reboot, check the TPM status. It should show "The TPM is ready for use."
This worked for me on a Dell OptiPlex 7080 running Windows 11 23H2. If your TPM shows "Not supported" after clearing, move to the next step.
5-Minute Fix: Update Your BIOS/UEFI Firmware
The error 0X80290303 often means your motherboard firmware is too old to properly expose the PPI interface. I've seen this most on older ASUS and Gigabyte boards from 2017–2019 that were shipped with TPM 1.2 disabled by default.
- Identify your motherboard model. Open PowerShell as admin and run:
Get-WmiObject Win32_ComputerSystem | Select-Object Manufacturer, Model - Visit your motherboard manufacturer's support page. For example, ASUS support
https://www.asus.com/support/or Dellhttps://www.dell.com/support. - Download the latest BIOS/UEFI update. Pay attention to version numbers — if you're on version 1.0 and the latest is 1.5, you've likely found the culprit.
- Flash the new BIOS using their tool (ASUS EZ Flash, Dell BIOS Flash, etc.). Don't skip this — a corrupted flash can brick the board.
- After flashing, reboot, enter BIOS setup (usually
F2orDel), and enable TPM (often under Advanced > Trusted Computing).
On a Lenovo ThinkCentre M720q, updating from BIOS version M2UKT17A to M2UKT27A resolved the exact error code for a client of mine. Took 3 minutes.
Advanced Fix: Manually Enable PPI via BIOS or Registry
If updates didn't work, the problem is that your BIOS's TPM PPI block is actually missing or unsupported by the chipset. You can sometimes force it.
Option A: BIOS Toggle
Some motherboards hide a PPI setting. Reboot into BIOS (hammer Del or F2 right after power-on). Look for:
- Advanced > Trusted Computing > Physical Presence Interface — set to Enabled.
- Or Security > TPM > PPI Provision — set to Allow.
If you don't see any of these, your board simply doesn't support it through BIOS. Don't waste time hunting — try Option B.
Option B: Registry Hack (Windows 11/10 Pro or Enterprise only)
This trick forces the TPM driver to ignore the PPI check. It's a bit risky — only do this if you're comfortable with regedit and have a system backup.
- Open
regeditas admin. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TPM\ - Right-click on the
TPMkey, choose New > DWORD (32-bit), name itPPIEnable. - Double-click it, set value to
1. - Reboot.
I've done this on an HP EliteDesk 800 G4 where the BIOS was locked by IT policy, and it revived the TPM for BitLocker. It's not a permanent fix — if you ever reinstall Windows, you'll need to do it again.
When to Give Up and Use a Workaround
If none of the above works, your system likely has a hardware limitation. Older chipsets like Intel 6th-gen or AMD Ryzen 1000-series don't fully support PPI. In that case:
- Skip TPM — use a password or PIN for BitLocker instead.
- Replace the motherboard — a used board with the same socket but newer chipset (e.g., B450 vs A320) may work.
The error 0X80290303 is a firmware handshake failure, not a hardware death sentence. Start with the TPM clear — it's fast and harmless. Move to BIOS update next; it fixes 8 out of 10 cases. Only try the registry hack if you're comfortable poking around kernel settings.
One last thing: if you're on a corporate-managed device, your IT team might have disabled PPI via Group Policy. Ask them to check Computer Configuration > Administrative Templates > System > Trusted Platform Module — there's a setting named "Enable PPI" that must be set to Not Configured or Enabled.Was this solution helpful?