TPMAPI_E_INVALID_KEY_BLOB (0X80290116) – Quick Fixes That Work

What This Error Actually Means

You got TPMAPI_E_INVALID_KEY_BLOB with code 0X80290116. The TPM (Trusted Platform Module) is telling you: "the data you gave me doesn't look like a valid key." That sounds like a cryptic IT thing, but here's what usually causes it:

• You recently updated the TPM firmware (like a BIOS update that included TPM changes)
• You made a backup of TPM keys and tried to restore them from a different machine
• BitLocker or some encryption software lost its mind after a crash
• A third-party app tried to use TPM keys that got corrupted

I've seen this mostly on Lenovo and Dell laptops after firmware updates. One client had a Dell Precision 7730 that threw this error after a BIOS update — took me 10 minutes to fix.

The 30-Second Fix: Reboot and Check TPM Status

First thing: reboot your machine. I know it sounds dumb, but TPM state can get stuck after a firmware update. A clean boot clears the TPM's internal buffers.

If the reboot doesn't fix it, open tpm.msc (hit Windows+R, type tpm.msc, press Enter). Look at the status. If it says "The TPM is ready for use" and you see version info, the TPM itself is fine — the problem is the key blob being passed to it.

If it says anything like "TPM not detected" or "Compatibility mode", you've got a bigger problem. Skip to the moderate fix.

The Moderate Fix (5 Minutes): Clear and Reinitialize the TPM

Warning: This will wipe all TPM keys. If you use BitLocker, make sure you have your recovery key first. Go to your Microsoft account or where you saved it. Don't skip this — I've had clients lose data because they didn't check.

Here's the step-by-step:

1. Open an admin PowerShell or Command Prompt
2. Type: Disable-TpmAutoProvisioning (this stops Windows from messing with the TPM while you work)
3. Then: Clear-Tpm
4. Reboot your machine. Windows will reinitialize the TPM on next boot.
5. After reboot, check tpm.msc again — it should show the TPM as ready.

If you don't have PowerShell, you can clear the TPM from BIOS/UEFI. Restart, mash F2/Del (varies by brand), look for "TPM" or "Security" settings, and find "Clear TPM" or "Reset TPM". On a Lenovo ThinkPad it's under Security > Security Chip > Clear.

After clearing, the error should be gone. If not, move to the advanced fix.

The Advanced Fix (15+ Minutes): Reinstall TPM Drivers and Rebuild Keys

If clearing the TPM didn't work, the issue is likely a corrupted driver or a stuck provisioning state. Here's the nuclear option:

Step 1: Uninstall the TPM Driver

1. Open Device Manager (right-click Start > Device Manager)
2. Look under "Security Devices" — you'll see "Trusted Platform Module 2.0" or similar
3. Right-click and select "Uninstall device" — check the box that says "Delete the driver software for this device"
4. Reboot. Windows will reinstall the driver automatically.

Step 2: Reset TPM Provisioning State

Open Registry Editor (Windows+R, type regedit, press Enter). Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TPM\WMI

Look for a value called ProvisioningState. If it's set to 1, change it to 0. This forces Windows to re-provision the TPM on next boot.

Don't touch anything else in that key. I once saw a guy delete the whole TPM registry key — bad idea. Just change that one value.

Step 3: Re-enable Auto-Provisioning

In an admin PowerShell, run:

Enable-TpmAutoProvisioning

Reboot one more time. Check tpm.msc — it should show the TPM as ready and the error should be gone.

If none of this works, you might have a hardware TPM failure. I've seen that on some older HP EliteBooks. In that case, check your motherboard for a TPM chip that's loose or dead. But that's rare — 90% of the time, the clear-and-reinstall method fixes it.

Quick Recap

That's it. Start with the reboot, then move up if needed. Don't waste time on anything else — this error is almost always a corrupted blob, not a hardware failure.