HP OMEN 30L – BIOS F.21 Update Causing TPM 2.0 and Secure Boot Issues

[JCollins23]

I am experiencing a serious BIOS/TPM issue with my HP OMEN 30L desktop after updating the BIOS. I need help restoring TPM 2.0 functionality and Secure Boot so I can play Call of Duty.

PC Information:

• Model: HP OMEN 30L Desktop GT13 series

• Product number: 328N9AA#ABA

• Motherboard product: 8876

• Processor: AMD Ryzen 7 5800X

• Graphics card: NVIDIA GeForce RTX 3080 (10 GB)

• Current BIOS: F.21 (updated from an older version)

• TPM firmware: AMD 3.92.0.5

• Operating system: Windows 11 64-bit

The Problem:

After updating my BIOS to F.24, I started experiencing problems with TPM 2.0 and Secure Boot, which were previously on and working fine. In Windows Device Manager, the TPM-related device reports Code 45: “Currently, this hardware device is not connected to the computer.” Windows is not detecting the TPM correctly. 

I also ran the Get-Tpm command in PowerShell to check the TPM status. The TPM checks were reporting failures, indicating that Windows was not detecting or recognizing the TPM properly.

However, when I enter the BIOS settings, the TPM device shows as Available, and the TPM State is set to On.

Im sure i can figure out the secure boot but how can I get my system to recognize the tmp

[Bill_To]

Greetings @JCollins23 

You are the second individual in this Forum having a TPM problem after updating the BIOS to F.24.

BIOS version F.24 is supposed to fix the TPM version problem.

Try updating your AM4 B550 MB's chipset drivers at this AMD Site if you have not done this. This might resolve the TPM problem.

But BIOS version F.24 has a known Secure Boot problem.

The following two options are available to attempt to fix the Secure Boot problem:

1. Periodically check your PC's download site for a future BIOS update. Or use this HP Site to check for future BIOS updates.

Or you can wait for HP Support Assistant to push a future BIOS update. Windows Update might also push a newer BIOS version.

2. Try the Secure Boot workaround solution in this HP Forum Thread.

Option 1 would be the safest approach.

Some Forum members are not having a good experience using option 2.

Regards