TPM 2.0 3.x.0.x we need an update

[theghost123]

I own an HP Omen 30L desktop (AMD platform). My system’s TPM 2.0 shows a Manufacturer Version of 3.84.0.5. Activision has documented that all AMD TPM firmware versions ending in .0.x fail TPM attestation and cause issues running Call of Duty (Warzone/Black Ops). They state this requires a firmware update from the system manufacturer.

I have already checked for BIOS updates on HP’s website, but none are available for my system. Could you please provide me with a BIOS update (or beta firmware) that includes the corrected AMD TPM firmware (version 3.x.2.x or higher)?

[NonSequitur777]

@theghost123,

Welcome to our HP Community forum!

This is a widespread issue, and the appropriate authorities have been notified -see this recent link: TPM for call of duty - HP Support Community - 9474787.

@Garp_senchau, any news/updates yet?

Kind Regards,

NonSequitur777

[Garp_senchau · Accepted solution]

Hi @theghost123,

Welcome to HP Support Community,

Thank you for posting your query

Thank you for tagging me in this, NonSequitur777. I appreciate you bringing this matter to my attention again. At this time, there are no new updates available regarding the AMD TPM firmware issue. However, I have informed our dedicated team, and they are actively looking into it.

To address your concern:

AMD TPM Firmware Issue: We are aware of the issue with AMD TPM firmware versions causing attestation failures, as noted by Activision. I completely understand how important it is to get this resolved, and we are actively working to address it. Please know that our team is prioritizing this, and we’re committed to providing a solution as soon as possible.

BIOS Updates: I’ve personally checked the available BIOS updates for your Omen 30L desktop (AMD platform), and at this time, there are no new updates on HP’s website that include the required AMD TPM firmware version (3.x.2.x or higher). I recommend keeping an eye on HP’s support page for any new updates, but I understand this might take some time. Please rest assured that once an update is available, it will be posted there.

Next Steps:

Check HP Support for Future Updates: I suggest regularly checking the HP support page for new BIOS or firmware updates. 

Ongoing Investigation: As mentioned, we have informed the dedicated team about the issue, and they are actively investigating it. While I don’t have a specific timeline yet, we are doing everything we can to address this matter quickly.

Additional Troubleshooting: While we await an update, you can try clearing the TPM:

Clear the TPM:

Important: Make sure to back up any data protected by TPM keys before proceeding.

1. Clear the TPM (Proceed with Caution):
   • Important: Before proceeding, back up any data protected by TPM keys, as clearing the TPM can result in data loss. Proceed at your own risk.
   • Open the Run command box by pressing the Windows key + R.
   • Type tpm.msc, and press Enter.
   • In the TPM management console, verify the Manufacturer Version.
   • If clearing the TPM is required, follow on-screen instructions to clear it through Windows.
2. Follow Instructions from HP: Make sure to follow HP's recommended procedures for clearing and updating the TPM. You can find more details on troubleshooting the TMP on Microsoft's Troubleshoot the TPM (it’s strongly recommended to refer to the guide).
3. Reboot and Test: After updating or clearing TPM, restart your system and check the functionality with your games and any applications requiring TPM’s latest version.

Once again, thank you to NonSequitur777 for tagging me. 

We’re taking this matter seriously and are actively working to resolve it. I appreciate your patience, and if you need further assistance or updates, don’t hesitate to reach out.

I hope this helps.

Please feel free to reply here if you have any questions or if you need further clarification on any of the steps. 

Take care and have a good day. 

Did we resolve the issue? If yes, please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!

Regards,

[NonSequitur777]

@Garp_senchau,

Thank you kindly!

आप सबसे अच्छे हैं! / ನೀವು ಅತ್ಯುತ್ತಮರು! / You are the best!

Warm Regards,

NonSequitur777

[Jeroen123]

I have a similar problem. I've been troubleshouting this for a few days now. This is what my problem is and what I did. Comes down to, updating BIOS to F.27 does not fix the problem due to a persistant AGESA-bug. Also my RestartPending stays on True.

I hope it's ok if I repost my findings.

Product: Victus by HP 15L Gaming Desktop PC TG02-0000a (4H508AV)

Hello everyone,
I am experiencing a persistent issue with the TPM 2.0 (fTPM) on my HP Victus 15L Gaming Desktop, resulting in RestartPending: True in PowerShell (Get-Tpm) and an error in Call of Duty: Warzone. The game displays the message: "TPM 2.0 status: not enabled. Module 2.0 requirements. To keep your game and security features up to date, enable TPM 2.0." This occurs despite TPM 2.0 appearing active according to BIOS and Get-Tpm. I am seeking a solution to eliminate RestartPending: True and get Warzone working. I suspect this might be a pre-existing firmware bug.System Specifications:

• Processor: AMD Ryzen 7 5700G with Radeon Graphics
• BIOS Version: F.27 (dated 8-4-2023, recently flashed via USB)
• TPM Status (from Get-Tpm after CMOS reset and PowerShell sync):
  • TpmPresent: True
  • TpmReady: True
  • TpmEnabled: True
  • TpmActivated: True
  • TpmOwned: True
  • RestartPending: True
  • ManufacturerIdTxt: AMD
  • ManufacturerVersion: 3.92.0.5
• Operating System: Windows 11 Home, Build 10.0.26100.6584 (Insider)
• RAM: 16 GB (2x 8 GB Micron 3200 MHz)
• Video Card: NVIDIA GeForce RTX 3060 (Driver 32.0.15.8129, 9-5-2025) + AMD Radeon Graphics (disabled)
• Audio: Realtek, NVIDIA, AMD (virtual devices like SteelSeries Sonar and Voicemod disabled)
• Secure Boot: Enabled (confirmed via msinfo32)

Actions Taken:

1. BIOS update to F.27 via bootable USB (repeatedly).
2. fTPM toggle in BIOS (Enabled/Disabled) with full shutdowns.
3. TPM driver uninstallation via Device Manager ("BIOS driver for Microsoft System Management" and "Trusted Platform Module 2.0") – multiple times.
4. PowerShell commands: Clear-Tpm, Initialize-Tpm.
5. AMD Chipset driver update to 7.06.02.123+.
6. Warzone reinstallation and "Scan and Repair" via Battle.net.
7. CMOS battery removal for BIOS reset.
8. Integrated Radeon Graphics disabled and virtual audio devices disabled.

• PowerShell commands: Disable-/Enable-TpmAutoProvisioning and Initialize-Tpm after CMOS reset.

Results:

• RestartPending: True persists after all steps, including CMOS reset and PowerShell sync.
• Warzone fails to start with the mentioned error upon launching.
• TPM attestation appears to fail, possibly due to an AGESA bug in F.27, as noted in the Call of Duty Season 05 Reloaded blog (September 2025) for AMD fTPM systems.

Question to the Community: Has anyone else with an HP Victus 15L (or similar model) experienced this issue, especially with BIOS F.27 and Ryzen 5000 processors? Are there any working solutions or patches that HP might not have officially released? I am considering contacting HP Support but would like to hear experiences first. All help is welcome!Notes:

• I have spent over 6 hours trying to resolve this and am seeking a direct fix. Thank you!

[john19488]

I have same problem there is no fix. beside getting new mother board

[theghost123]

Any updates on this issue? I have yet to find an acceptable solution. 

[vasthomas]

any updates? my Omen 25L (AMD 5600G) is also affected:

latest f36 bios (august), tmp version: 3.94.0.5

[doorman6]

Same problem here, i did the F.47 Rev.A Bios update and its still 3.90.0.5.

No more Biuos update available, I think I have to buy a new motherboard, but definitely no more HP PC.

[Jeroen123]

When I came first aware of this problem (HP Victus Desktop PC 15L) my BIOS was F25. I did the available BIOS update, released April 2025 to version F27. This did not fix the problem. I recently did the BIOS update, released September 2025 to version F28. The problem is still there. Having missed F26, I still get the impression this a bigger problem.

I have done all your steps and those recommend by Windows, regarding the RestartPending True issue. Many times over.

I do appreciate you have setup a dedicated team to fix this issue.