TPM Error 0x80280402: Duplicate Handle Fix

Quick Fix (30 seconds) — Restart and Retry

This error almost always happens because the TPM chip gets confused after a sleep/wake cycle or a fast startup. The TPM keeps a handle to a previous command that's still open, and your app tries to reuse it. A full restart clears that stale handle.

1. Save your work.
2. Click Start > Power > Restart. Don't use Shutdown — Windows fast startup can keep that state.
3. After reboot, try whatever app or command gave you the error again.

If that fixed it, you're done. If not, move to the next step.

Moderate Fix (5 minutes) — Reset TPM Driver and Service

Restart didn't cut it? The TPM driver or the TPM Base Services might be hung. Let's force a clean restart of the driver stack.

1. Open Device Manager (right-click Start or press Win+X, then pick Device Manager).
2. Expand Security Devices. You should see Trusted Platform Module 2.0.
3. Right-click it and choose Disable device. Confirm the warning.
4. Wait 10 seconds.
5. Right-click it again and choose Enable device.
6. Now open an admin Command Prompt or PowerShell. Press Win+R, type cmd, then Ctrl+Shift+Enter.
7. Run these commands one at a time:
   

   net stop TBS
   net start TBS

8. Close the window and retry your operation.

The TBS service (TPM Base Services) is the middleman between apps and the TPM. Stopping and starting it flushes any stale handles. Most people get the error fixed here.

Advanced Fix (15+ minutes) — Clear the TPM (Last Resort)

If you've done the first two steps and still see 0x80280402, something is corrupt in the TPM's internal state. Clearing the TPM wipes all keys, including BitLocker recovery keys, Windows Hello, and any vTPM keys from Hyper-V. Back up your recovery keys first.

Back up BitLocker keys

• Open Control Panel > BitLocker Drive Encryption.
• Click Back up your recovery key for each drive. Save to a safe place (not the same drive).

Clear TPM via Windows UI

1. Press Win+R, type tpm.msc, hit Enter.
2. Under Actions, click Clear TPM.
3. You'll be prompted to restart. The system will reboot into UEFI and clear the TPM.
4. After reboot, Windows will reinitialize the TPM. You may need to re-set up Windows Hello and re-enable BitLocker.

Clear TPM via PowerShell (if UI is borked)

# Run as admin
Clear-Tpm
Restart-Computer -Force

On reboot, the TPM is fresh. The duplicate handle issue is gone. But you've traded a quick fix for a 15-minute detour. Only do this if the error keeps coming back after steps 1 and 2.

Heads up: If you see this error in a VM (Hyper-V, VMware) using a virtual TPM, the fix is the same — restart the guest, then restart the TPM service inside the guest. Clearing the vTPM in the host settings also works but breaks BitLocker inside the VM.

Why This Happens (the quick version)

The TPM spec says a command handle must be unique per session. Windows or a misbehaving driver sometimes sends a command with a handle that's still in use — the TPM responds with 0x80280402. It's not a hardware failure. It's a software handshake problem. Don't replace the TPM chip unless you've exhausted all three fixes above.