• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Join the HP Community Solve‑a‑thon | Help Others & Share Your Solutions | Live on Zoom | 2:30 PM to 2:30 AM IST | Every Wednesday Click here to know more
HP Recommended
Microsoft Windows 11

to keep a long story short, I have an OMEN 40L GT21, product 8949. I updated the BIOS from F.20 to F.38 because of a TPM attestation failure. BIOS shows TPM Device Available and TPM State On, but Windows says no compatible TPM can be found. Device Manager shows Trusted Platform Module 2.0 as greyed out with Code 45, and PowerShell Get-Tpm reports TpmPresent say False. The HP BIOS utility also prompts for Local Admin OTP. I need help because this has become frustrating after recently having to repair the same pc that I'm speaking about.

1 REPLY 1
HP Recommended

@Just_Luck98,

 

Welcome to our HP Community forum!

 

Since your OMEN 40L GT21 (HanaA motherboard (SSID: 8949) shows TPM Device Available and TPM State On in BIOS, the TPM hardware itself appears to be detected by the firmware. However, Windows is clearly not seeing it, as evidenced by the Code 45 error in Device Manager and Get-Tpm returning TpmPresent : False.

 

Before trying anything more invasive, I would suggest checking the following:

 

  1. In Device Manager, select View > Show hidden devices, right-click the greyed-out Trusted Platform Module 2.0, choose Uninstall device, then reboot. Windows should attempt to enumerate the TPM again.
  2. Open tpm.msc and confirm whether Windows still reports that no compatible TPM can be found.
  3. If BitLocker is not enabled (or you have your recovery key safely backed up), enter BIOS and perform a Clear TPM operation, then allow Windows to rediscover and reprovision it after reboot.
  4. Load BIOS defaults (or at least verify TPM/PTT/fTPM settings remain enabled), save changes, and reboot.

 

Regarding the Local Admin OTP prompt in the HP BIOS Configuration Utility: that is typically associated with HP enterprise BIOS management features and is unrelated to the TPM detection issue itself. Unless you intentionally configured BIOS administration through HP's enterprise tools, I would not focus on that at this stage.

 

One additional observation: your HanaA (SSID: 8949) platform is not currently listed in HP's published advisory covering systems affected by the recent TPM attestation issue. That may simply mean HP has not yet released an updated BIOS specifically for this platform. If this TPM

detection problem began immediately after updating from F.20 to F.38, it would be worthwhile to report that detail to HP, as it may help identify whether another BIOS revision is needed for the HanaA platform.

 

Could you also post:

 

  • The complete output of msinfo32 for the BIOS Version/Date and BIOS Mode fields.
  • A screenshot of the BIOS Security > TPM page.
  • Whether Device Security in Windows Security reports a Security processor or says none is available.
  • The "System SKU" as displayed in System Information.

 

Btw, HP recently published a Knowledge Base article covering TPM attestation issues affecting certain OMEN and Victus gaming systems. Although your symptoms are somewhat different (Windows is not detecting the TPM at all), it is still worth reviewing because it covers HP's current recommendations regarding BIOS updates, TPM reset/clear procedures, and BitLocker/PIN considerations:

 

Troubleshooting TPM Attestation Errors on your gaming device.

 

Since your BIOS already detects the TPM but Windows does not (Get-Tpm reports TpmPresent : False and Device Manager shows Code 45), I would first focus on restoring Windows' ability to enumerate the TPM before troubleshooting attestation itself.

 

Kind Regards,

 

NonSequitur777


† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.
-->