The Trusted Platform Module (TPM) hardware failed to execute a TPM command. (code: 0x80284001)

  • Windows 11 24H2
  • Framework Laptop 13 AMD 7840U
  • BIOS 3.05

For a while now I am having issues with the TPM module. These manifest themselves in the following way:

  • When I try to use a stored Passkey (e.g. for a website), an undefined error will occur, Windows’ Passkey popup won’t come up at all.
  • When I try to log into Windows via Pin it will not work: “Something went wrong and your PIN isn’t available (code: 0x80284001)” (though face recognition via Windows Hello still works for some reason).
  • When I try to unlock my KeePass database via the stored biometric data an error will occur.

Within the Windows Event Viewer under System there will alwys be the following message:

The Trusted Platform Module (TPM) hardware failed to execute a TPM command.

Unfortunately that is all that it says. When I try to execute Get-Tpm in an elevated PowerShell, it will only output

Get-Tpm : An internal error has occurred within the Trusted Platform Module support program. (Exception from HRESULT: 0x80284001)
At line:1 char:1
+ Get-Tpm
+ ~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-Tpm], TpmWmiException
    + FullyQualifiedErrorId : Microsoft.Tpm.Commands.TpmWmiException,Microsoft.Tpm.Commands.GetTpmCommand

plus the aforementioned message will be visible in the Event Viewer.

When I try to access the TPM Management (tpm.msc) it will say “Cannot load management console”

Loading of the managmenet console failed. An internal error has occurred within the Trusted Platform Module support program. (Exception from HRESULT: 0x80284001) Try again.

Originally I thought this only happens after the Laptop was in Standby for some time, but today it happened right after a fresh boot after being shut down completely.

Google search results for the 0x80284001 TPM error are a bit inconclusive. To me it seems like it’s more of a hardware or BIOS issue, but I am at a loss currently what I could try.

Btw. I do use Bitlocker and can boot normally otherwise.

1 Like

Hi @fritzmg,

You might start a ticket with support to have them help you identify the issue with the TPM.

Let us know how it turns out.

I contacted Framework support and one of the troubleshooting steps they instructed was to reset the BIOS to its defaults. Curiously that has, at least so far, fixed the problem - even though the only things I ever changed in the BIOS was the power button brightness and battery max charge.

Though of course I’ll still have to observe whether this issue re-occurs over a longer period of time.

1 Like

It happened again and once again a BIOS reset fixed the issue. Though this time Framework support also suggested to update the BIOS to 3.07 (which was recently released at the time).

Hi @fritzmg!

Interesting that it occurred again months later. Same issue too. I suspect something is physically wrong with the TPM and after X cycles or uses it manages to corrupt access to itself.

The updated BIOS probably has something to do with the commands being send and read from it at the EC level to help better understand what is going on. This seems like a rare defect in just this particular TPM. Something about the BIOS reset gives it a clean path to communicate again with the TPM along with reading and sending key information to the module.

Thanks for the update!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.