0X80280802

TPM_E_DOING_SELFTEST (0x80280802) Fix – TPM Stuck in Self-Test

Windows Errors Beginner 👁 10 views 📅 May 26, 2026

Your TPM is running its own health check and won't respond until it's done. Usually finishes in 30-90 seconds. If it's stuck, the fix is straightforward.

Quick Answer

Wait 90 seconds. If the error persists, clear the TPM from Windows Security (Device Security > Security Processor Details > Clear TPM) or run tpm.msc and restart. Skipping the wait causes unnecessary reboots.

Why This Happens

Your TPM chip is running a full self-test – something it does after a cold boot, firmware update, or system crash. The test usually takes 30 to 90 seconds. During that window, any app trying to talk to the TPM (BitLocker, Windows Hello, VBS) gets slapped with 0x80280802. It's not a bug. It's the TPM saying “busy, call back later.” The culprit here is almost always clicking “Repair” or “Retry” too fast. Windows expects you to wait, but users don't.

Sometimes the TPM genuinely gets stuck. This happens most often on Dell and HP systems that shipped with TPM 2.0 enabled but the firmware didn't fully reset after a BIOS update. Older Lenovo ThinkPads with TPM 1.2 also have this quirk. If you're on Windows 11 22H2 or later, you'll see this error in Event Viewer under System log, source TPM, event ID 15 or 22.

Fix Steps (Numbered)

  1. Wait 90 seconds. Seriously. Don't reboot. Don't mash F2. Go get coffee. Then try your operation again.
  2. If still broken, clear the TPM via Windows: Go to Settings > Privacy & Security > Windows Security > Device Security. Click Security Processor Details. Then Security Processor Troubleshooting. Hit Clear TPM. You'll need to restart – the system will reinitialize the TPM fresh.
  3. Alternative: Use tpm.msc. Press Win + R, type tpm.msc, hit Enter. In the Actions pane, click Prepare the TPM or Clear TPM (if available). Restart after.
  4. If tpm.msc says “Compatible TPM cannot be found,” check BIOS. Reboot, enter BIOS (F2/Del), look for Security > TPM. Make sure it's enabled and set to Firmware TPM (or PTT on Intel, fTPM on AMD). Save and exit. Then boot to Windows and retry.
  5. Last resort – BIOS reset. In BIOS, load factory defaults (usually F9). Reboot. TPM will go through a full self-test cycle again, but this time it should finish cleanly.

Alternative Fixes (If Main Steps Fail)

  • Restart the TPM service: Open PowerShell as admin and run restart-service tpm. This only works on Windows 11 if the service is stuck – it's rare, but worth a shot.
  • Disable and re-enable TPM in BIOS: Go back to BIOS, set TPM to Disabled, save, boot to Windows, shut down, enable TPM again. This forces a full reinitialization. You'll lose any TPM-bound keys (BitLocker recovery key required).
  • Run the TPM diagnostics tool: Microsoft's tpmdiag.exe (part of Windows ADK) can force a reset. Not installed by default – download from MS if you're desperate.
Warning: Clearing the TPM wipes all keys. If you use BitLocker, have your recovery key handy – it's in your Microsoft account or printed when you set it up. Without it, you're locked out of the drive.

Prevention Tip

The easiest fix is to never rush Windows after a reboot or BIOS update. Give the TPM 2 minutes before launching any security apps. Also keep BIOS/UEFI firmware updated – manufacturers (Lenovo, Dell, HP) regularly patch TPM self-test bugs. Set a reminder to check for BIOS updates every 6 months. That'll cut this error by 90%.

Was this solution helpful?

TPM_E_DOING_SELFTEST 0x80280802 TPM self-test stuck TPM not responding TPM error Windows 11 TPM error Windows 10 clear TPM reset TPM TPM self-test timeout BitLocker TPM error TPM 2.0 self-test TPM initialization failure