TBS_E_BAD_PARAMETER 0X80284002: Fix in 5 Minutes Flat

The 30-Second Fix: Restart the TBS Service

This error almost always means the TPM Base Services (TBS) service has cached bad data. I've seen it after a botched BitLocker unlock or a third-party security tool interfering. Here's how you kill it fast.

1. Press Win + R, type services.msc, hit Enter.
2. Scroll to TPM Base Services. Double-click it.
3. Click Stop, then Start. Wait 5 seconds.
4. Close the window. Try your TPM-dependent app again.

Had a client last month whose entire print queue died because of this—restarting TBS fixed it instantly. If that didn't work, move to the next step.

The 5-Minute Fix: Clear TPM Ownership (Without Losing Data)

If restarting TBS didn't cut it, the TPM has corrupted ownership data. Clearing it resets everything, but you won't lose BitLocker keys if they're saved to your Microsoft account. On a domain-joined machine, check with IT first—some orgs lock this down.

1. Open Windows Security app. Go to Device security > Security processor details > Clear TPM.
2. Click Clear. Your PC might reboot once or twice.
3. After reboot, TPM initializes fresh. The error should vanish.

Alternate: Run tpm.msc from Run dialog, then click Clear TPM in the actions pane. Same result.

One gotcha: if BitLocker is active, you'll need your recovery key. I keep mine on a USB stick for exactly this reason.

The 15+ Minute Advanced Fix: Driver Rollback or Update

If clearing TPM didn't work, it's likely a driver issue. I see this mostly on Lenovo ThinkPads after a BIOS update. The TPM driver version mismatches Windows' expectations.

1. Press Win + X, select Device Manager.
2. Expand Security devices. Right-click Trusted Platform Module 2.0 and choose Properties.
3. Go to the Driver tab. Click Roll Back Driver if available. If not, click Update Driver > Browse my computer > Let me pick.
4. Choose an older driver from the list (usually a Microsoft-provided one).

Still no luck? Check the System Event Log for more details. Open Event Viewer, go to Windows Logs > System, filter by Source: TBS. Look for event ID 0 or error descriptions. I've seen corrupted registry entries in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TBS cause this—export the key, then delete it and restart the service. But that's rare.

If you're stuck, a full Windows reset or BIOS reflash is the nuclear option. I've only needed that twice in ten years.

Pro tip: never disable TBS in services. Windows depends on it for secure boot and BitLocker. Disabling it will brick half your security features.

That's it. Start with the service restart, then clear TPM, then driver fix. You'll be done in under 5 minutes.