Fix TBS_E_INVALID_CONTEXT_PARAM 0x80284007 in Windows

Quick answer

Run tpm.msc to check TPM status, then restart the TBS service (net stop TBS && net start TBS as admin). If that fails, clear TPM from BIOS or tpm.msc, then re-enable it.

What this error means

You're getting 0x80284007 — that's a TBS (TPM Base Services) error. The exact message is “One or more context parameters are invalid.” I've seen this most often on Windows 10 21H2 and Windows 11 22H2 after a BIOS update, or when someone replaces a motherboard without a clean TPM reset. The culprit here is almost always a stale TPM state or a driver that’s hung onto an old context handle.

When an application (BitLocker, Windows Hello, or a VPN client) tries to talk to the TPM, it passes a context structure. If the TBS layer doesn't recognize the context — maybe because the TPM was reset, or the driver got swapped — it throws 0x80284007. The fix isn't complicated, but you need to rule out a few things first.

Fix steps (try in order)

1. Restart the TBS service

1. Open Command Prompt as Administrator.
2. Run:

   net stop TBS && net start TBS

3. This flushes the TBS context pool. If the error was caused by a hung handle, this fixes it immediately.

2. Check TPM status in tpm.msc

1. Press Win + R, type tpm.msc, hit Enter.
2. Look at the status: it should say “The TPM is ready for use”.
3. If it says “Compatible TPM cannot be found”, go into your BIOS and verify TPM is enabled (often under Security or Trusted Computing).
4. If TPM is disabled, enable it, save and exit, then boot into Windows and check again.

3. Clear the TPM (safest way)

Warning: Clearing TPM wipes BitLocker keys, Windows Hello PIN, and any other TPM-bound credentials. Back up your BitLocker recovery key before doing this.

1. Open tpm.msc as admin.
2. Click Clear TPM in the Actions pane.
3. Follow the wizard — you'll be prompted to restart. After reboot, Windows re-initializes the TPM automatically.
4. Check the status again: it should say “Ready”.

4. Reinstall the TPM driver

1. Open Device Manager.
2. Expand Security devices.
3. Right-click Trusted Platform Module 2.0 and select Uninstall device.
4. Check “Attempt to remove the driver for this device”.
5. Restart your PC. Windows will reinstall the driver automatically.

Alternative fixes if the main ones fail

Reset the TPM via PowerShell

Get-WmiObject -Namespace "root/cimv2/security/microsofttpm" -Class Win32_Tpm | ForEach-Object { $_.SetPhysicalPresenceRequest(12) }

This triggers a TPM clear on next reboot. Same warning about keys applies.

Check for BIOS updates

I've seen this error on Lenovo ThinkPads and Dell OptiPlex after a BIOS update that changed TPM settings. Go to your manufacturer's support page and install the latest BIOS. Then reset TPM in BIOS and boot back into Windows.

Run SFC and DISM

Corrupted system files can break the TBS service. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. Rarely the fix, but worth a shot if nothing else works.

Prevention tip

If you're upgrading your motherboard or CPU, always disable BitLocker and clear the TPM before swapping hardware. Windows can handle the initial TPM context after a clean boot, but a stale context from the old hardware will trigger 0x80284007 every time. Also, avoid running TPM-dependent apps with admin rights if you don't need them — it cuts down on context mismatches.

One last thing: if you're on a corporate-managed machine, don't clear TPM without checking with your IT team first. They'll want to re-enroll your BitLocker keys after the reset.