Fix 0x8029021A TPM Incompatible Error on Windows

TBS can't talk to your TPM chip because the TPM driver or firmware is out of date. On older systems like a TPM 1.2 chip on Windows 10/11, this error pops up when Secure Boot or TPM is misconfigured.

Quick answer (for pros)

Run tpm.msc to check TPM version — if it shows 1.2 but Windows expects 2.0 (common on Windows 11), your hardware won't work without a firmware update. Clear TPM in UEFI, then update the TPM driver from the OEM's site.

What's going on

This error means the TBS (TPM Base Services) can't talk to your TPM chip. The culprit here is almost always a version mismatch. TBS expects TPM 2.0, but the chip is running 1.2. This happens on older machines you've upgraded to Windows 10 or 11, or on systems where the TPM firmware never got updated. I've seen it on Dell OptiPlex 7040s and some Lenovo ThinkPads from 2016. Another common trigger: you just enabled TPM in BIOS after it was disabled, and the OS hasn't cleared the old state. Don't bother reinstalling Windows — that rarely helps.

Fix steps

Check your TPM version. Press Win + R, type tpm.msc, hit Enter. Look at "Specification version" — if it says 1.2, you're on old hardware. If it says 2.0, skip to step 3.
Update TPM firmware. Go to your motherboard or laptop manufacturer's support page. Search for "TPM firmware update". For Dell, use the Dell Command Update tool. For Lenovo, look under BIOS/UEFI updates in System Update. This is the real fix — a firmware update bumps 1.2 to 2.0 on most systems that support it.
Clear TPM from UEFI. Reboot and enter BIOS/UEFI (usually F2, F12, or Del during boot). Find the TPM section — it might be under Security or Advanced. Look for "Clear TPM" or "Reset TPM". Select it, confirm, save and exit. This wipes the old keys and resets the chip.
Clear TPM from Windows. If you can boot to Windows, open PowerShell as admin and run:
```
Clear-Tpm
```
If it fails (it will if TBS can't talk), you'll need to do it from UEFI anyway.
Update TPM driver. Open Device Manager, expand "Security devices", right-click "Trusted Platform Module 2.0" (or 1.2), choose "Update driver" > "Browse my computer" > "Let me pick" > select the TPM driver from Microsoft's list. If you see "Trusted Platform Module 1.2", you need the firmware update from step 2.

Alternative fixes

If the main fix didn't work, try these:

Disable and re-enable TPM in UEFI. Set TPM to "Disabled", save and reboot. Then go back in and set it to "Enabled". This forces the chip to reinitialize.
Check Secure Boot. Some systems require Secure Boot enabled for TPM 2.0 to work. In UEFI, find Secure Boot and set it to "Enabled" (not Standard). Then reboot.
Run the TPM troubleshooter. Windows includes one — go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > TPM. It rarely fixes the issue, but it's worth a shot before you give up.
Reset BIOS to defaults. In UEFI, find "Load Optimized Defaults" or "Reset to Default". Save and exit. Then re-enter UEFI and enable TPM. This clears any weird leftover configurations.

Prevention

Once you get this fixed, don't let it happen again. Keep your TPM firmware updated — check your OEM's support site every 6 months or so. If you're building a new system, buy a motherboard with TPM 2.0 built-in (most modern boards from 2020 onward have it). Avoid messing with TPM settings in UEFI unless you really need to — every time you toggle it, you risk corrupting the state. And if you're on Windows 11, make sure your TPM is 2.0 before you upgrade. Check with tpm.msc first. Saves you this headache.