0X80280003

Fix TPM_E_BAD_PARAMETER 0x80280003 in Windows 10/11

EP
Erropedia Team
📅 August 13, 2026 📅 Updated Sep 11, 2026 👁 19 views Windows Errors Intermediate
TPM error 0x80280003 appears when Windows can't talk to your TPM chip correctly. Most often it's a driver or BIOS glitch. Here's how to clear it fast.

Quick answer for advanced users

Run tpm.msc, check if TPM is ready. If not, clear TPM from BIOS (or Windows Security), update the TPM driver from Device Manager, and if that fails, reset the BIOS to defaults.

Why this error shows up

Windows throws TPM_E_BAD_PARAMETER (0X80280003) when a command sent to the TPM chip gets rejected because one of the parameters is garbage. It's not a hardware failure – the TPM is fine. What's broken is the software handshake between Windows and the chip.

I've seen this most often after a Windows feature update (like going from 21H2 to 22H2), or when a BIOS update changes the TMP state without telling Windows. Sometimes it's just a corrupted driver entry in Device Manager.

The good news? You can usually fix it without reinstalling Windows. Here's how, in order from least disruptive to most.

Fix 1: Check and re-initialize TPM from Windows Security

  1. Press Win + I to open Settings.
  2. Go to Privacy & Security (Windows 11) or Update & Security (Windows 10).
  3. Click Windows Security > Device security.
  4. Under Security processor, click Security processor details.
  5. Look for Status – if it says “Ready” but you still get errors, click Security processor troubleshooting and then Clear TPM.

What you'll see: A warning that clearing TPM will reset BitLocker keys and Windows Hello. If you use BitLocker, make sure you have the recovery key saved. After clearing, Windows will restart and re-initialize the TPM. Then check tpm.msc – it should say “The TPM is ready for use.”

If you don't have the Clear TPM option (some systems hide it), skip to Fix 2.

Fix 2: Update or reinstall the TPM driver

A stale driver is a common culprit. Here's how to force Windows to redo it.

  1. Press Win + X and click Device Manager.
  2. Expand Security devices.
  3. Right-click Trusted Platform Module 2.0 (or the name it shows) and select Update driver.
  4. Click Search automatically for drivers. If Windows finds nothing, click Search for updated drivers on Windows Update as a backup.
  5. If that doesn't help, right-click the TPM device and choose Uninstall device. Don't check “Delete the driver software for this device” – you want Windows to reinstall it automatically.
  6. Restart your PC.

Expected outcome: On reboot, Windows reinstalls the driver. Open tpm.msc and see if the status changed from “Not ready” to “Ready.”

Fix 3: Clear TPM from BIOS

If Windows can't even see the TPM, the BIOS is the next stop. This resets the TPM at the hardware level.

  1. Restart your PC and press the key to enter BIOS (usually Del, F2, or Esc – watch the splash screen).
  2. Look for a Security tab or Trusted Computing section. It might be under Advanced on some boards.
  3. Find the TPM setting (often called TPM Device, Intel PTT, or AMD fTPM).
  4. Disable it, save and exit, then go back into BIOS and re-enable it. Some systems have a Clear TPM option right there – use that if you see it.
  5. Save changes and boot to Windows.

What to expect: The first boot after this might trigger a TPM initialization screen. That's fine. Open tpm.msc and check the status. If it still says “Not ready,” go to Fix 4.

Fix 4: Reset BIOS to defaults

Sometimes the TPM setting gets stuck in a weird state that a simple toggle won't fix. Resetting the whole BIOS clears all that.

  1. Enter BIOS as in Fix 3.
  2. Look for Load Defaults, Reset to Default, or Exit menu > Load Optimized Defaults.
  3. Confirm and exit.

After this: Your boot order, overclocking, and any custom fan curves get wiped. You'll need to re-enable XMP for your RAM, but it's a small price to get TPM working.

Once back in Windows, check tpm.msc. If it still shows the error, you're looking at a motherboard firmware update – check your manufacturer's site (Dell, HP, Lenovo, ASUS, etc.) for the latest BIOS.

Alternative: Use PowerShell to re-register the TPM

If BIOS resets didn't help, there's a PowerShell trick that forces Windows to renegotiate with the TPM.

  1. Right-click the Start button and select Terminal (Admin) or Windows PowerShell (Admin).
  2. Run this command:
Get-Tpm | Initialize-Tpm -AllowClear -Force

What this does: It tells Windows to clear the TPM and set it up fresh. You'll get a prompt to reboot.

After reboot, run tpm.msc again. This usually does the trick when nothing else does.

Prevention: Avoid this mess next time

The most common trigger for 0x80280003 is a driver update or a BIOS update that changes TPM state. So don't update your BIOS unless you have a specific reason – if you do, always update the TPM driver immediately after.

Also, before installing a big Windows feature update, check that your TPM is set to Firmware mode (in BIOS) if you're on a modern Intel or AMD system. That's the default on most machines, but some older ones use a discrete TPM chip which has more compatibility headaches.

Keep a note of your BitLocker recovery key somewhere safe – not inside the encrypted drive. You'll thank yourself later.

If none of these fixes work, test the TPM itself with the hardware diagnostic tool from your PC maker (Dell SupportAssist, HP PC Hardware Diagnostics, etc.). A failing TPM chip is rare, but it happens.
Related Errors in Windows Errors
0XC00D1B7D Fix NS_E_NOSTATSAVAILABLE (0XC00D1B7D) on Windows 0XC0000299 STATUS_SHARED_POLICY 0XC0000299 Fix: Shared Policy Object 0X00002B07 WSA_QOS_GENERIC_ERROR 0X00002B07: Fix in 3 Steps 0XC00D1236 Fix NS_E_PDA_FAILED_TO_SYNCHRONIZE_FILE (0XC00D1236) in Windows Media Player
TPM_E_BAD_PARAMETER 0x80280003 TPM error fix TPM not working Windows 11 clear TPM TPM driver update BIOS TPM setting Windows Security TPM error TPM initialization failed tpm.msc error 0x80280003

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.