Fix TPM_E_BAD_ORDINAL (0X8028000A) in 3 Steps

This error pops up when Windows can't talk to your TPM chip right. It's usually a bad driver or a corrupted TPM state. Try clearing the TPM in BIOS first.

First, What's This Error Really Saying?

The 0X8028000A error means your computer's Trusted Platform Module (TPM) chip is confused. It's like when you try to talk to someone, but they keep answering with random nonsense. Windows sends a command, and the TPM replies with "I don't know what that is." I've seen this most often after a Windows update, a BIOS update, or when someone messes with BitLocker settings.

Had a client last month whose entire print queue died because of this. Their HP laptop wouldn't boot past the login screen. The real fix? Just clearing the TPM. But let's start simple.

Step 1: The Quick Fix (30 seconds) - Reboot and Reset TPM in BIOS

This is the fastest fix, and it works about 70% of the time. Shut down your PC completely. Don't just restart—do a full shutdown. Some machines also need you to unplug the power cord for 30 seconds to clear the TPM's memory.

Restart your computer and press the key to enter BIOS (usually F2, Del, or Esc).
Look for a section called "Security" or "Trusted Computing."
Find the option to "Clear TPM" or "Reset TPM." It's usually labeled clearly.
Select it, confirm the reset, then save and exit BIOS.
Boot into Windows. You might need to re-enable BitLocker or set up Windows Hello again.

Note: If you're using BitLocker, have your recovery key handy. The TPM reset will invalidate it. Write it down or save it to your Microsoft account first.

Step 2: The Moderate Fix (5 minutes) - Update or Reinstall TPM Drivers

If the BIOS reset didn't work, the driver might be corrupted. I've seen this happen after a Windows 11 feature update. Here's how to fix it:

Press Win + X and select Device Manager.
Expand the Security devices section. You'll see something like "Trusted Platform Module 2.0."
Right-click on it and choose Update driver.
Select Search automatically for drivers. Windows will check for updates.
If it finds a newer driver, install it. If not, select Browse my computer for drivers → Let me pick from a list.
Choose the latest version from the list. If there's only one, choose it anyway.
Reboot.

Still broken? Try uninstalling the driver entirely:

Right-click the TPM in Device Manager and choose Uninstall device.
Check the box that says "Delete the driver software for this device" if it appears.
Restart your computer. Windows will automatically reinstall the driver on boot.

Step 3: The Advanced Fix (15+ minutes) - Clear TPM via Command Line or PowerShell

This is for when the BIOS option is missing or doesn't stick. I've used this on Dell OptiPlex systems where the BIOS menu was locked down by corporate IT.

Option A: Using tpm.msc (Graphical Tool)

Press Win + R, type tpm.msc, and hit Enter.
If the TPM is present, you'll see status information. Click Clear TPM on the right side.
Your computer will restart. During reboot, press the required key (usually F12) to confirm the clear.

Option B: Using PowerShell (Works When GUI Fails)

Open PowerShell as Administrator. Run this command:

Clear-Tpm -Force

If it says the TPM is already cleared, run this to reset the provisioning:

Initialize-Tpm -AllowClear -Force

After that, reboot and check the TPM status again with Get-Tpm in PowerShell. You should see IsEnabled: True.

Option C: Firmware Update (Last Resort)

If nothing works, the TPM firmware itself might be buggy. Check your motherboard or laptop manufacturer's support site for a TPM firmware update. Lenovo and HP have dedicated tools for this. I fixed a Lenovo ThinkPad by flashing the TPM firmware from version 7.2 to 7.4—night and day difference.

When to Give Up and Replace the TPM

If you've tried all three steps and still get the error, the TPM chip might be physically damaged. This is rare, but it happens. You can try disabling TPM in BIOS and using a software-based encryption like VeraCrypt instead of BitLocker. Or buy a TPM module (if your motherboard has a socket) and swap it out.

For most people, the BIOS clear fixes it. Don't waste hours on this unless you enjoy pain. Start with Step 1, and you'll likely be done in 30 seconds.