F5F Stay Refreshed Hardware Desktop Your TPM device is detected, yet it isn't functioning properly.

Your TPM device is detected, yet it isn't functioning properly.

Your TPM device is detected, yet it isn't functioning properly.

L
LLLLLAMA
Junior Member
48
03-13-2021, 12:16 AM
#1
I purchased this laptop from a nearby hardware shop. It no longer comes with any warranty. Over the years, after several OS installations, I observed that my TPM 2.0 began to malfunction. The model is an HP Gaming Pavilion 15-ec2010 with the OS named Microsoft Windows 11 Pro Version 10.0.22000 Build 22000. Other details about the system aren't available. The manufacturer is Microsoft Corporation, and the system is a desktop PC running x64-based architecture. It has the SKU 4F6X5EA#AB9. The processor is an AMD Ryzen 5 5600H with Radeon graphics, 3301 MHz, 6 cores, and 12 logical processors. The BIOS version is AMI F.27 from April 8, 2024, with SMBIOS 3.3, BIOS mode UEFI, and Secure Boot enabled. The hardware abstraction layer version is 10.0.22000.1696. There are 16 GB of RAM installed, with 15.3 GB free, plus 18.3 GB of virtual memory, totaling 4.93 GB available. The system supports virtualization-based security, but certain features like Hyper-V won't appear due to limited BIOS support.

I've attempted to update the BIOS, changed it manually via the HP website, and disabled/re-enabled TPM. I've also reset the keys and ensured Secure Boot remains active. Despite these efforts, the TPM isn't recognized, and Windows 11 installation still fails to detect it.
L
LLLLLAMA
03-13-2021, 12:16 AM #1

I purchased this laptop from a nearby hardware shop. It no longer comes with any warranty. Over the years, after several OS installations, I observed that my TPM 2.0 began to malfunction. The model is an HP Gaming Pavilion 15-ec2010 with the OS named Microsoft Windows 11 Pro Version 10.0.22000 Build 22000. Other details about the system aren't available. The manufacturer is Microsoft Corporation, and the system is a desktop PC running x64-based architecture. It has the SKU 4F6X5EA#AB9. The processor is an AMD Ryzen 5 5600H with Radeon graphics, 3301 MHz, 6 cores, and 12 logical processors. The BIOS version is AMI F.27 from April 8, 2024, with SMBIOS 3.3, BIOS mode UEFI, and Secure Boot enabled. The hardware abstraction layer version is 10.0.22000.1696. There are 16 GB of RAM installed, with 15.3 GB free, plus 18.3 GB of virtual memory, totaling 4.93 GB available. The system supports virtualization-based security, but certain features like Hyper-V won't appear due to limited BIOS support.

I've attempted to update the BIOS, changed it manually via the HP website, and disabled/re-enabled TPM. I've also reset the keys and ensured Secure Boot remains active. Despite these efforts, the TPM isn't recognized, and Windows 11 installation still fails to detect it.

O
owen22s
Member
70
03-13-2021, 01:09 AM
#2
Verify BIOS configuration for legacy boot mode (CSM) settings
O
owen22s
03-13-2021, 01:09 AM #2

Verify BIOS configuration for legacy boot mode (CSM) settings

P
73
03-14-2021, 05:02 AM
#3
It seems the gadget doesn’t support Windows 11, but there’s a tutorial available on how to use Rufus to work around this issue.
P
PinkUniGamer15
03-14-2021, 05:02 AM #3

It seems the gadget doesn’t support Windows 11, but there’s a tutorial available on how to use Rufus to work around this issue.

N
Nadroj9999
Member
91
03-14-2021, 10:29 AM
#4
This feature isn't available in the BIOS, it seems very restricted. I remember they had TPM2.0 before, and I used this laptop for Vanguard games.
N
Nadroj9999
03-14-2021, 10:29 AM #4

This feature isn't available in the BIOS, it seems very restricted. I remember they had TPM2.0 before, and I used this laptop for Vanguard games.

K
Kimbaj123
Member
181
03-14-2021, 02:25 PM
#5
It seems your firmware includes a TPM, but this feature isn't compatible with Windows 11. It could have functioned on Windows 10. The issue might stem from a recent firmware update.
K
Kimbaj123
03-14-2021, 02:25 PM #5

It seems your firmware includes a TPM, but this feature isn't compatible with Windows 11. It could have functioned on Windows 10. The issue might stem from a recent firmware update.