0X80290201

TBSIMP_E_CLEANUP_FAILED (0X80290201) Fix Guide

This error means the TPM Base Services couldn't clean up a context. Usually happens after a failed TPM operation or driver hiccup on Windows 10/11.

Quick answer

Open PowerShell as admin and run Clear-Tpm -AllowClear. Then reboot. If that doesn't fix it, you'll need to reset the TPM from UEFI or reinstall the TPM driver.

What's actually happening here

The error code 0X80290201 maps to TBSIMP_E_CLEANUP_FAILED in the TPM Base Services (TBS) layer. This isn't a hardware failure — it's a software lock. The TPM got stuck in a state where the context (basically a session handle) couldn't be released. I see this most often after a BitLocker recovery, a failed Windows update, or when someone's app tried to use the TPM and crashed mid-operation.

The TBS layer manages all TPM requests from Windows apps. When an app doesn't properly close its TPM session, the TBS driver holds onto the context. After a few of these pile up, you get the 0X80290201 error on any new TPM request. Think of it as a stuck door — the TPM is fine, but the door handle won't turn.

Step-by-step fix

  1. Open PowerShell as administrator. Right-click the Start button and select "Windows PowerShell (Admin)" or "Terminal (Admin)" on Windows 11.
  2. Check your TPM status. Type Get-Tpm and press Enter. Look at the output — you'll see lines like TpmPresent, TpmReady, and TpmEnabled. If TpmPresent is False, you've got a hardware problem. If it's True but TpmReady is False, the TPM is stuck.
  3. Clear the TPM lock. Run Clear-Tpm -AllowClear. You'll get a prompt asking if you're sure. Type Y and press Enter. After that, you should see a message saying "The TPM was cleared successfully."
  4. Reboot your machine. This is critical — the TPM won't reinitialize until after a cold boot. Do a full shutdown, not a restart. Hold Shift while clicking Shut Down to force a full power-off.
  5. Verify the fix. After booting back up, run Get-Tpm again. You should see TpmReady: True and TpmEnabled: True.

Alternative fixes if the main one doesn't work

Sometimes Clear-Tpm throws an error itself — usually because Windows is blocking the clear operation. Here's plan B:

Reset TPM from UEFI/BIOS

  1. Restart your PC. During boot, press the key to enter UEFI setup — usually F2, Del, or F10 depending on your motherboard (ASUS uses F2, Dell uses F2, HP uses F10).
  2. Find the TPM settings. Look under Security, Advanced, or Trusted Computing. The exact path varies: on ASUS it's under Advanced > Trusted Computing, on Dell it's Security > TPM 2.0 Security.
  3. Clear or reset the TPM. There's usually an option labeled "Clear TPM" or "Reset TPM". Select it, confirm the warning, then save and exit.
  4. Boot back into Windows. Run Get-Tpm to confirm the TPM is ready again. If you had BitLocker enabled, you'll need your recovery key to unlock the drive.

Reinstall the TPM driver

  1. Open Device Manager (right-click Start > Device Manager).
  2. Expand "Security devices". You'll see "Trusted Platform Module 2.0" there.
  3. Right-click it and select "Uninstall device". Check the box that says "Delete the driver software for this device" if it appears.
  4. Reboot once. Windows will automatically reinstall the driver during startup.

Prevention tip

The most common trigger for this error is apps that use the TPM directly — like some VPN clients, encryption tools, or enterprise management software — and then crash. If you see this error repeatedly, look at Event Viewer under Windows Logs > System. Filter by source "TBS" or "TPM". The event log usually names the process that left the TPM context hanging. Uninstall or update that software.

Also, don't run Clear-Tpm unless you actually have the error. Clearing the TPM resets BitLocker keys, Windows Hello biometrics, and any certificate stores tied to the TPM. It's a sledgehammer — use it only when the error is actually breaking things.

Related Errors in Windows Errors
0XC00D1265 Fix NS_E_BKGDOWNLOAD_CALLFUNCFAILED (0XC00D1265) in Windows Media Player 0X80110485 COM+ app pause/resume error 0X80110485 fix 0X8011045C Fix COMADMIN_E_AMBIGUOUS_APPLICATION_NAME (0x8011045C) 0X000036BA SXS Thread Queries Disabled (0x000036BA) – Fix in Minutes

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.