0X80290214

Fix TBSIMP_E_INVALID_RESOURCE (0x80290214) TPM Error

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Jul 31, 2026 👁 8 views Windows Errors Intermediate
This error pops up when Windows can't write to the TPM because the resource type doesn't match what the TPM expects. Usually happens after a BIOS update or TPM firmware upgrade.

You're trying to set up Windows Hello or enable BitLocker, and boom — you get error 0x80290214 (TBSIMP_E_INVALID_RESOURCE). It usually shows up right after a BIOS update, a TPM firmware upgrade, or swapping a motherboard. The system says the TPM is there, but it rejects any command that tries to create or use keys. Annoying as hell.

What Causes This

The Trusted Platform Module (TPM) keeps a tiny internal database of resources — keys, hashes, attestation data. Each resource has a type tag. After a firmware update, the TPM's internal state can get corrupted. The TPM Base Services (TBS) layer sees a resource but the type tag doesn't match what it expects. So it throws this error instead of trying to use it.

The culprit here is almost always a partial or interrupted TPM firmware update. BIOS updates often include TPM firmware blobs, and if that flash fails mid-way, the TPM ends up with mismatched resource types. It's not a security problem — it's just a data integrity issue inside the TPM's volatile memory.

Fix It — Clear and Reset the TPM

Don't bother reinstalling Windows or running SFC /scannow — that won't touch the TPM's internal storage. The only reliable fix is to clear the TPM. This removes all keys, so back up your BitLocker recovery key first if you use it.

Step 1: Back Up BitLocker Recovery Key

If you use BitLocker, get your recovery key before touching the TPM.

  1. Open Control Panel > BitLocker Drive Encryption.
  2. Click Back up your recovery key next to the OS drive.
  3. Save it to your Microsoft account, a USB drive, or print it. Don't skip this.

Step 2: Clear the TPM from Windows

This is the quickest method. You need local admin rights.

  1. Press Win + R, type tpm.msc, hit Enter.
  2. In the TPM Management console, click Clear TPM on the right panel.
  3. You'll be prompted to restart. The system will reboot and enter UEFI/BIOS to clear the TPM.
  4. After restart, the TPM will be initialized fresh by Windows.

Step 3: If the GUI Fails, Use Command Line

Sometimes the GUI won't let you clear if the TPM is in a bad state. Use PowerShell instead.

# Run as Administrator
Clear-Tpm -Force
Restart-Computer

After reboot, check the TPM status again with Get-Tpm.

Step 4: Alternative — Clear from BIOS/UEFI

If Windows can't talk to the TPM at all, clear it from firmware.

  1. Restart and mash F2 (Dell), Del (ASUS), F10 (HP), or the key your board uses to enter BIOS.
  2. Look for Security > TPM or Trusted Computing.
  3. Find Clear TPM or Factory Reset TPM. The wording varies.
  4. Save and exit. Boot into Windows. It should re-initialize the TPM automatically.

What to Check If It Still Fails

If you've cleared the TPM and the error comes back, a few things to verify:

Check the TPM Driver

Windows might have picked up a corrupt driver for the TPM chip. Reinstall it.

  1. Open Device Manager.
  2. Expand Security devices. You'll see Trusted Platform Module 2.0.
  3. Right-click it, choose Uninstall device. Check Delete the driver software for this device if it's available.
  4. Restart. Windows will reinstall the driver fresh.

Update Chipset Drivers

TPM communication goes through the chipset. Go to your motherboard manufacturer's site and grab the latest chipset driver. For Intel systems, that's the Intel Management Engine (ME) driver. For AMD, it's the chipset driver package. Install it, reboot.

Verify TPM Firmware Version

Some OEMs shipped TPMs with buggy firmware versions. Check your TPM firmware version in tpm.msc under Specification version. Then visit your PC or motherboard support page and look for a TPM firmware update. Lenovo and Dell both have released TPM firmware updates specifically to fix resource type mismatch bugs. Apply it even if it's a few months old.

Hardware TPM vs. Firmware TPM

If you're on an AMD system with a discrete TPM module (a separate chip on the motherboard), check that it's seated correctly. Power off, unplug, reseat the TPM module. I've seen bent pins cause this exact error more than once. For Intel systems with firmware TPM (PTT), there's nothing to reseat — just make sure it's enabled in BIOS.

Last Resort — Reset the BIOS to Defaults

I don't like doing this because it resets all your custom settings, but it works when BIOS and TPM state get out of sync. Go into BIOS, load optimized defaults (often F5), save and exit. Then clear the TPM again from Windows. That sequence resolves some really stubborn cases.

If none of that works, your TPM chip might be physically dead. You can test it by running a Linux live USB with tpm2-tools installed and running tpm2_getrandom 8. If that fails with a hardware error, replace the motherboard or TPM module. But honestly, 9 times out of 10, clearing the TPM and updating the driver does the trick.

Related Errors in Windows Errors
0X80342001 Fix ERROR_NDIS_DOT11_MEDIA_IN_USE (0x80342001) Now 0X00000598 0x598: Invalid LB Message in Single-Select Listbox 0XC00D1394 Fix Windows Media Player Error 0XC00D1394 Fast 0XC0000235 STATUS_HANDLE_NOT_CLOSABLE (0XC0000235) Fix — NtClose on Protected Handle
TBSIMP_E_INVALID_RESOURCE 0x80290214 TPM error Trusted Platform Module Windows Hello failure BitLocker error TPM resource type mismatch TPM firmware update issue clear TPM fix TPM error Windows 11 TPM initialization failure TPM base services error TPM driver reinstall TPM BIOS settings

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.