Lenovo Carbon X1 Gen 13 TPM attestation issues

Anonymous
2025-03-05T17:40:27+00:00

Hi everyone,

I'm experiencing an issue with TPM attestation on my Lenovo X1 Carbon Gen 13 when trying to enroll the device into Windows Autopilot. The error I get is: Attestation timeout error

Observations:

  • In Windows Security > Device Security, the TPM attestation status is stuck on "Loading...", whereas on another working device (different model), it correctly shows "Ready".
  • I have two brand new X1 Carbon Gen 13s, both delivered this week, and both are experiencing the same attestation error.

TPM Status (tpmtool getdeviceinformation):

  • Ready For Attestation: False
  • Is Capable For Attestation: False
  • TPM Manufacturer: ST Microelectronics (STM)
  • TPM Spec Version: 1.59
  • BitLocker PCR7 Binding State: Binding Not Possible

What I’ve Tried So Far:

  • Updated to the latest BIOS from Lenovo's support site.
  • Cleared and reset TPM in both Windows (Clear-Tpm) and BIOS.
  • Switched from Discrete TPM 2.0 to Firmware TPM (if available, but couldn't find an option).
  • Disabled Microsoft Pluton Processor Control and Intel TXT Feature in BIOS.
  • Ensured Secure Boot is enabled.
  • Restarted the Device Health Attestation Service.
  • Checked network connectivity to Microsoft attestation servers (attestation.microsoft.com).

Still Facing These Issues:

  • TPM remains "Ready for Attestation: False".
  • Windows Security > Device Security still shows TPM attestation as "Loading...".
  • Autopilot enrollment fails with an attestation timeout.

Has anyone else experienced this issue with Lenovo X1 Carbon Gen 13 and STM TPMs? Could this be a firmware issue? Is there an official Lenovo fix or a BIOS setting I might have missed? I can't find the TPM upgrade utility for the Gen 13, so I am unable to upgrade the TPM firmware.

Would appreciate any advice - thanks in advance!

Windows for home | Windows 11 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

29 answers

Sort by: Most helpful
  1. Anonymous
    2025-04-19T07:37:02+00:00

    Hi.. well the 3078 looks good... but its weird that outputting the ek, got you 2 for the price of 1. It should give you only 1 ... can you show the output of the Get-TpmEndorsementKeyInfo.. if you want you could also contact me directly by teams... as i really want to get to the bottom of this.. as having 2 ek certs now is weird... Did you also used the clear-tpm command in windows?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-04-17T16:37:27+00:00

    Here is the screenshot.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-04-17T05:01:03+00:00

    He at that certificate if you click on details it should show the RSA public key.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-04-16T23:44:40+00:00

    Good to know Rudy thank you for your suggestion and reply. :)

    I followed the steps above in the order on my Gen 13 same errors as before.

    Here are 2 event viewer logs not sure if they help and I think included the RSA info you requested?

    If this is not the info how could I get the RSA info?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-04-16T07:11:10+00:00

    Normally it only needs to have 1EK cert... and you dont need to install them manually in the certstore... :) but i am wondering how they look like.. do you can share the properties (rsa key from them ?)

    The certenroll task looks good..

    Install Windows

    From the OOBE (shift f10) go to windows updates and install the April build

    Restart Windows

    Clear-TPM and reboot the device

    Open and run the PowerShell attestation tool (or run the tpm-maintenance task)

    Check if the EKCert is on the device Get-TpmEndorsementKeyInfo

    From there on you should be able to pre-pro the device with autopilot again

    Was this answer helpful?

    0 comments No comments