0X80290215

Fix TBSIMP_E_NOTHING_TO_UNLOAD (0x80290215) in Windows

Windows Errors Intermediate 👁 0 views 📅 May 26, 2026

This error pops up when Windows Update tries to unload resources that are already cleared. Here's what triggers it and how to fix it fast.

You're running Windows Update, or maybe a manual cleanup, and you get hit with 0x80290215 — TBSIMP_E_NOTHING_TO_UNLOAD. This usually happens when the Trusted Platform Module (TPM) base services (TBS) are trying to unload resources that are already cleared. I saw this last month on a Dell laptop running Windows 10 22H2 right after a failed cumulative update. The user had disabled TPM in BIOS, then re-enabled it, and updates went sideways.

Root Cause

The TBS service manages TPM commands. When it tries to free up resources — like after an update or a TPM reset — it checks what's loaded. If nothing's there to unload (because it's already been cleared by another process or a driver), it throws this error. It's not harmful, but it can block updates or make cleanup tools fail. The real trigger is usually a mismatch between the TPM state and what Windows expects — often after a BIOS change, a driver update, or a corrupted update cache.

Fix Steps

Step 1: Clear the Windows Update Cache

This is the first thing to try. The update cache can get stuck and confuse TBS. Here's how:

  1. Open Command Prompt as Administrator.
  2. Run these commands one at a time:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Restart your PC and try the update or cleanup again. This fixed it for my client in about 5 minutes.

Step 2: Run DISM and SFC

If the cache clear doesn't work, corruption in system files might be messing with TBS. Run these:

  1. Open Command Prompt as Administrator.
  2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This takes 10-15 minutes. Don't interrupt it.
  3. Then run sfc /scannow. Let it complete.
  4. Reboot.

Step 3: Reset the TPM

If the error persists, the TPM state might be out of sync. You can reset it from Windows, but check your BIOS first — some systems need that.

  1. Go to Settings > Update & Security > Windows Security > Device security.
  2. Click Security processor details, then Security processor troubleshooting.
  3. Select Clear TPM. This will reset it to factory defaults. You'll need to re-enable BitLocker or PIN if you use them.
Warning: Clearing TPM removes all keys. Make sure you have backup keys stored elsewhere, like a Microsoft account or USB drive.

Step 4: Check BIOS TPM Settings

I've seen this error on machines where TPM is disabled in BIOS but Windows still expects it. Reboot into BIOS (usually F2 or Del at startup), look for Security > TPM or Intel PTT or AMD fTPM, and make sure it's enabled. Save and exit. Then boot into Windows and try the update again.

If It Still Fails

If none of this works, check for driver conflicts. Open Device Manager, look for System devices, and find Trusted Platform Module 2.0. Right-click it, uninstall it, then scan for hardware changes to reinstall it. Also check Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > TBS-Operation for more clues. If you're still stuck, run the Windows Update Troubleshooter from Settings — it's basic but sometimes catches a sneaky issue.

Was this solution helpful?