topic Query: VMware sucks: TPM 2.0 device detected but a connection could not be established in ProLiant Servers (ML,DL,SL)

VMware : TPM 2.0 device detected but a connection could not be established

localhorst — Tue, 06 May 2025 01:17:11 GMT

Hello. I am using a HPE Proliant DL360 Gen10 with TPM 2.0 module. During bootup all is ok with TPM. In ILO it tells me Present and enabled.. Module Type: 2.0.
So far so good.

But the ESXi UI gets me this error. "TPM 2.0 device detected but a connection could not be established"

I have UEFI Only, Secure Boot. I don't understand FIFO vs. CRM setting. Intel TXT also enabled.

Does anybody using VMware in such a configuration and got TPM running?

Re: VMware : TPM 2.0 device detected but a connection could not be established

SydUmar_1 — Fri, 02 May 2025 08:08:02 GMT

Hello @localhorst
Please set the TPM setting in BIOS for Current TPM 2.0 Active PCR's to SHA256 only and check if that addresses the issue.

Query: VMware sucks: TPM 2.0 device detected but a connection could not be established

support_s — Tue, 06 May 2025 05:35:23 GMT

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".