0X80280026

TPM_E_INVALID_POSTINIT (0X80280026) Fix: Wrong TPM Command Sequence

EP
Erropedia Team
📅 July 21, 2026 📅 Updated Aug 1, 2026 👁 9 views Windows Errors Intermediate
Your TPM chip is confused about startup order. The fix is to clear and reinitialize the TPM. Here's how to do it without reinstalling Windows.

Quick Answer

Clear the TPM through UEFI/BIOS or use tpm.msc in Windows and select "Clear TPM". Reboot twice. That's usually it.

Why This Happens

The TPM (Trusted Platform Module) is a microcontroller that stores keys, passwords, and certificates. When you see code 0X80280026, it means some application or process sent a command to the TPM before it finished its startup sequence. The TPM only accepts certain commands in a strict order: first TPM_Init, then TPM_Startup, then everything else. If something jumps the gun — like your antivirus, BitLocker checking early, or a wonky driver — the TPM gets confused and throws this error.

I've seen this happen most often after a Windows update (especially the 22H2 or 24H2 patches) or after a sudden power loss. Laptops with firmware TPM (fTPM) on AMD systems are prone to this — the Ryzen 3000/5000 series had a known bug with this exact behavior. Intel PTT (Platform Trust Technology) systems also get it sometimes, but less frequently.

The culprit here is almost always a stale TPM state. The chip remembers the last incomplete session and refuses to start fresh. Clearing it wipes that memory.

Fix Steps

Step 1: Clear TPM in Windows (the easy way)

  1. Press Win + R, type tpm.msc, hit Enter.
  2. In the TPM Management window, look at the right pane. Click "Clear TPM".
  3. You'll see a warning about BitLocker keys. If you use BitLocker, you need your recovery key. Write it down or have it ready.
  4. Click "Restart and clear TPM now". Your PC will reboot.

Step 2: Complete the reboot cycle

When it restarts, you'll see a blue screen asking you to press a key (usually F12) to confirm the TPM clear. Do it. The system will reboot again. After that second boot, Windows should reinitialize the TPM automatically. Check if the error is gone by going back to tpm.msc — it should say "The TPM is ready for use".

Step 3: Command line alternative (if GUI fails)

If tpm.msc doesn't open or the clear button is grayed out, open Command Prompt as Administrator and run:

tpmtool clear

This does the same thing but bypasses GUI issues. Follow the same reboot confirmation process.

Alternative Fixes If the Main One Fails

Clear TPM from UEFI/BIOS

If Windows itself can't clear the TPM (maybe because the OS won't boot), you'll need to do it from firmware. Reboot and mash the key for your BIOS — F2 on Dell/Lenovo, Del on ASUS/MSI, F10 on HP. Look for a setting called "TPM State" or "Security Chip". Set it to "Disabled" or "Clear". Save and exit. Then go back in and re-enable it. This forces a full hardware reset.

For AMD fTPM systems, the option is often under "AMD CBS" → "Firmware TPM". Disable it, save, boot, then re-enable it.

Reset TPM via Registry Hack (rarely needed)

Sometimes the TPM driver gets stuck. Delete the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TPM\State

Back it up first. Then delete it. Reboot. The TPM service will recreate it fresh. This is a last resort — I've only needed this on Windows 10 1909 builds.

Prevention Tip

Set your system to not clear TPM on boot. In tpm.msc, go to "Action" → "Prepare the TPM". This turns off the automatic reset that some BIOS versions do after a crash. Also, avoid shutting down your PC by holding the power button — that's a common trigger for this error. Always use Start → Shut down.

If you're on an AMD Ryzen system with fTPM, check your motherboard manufacturer's site for a BIOS update. ASUS released a fix for this in BIOS version 4602 and later for B450/X470 boards. Gigabyte had a similar patch for F40+ BIOS. These updates stop the fTPM from losing its mind after a cold boot.

Related Errors in Windows Errors
0XC01E000B STATUS_GRAPHICS_PRESENT_REDIRECTION_DISABLED (0xC01E000B) Fix 0XC00D0FEB Fix NS_E_WMPOCX_UNABLE_TO_LOAD_SKIN (0XC00D0FEB) in Windows 0X00000523 0x00000523 Invalid Account Name Fix That Works 0XC01E0320 STATUS_GRAPHICS_STALE_MODESET (0xC01E0320) Fix: Stale Mode Set Error
TPM_E_INVALID_POSTINIT 0X80280026 TPM error TPM init sequence clear TPM TPM startup fix Windows TPM error BitLocker TPM error TPM chip problem TPM reset TPM 2.0 error TPM command sequence TPM initialization error Windows security chip error TPM firmware fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.