Many users have complained about the same. Fortunately, we can fix the issue with a few changes in System BIOS in no time. This guide will discuss all the steps to fix the error right after talking about the probable causes.
What causes the TPM 2.0 device detected but a connection cannot be established error?
There are several reasons for the error to occur; some of the popular ones are :
TPM algorithm – If the TPM2 algorithm selection for the ESXi host’s BIOS is not set to use the SHA256 hashing algorithm, you might get this error. Intel(R) TXT disabled – You may get this TPM error if the Intel(R) TXT is disabled. To resolve this, you need to enable it. Secure BOOT disabled – If Secure BOOT is not enabled, you might get this message in vCenter. To fix this, you need to enable Secure BOOT.
What can I do if TPM 2.0 device is detected but a connection cannot be established?
Below are the requirements that your vCenter Server environment should meet to use TPM 2.0 chip:
vCenter Server 6.7 ESXi 6.7 host: TPM 2.0 chip installed and configured. Make sure UEFI is selected.
So, these are the steps you need to follow to fix the TPM 2.0 device detected but a connection cannot be established error. If you have other issues, like the TPM device not being detected, you need to check your BIOS settings. If you have any other questions or concerns about TPM or TPM malfunctioning, feel free to mention them in the comments below.
SPONSORED
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
