TBSIMP_E_TPM_ERROR (0X80290204) Fix

Cause 1: TBS Service is Stuck or Disabled

What's actually happening here is that the TPM Base Services (TBS) – the Windows service that acts as a translator between your OS and the TPM chip – has stopped responding or was manually disabled. Error 0x80290204 appears because the TBS service returns a timeout or an invalid handle when the TPM driver tries to talk to the hardware. You'll see this most often after a Windows update that restarts the TBS service without properly reinitializing it, or after a forced shutdown that leaves the service in a zombie state.

Fix: Restart the TBS Service

1. Press Win + R, type services.msc, and hit Enter.
2. Find TPM Base Services in the list. Its display name is exactly that – don't confuse it with anything else.
3. Right-click it and select Restart. If the option is grayed out, the service is disabled. Double-click it, set Startup type to Automatic, click Apply, then select Start.
4. Close the window and run the operation that triggered the error again – usually a BitLocker unlock or a TPM provisioning tool.

The reason step 3 works is that the TBS service holds a critical handle to the TPM hardware. When Windows updates or crashes, that handle can become orphaned. A full restart of the service forces Windows to release the old handle and request a fresh one from the TPM driver. If the error persists, move to the next cause.

Cause 2: Corrupted TPM Driver Stack

If the TBS service is running but the error still shows up, the TPM driver stack itself might be corrupted. This happens after a failed driver update or when a third-party security tool (I'm looking at you, some antivirus suites) hooks into the TPM stack and breaks the communication chain. The error code stays the same because TBS can't complete the handshake with the TPM hardware.

Fix: Reinstall the TPM Driver from Device Manager

1. Press Win + X and select Device Manager.
2. Expand Security devices (not System devices – this is a common mistake). You'll see Trusted Platform Module 2.0 or similar.
3. Right-click the TPM device and select Uninstall device. Check the box that says Delete the driver software for this device if it appears – it won't always show up, but if it does, check it.
4. Reboot your machine. Windows will automatically reinstall the built-in TPM driver from its driver store during boot.

What's actually happening here is that Windows stores a backup copy of the TPM driver in C:\Windows\System32\DriverStore. By removing the active driver, you force the PnP system to pull a fresh copy from that store. This clears any registry entries or file references that got corrupted. If you're on a Dell or Lenovo system, you might also need to run tpm.msc after reboot to reinitialize the TPM – but normally Windows handles that automatically.

Cause 3: TPM Firmware Corruption (Rare but Real)

This one's uncommon – maybe 1 in 100 cases – but when it hits, nothing else will fix it. The TPM chip's internal firmware gets corrupted, usually from a failed BIOS update that touched the TPM, or from a power failure during a TPM clear operation. Error 0x80290204 becomes persistent across reboots and service restarts. You'll also notice that tpm.msc shows "Compatible TPM cannot be found" even though the BIOS clearly has it enabled.

Fix: Clear the TPM via UEFI/BIOS

1. Restart your PC and enter the BIOS/UEFI setup (usually F2, Del, or F10 – varies by manufacturer).
2. Look for a Security tab, then find TPM or Intel PTT or AMD fTPM.
3. Select Clear TPM (sometimes called Reset TPM or Erase TPM). Confirm the prompt.
4. Save and exit. Windows will boot fresh, and the TPM will reinitialize with factory firmware.

The reason this works is that clearing the TPM from the BIOS level rewrites the internal state of the TPM chip – it doesn't just reset the OS-side data. This is the nuclear option: you'll lose any keys stored in the TPM (like BitLocker recovery keys – have those backed up!). But for the actual firmware corruption, this is the only path that touches the hardware directly.

Important note: Never clear the TPM from within Windows if you get error 0x80290204 – the TBS service can't communicate, so the Windows tool will just fail. Always do it from the BIOS.

Quick-Reference Summary Table