• ×
    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
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended

Subject: HP OMEN - fTPM / Attestation Handshake Failure After F22 BIOS Update

Message:

Hi HP Support Team,

I am experiencing a critical hardware-level security validation issue on my HP OMEN laptop right after upgrading to the latest F22 BIOS version.

The system fails to complete the hardware device attestation handshake on secure remote servers (specifically affecting the Ricochet Anti-Cheat system, resulting in a persistent "Failed Attestation Status" error). However, on the local OS level, all features seem intact.

Here are the technical details of the issue:

  1. The Trigger: Everything was working flawlessly until the exact moment I updated the BIOS to the F22 version.

  2. The Symptom: The F22 firmware seems to have a bug in its fTPM (Firmware TPM) signing/endorsement algorithm. It provides corrupted or unrecognized attestation certificates during remote security handshakes.

  3. Local Diagnostics: Inside Windows, Core Isolation (Memory Integrity) and Kernel-mode Stack Protection are fully enabled and functional. Running the local CODSecureAttestationWizard returns a successful result, proving the hardware is physically active, but the remote servers cannot decrypt the token produced by this specific F22 BIOS firmware.

  4. Troubleshooting Done: I have already cleared the TPM keys via tpm.msc, rebuilt the BitLocker key protectors via PowerShell (manage-bde), and performed a hardware "Clear TPM" directly inside the OMEN Setup Utility. The issue strictly persists, confirming it is a firmware-level bug.

Since the modern OMEN Setup Utility strictly prevents rolling back to a previous BIOS version via standard local or USB recovery methods due to security policies, I am stuck with this bugged F22 firmware.

Could you please pass this report to your engineering/firmware team? We urgently need either a hotfix/patch BIOS version to fix the fTPM attestation loop, or a official method to safely downgrade the BIOS to the previous stable version.

i already tried evereything in here 

TPM Attestation Failure on OMEN Max 16 for Call of Duty - HP Support Community - 9608222

Thank you for your assistance.

Best regards,

† 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>.