0X80280039

Fix TPM_E_REQUIRES_SIGN (0x80280039) on Windows 10/11

EP
Erropedia Team
📅 July 28, 2026 📅 Updated Aug 1, 2026 👁 5 views Windows Errors Intermediate
This error means your TPM chip needs a signed command. Usually happens with BitLocker or Windows Hello after driver updates. Clear TPM keys or update firmware.

This error is a pain. Let's kill it fast.

I've seen this on Dell, HP, and Lenovo machines running Windows 10 and 11. The culprit is almost always a corrupted TPM driver update or a system sleep cycle that desynced the chip. Don't bother reinstalling Windows — that rarely helps.

The Quick Fix: Clear TPM in BIOS/UEFI

This works 9 out of 10 times. Your TPM got confused and needs a hard reset.

  1. Restart your PC and smash F2 (or Del, F10, F12 — depends on brand) to enter BIOS/UEFI.
  2. Look for a section called "Security" or "Trusted Computing."
  3. Find the option to "Clear TPM" or "Reset TPM." On Dell it's under "TPM 2.0 Security" → "Clear." On HP it's "TPM State" → "Reset."
  4. Select it, confirm the warning, and save and exit (usually F10).
  5. Boot into Windows. You'll see a message saying TPM initialized. That's good.

Now try whatever was failing — BitLocker unlock, Windows Hello setup, whatever. Should work now.

Why This Works

Your TPM chip stores keys and signed commands internally. When a driver update or power event messes with that storage, the chip rejects unsigned commands — even legitimate ones. Clearing the TPM wipes that corrupted storage and lets the chip rebuild its state. Think of it like resetting a locked safe. You lose the old keys inside, but everything starts fresh.

One thing: clearing TPM will break BitLocker if you don't have the recovery key handy. So back that up first. I've seen people lock themselves out of their drives. Don't be that person.

If That Didn't Work: Update TPM Firmware

Sometimes the TPM firmware itself is buggy. I fixed this on a Dell OptiPlex 7080 that kept throwing 0x80280039 after every sleep cycle. A firmware update killed it dead.

  1. Go to your PC manufacturer's support site.
  2. Search for "TPM firmware" for your exact model. For Dell, it's in "Drivers & Downloads" → "Security." For HP, it's "Firmware – TPM."
  3. Download the latest firmware installer. Run it as administrator.
  4. Restart. The firmware flashes during boot — don't power off.
  5. Boot into Windows. Check TPM status with tpm.msc — it should show "The TPM is ready for use."

Skip generic firmware updaters — use only the manufacturer's tool. Lenovo's TPM updater, for example, is model-specific.

Less Common Fixes That Work

Reinstall TPM drivers

Sometimes the driver, not the hardware, is the problem.

  1. Open Device Manager (right-click Start).
  2. Expand "Security devices." You'll see "Trusted Platform Module 2.0."
  3. Right-click it → "Uninstall device." Check "Delete the driver software for this device" if offered.
  4. Restart. Windows reinstalls the driver automatically.

Disable and re-enable TPM in BIOS

Some BIOS versions toggle the TPM state incorrectly after updates.

  1. Enter BIOS, find TPM settings.
  2. Set it to "Disabled." Save and exit.
  3. Boot into Windows once (you'll get a TPM error — that's fine).
  4. Reboot, re-enable TPM in BIOS.

This forces a fresh handshake between the OS and chip.

Run Microsoft's TPM troubleshooter

Only if you're desperate. It's rarely the fix, but costs nothing.

Download Microsoft TPM Troubleshooter, run it, follow prompts. I've seen it fix one case out of thirty — but that one case was a pain, so I'm including it.

Prevention: Keep TPM Firmware and Drivers Updated

This error loves to come back if you ignore updates. Set a reminder to check for TPM firmware updates every 6 months. Most manufacturers release them silently — you won't see them in Windows Update.

Also, don't let your laptop fully drain the battery with TPM-dependent features running. I've seen corrupt TPM states from sudden power loss during sleep. If you use BitLocker or Windows Hello, shut down properly, don't just slam the lid.

And for the love of all that's holy, back up your recovery keys. Write them down, store them in a password manager, print them and hide them. The day you need them is the day you forgot.

That's it. Clear TPM, update firmware, reinstall drivers. You're welcome.

Related Errors in Windows Errors
0XC0000502 STATUS_THREAD_ALREADY_IN_TASK (0XC0000502) – Thread Already Joining Task 0X4026243A Fix 0X4026243A: Graphics Adapter Deferred Start 0X00000002 0X00000002: File Not Found – What Actually Triggers It 0X00001B64 Modem Response Timeout 0x1B64: Fix in 2 Minutes
TPM_E_REQUIRES_SIGN 0x80280039 TPM error signed command error TPM chip BitLocker TPM error Windows Hello TPM TPM firmware update clear TPM keys TPM driver fix TPM 2.0 error Dell TPM error HP TPM error Lenovo TPM error

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.