Fix TBSIMP_E_INVALID_CONTEXT_HANDLE (0x80290202) in Windows

1. Most common cause: TBS driver got stale after sleep or driver update

This error shows up when Windows can't talk to the TPM because the internal pointer (the context handle) is dead. Think of it like a phone number that used to work but now it's disconnected. This happens most often after your PC wakes from sleep, or after you install a BIOS or chipset driver update.

Fix number one is simple: reset the TPM Base Services (TBS) driver. You don't need to reboot first.

Step-by-step: Reset TBS driver

1. Press Windows + R, type services.msc, hit Enter. A window of service names opens.
2. Scroll down to TPM Base Services. Right-click it, pick Stop. After you click Stop, the Status column should go blank.
3. Wait 10 seconds. Then right-click it again and pick Start. Now the Status column should say Running.
4. Close the services window. Try whatever app gave you the error again. That's it.

If that doesn't work, you might need to force the driver to reload. Do this:

1. Open Command Prompt as admin. Press Windows + X, pick Terminal (Admin) or Command Prompt (Admin).
2. Type net stop tbs and press Enter. You should see "The TPM Base Services service is stopping..." then "stopped."
3. Wait 5 seconds. Type net start tbs and press Enter. You should see "The TPM Base Services service started successfully."

This fix works about 70% of the time. If the error comes back every day, move to cause #2.

2. Second cause: Corrupted TPM driver or chipset driver

Windows Update sometimes pushes a TPM driver that's the wrong version for your hardware. Or the chipset driver might be older than the TPM firmware. This is common on Dell and HP business laptops from 2020-2023.

What to do: Update the TPM driver manually

1. Press Windows + X, pick Device Manager.
2. Click View at the top, then check Show hidden devices.
3. Expand Security devices. You should see something like Trusted Platform Module 2.0. Right-click it, pick Update driver.
4. Pick Browse my computer for drivers.
5. Pick Let me pick from a list of available drivers on my computer.
6. If there's more than one driver listed, pick the oldest one (usually the Microsoft generic driver). Then click Next. After you install it, Windows will say it's updated.
7. Restart your computer. After it comes back up, check if the error is gone.

If that didn't work, go back and pick the newest driver. On some Lenovo ThinkPads, the newest driver from Intel or AMD fixes this completely. On HP EliteBooks, the Microsoft generic driver is more stable. You have to test both.

3. Third cause: TPM ownership got scrambled (needs a clear)

This is the nuclear option. If you've done everything above and still get the error, the TPM's internal memory is probably corrupted. Clearing the TPM wipes all keys, including BitLocker keys. If you use BitLocker, pause here. You must have your recovery key ready, or disable BitLocker first. Otherwise you'll lock yourself out of your own data.

How to clear TPM from Windows

1. Open Windows Security. Click the shield icon in the system tray, or search for Windows Security from Start.
2. Click Device security on the left.
3. Under Security processor, click Security processor details.
4. Click Security processor troubleshooting.
5. Click Clear TPM. You'll see a warning. Read it. If you're sure, click Clear and restart.
6. The computer will restart automatically. It might take a minute or two. During restart, the BIOS might ask you to confirm the TPM reset. Press F1 or Enter (the key varies by manufacturer).

If that fails: Clear TPM from BIOS

Some manufacturers hide the Windows clear option. Do this instead:

1. Restart your computer. While it's booting up, mash F2 (Dell), F10 (HP), F1 (Lenovo), or Del (custom builds) to enter BIOS setup.
2. Look for Security or Trusted Computing tab.
3. Find Clear TPM or Reset TPM. It's often under TPM State or TPM Operations.
4. Select it, confirm the prompt. The computer may restart once or twice during this process.
5. After it boots back to Windows, open Device Manager and verify the TPM shows up as Trusted Platform Module 2.0 without any yellow warning icons.

After clearing the TPM, you'll need to re-enable BitLocker if you use it. And any apps that rely on TPM (Windows Hello, virtual smart cards, some VPN clients) will need to be set up again. That's the trade-off.

Quick-reference summary

Start with cause #1. It fixes most people. If you're still seeing the error after #3, your TPM chip might be physically failing. That's rare on modern hardware, but happens. Run wmic tpm get status in Command Prompt. If it says "The TPM is ready for use" but you still get the error, consider replacing the motherboard.