TPM Security Data Change Detected after BIOS F.27 update

[crustypatties]

My HP OMEN 16-c0012dx (AMD Ryzen 7 5800H) started displaying “TPM Security Data Change Detected” on every normal startup after updating to BIOS F.27.

Pressing F2 allows Windows to boot, but the warning returns every time.

Troubleshooting already completed:

* BIOS shows TPM Device: Available and TPM State: On.
* Windows tpm.msc reports “Compatible TPM cannot be found.”
* Device Manager shows AMD PSP 10.0 Device working properly, but no TPM 2.0 device.
* A power reset did not resolve the issue.
* HP Support Assistant reports no available updates.
* HP’s driver page lists F.27 as the latest BIOS.

My C: drive is BitLocker-encrypted, and I have saved my recovery key.

What is the safest HP-supported way to restore TPM functionality and eliminate this startup warning? Should the BIOS be repaired, or is a TPM reset necessary?

[Deep_World]

Hi  @crustypatties 
 
Welcome to the HP Support Community!

Thanks for reaching out!

I understand your concern , don’t worry let me check and help you with this.

Since the TPM warning started immediately after BIOS F.27 and Windows cannot detect the TPM, kindly avoid clearing the TPM at this stage, especially because your C: drive is protected by BitLocker.
 

Meanwhile, kindly try these steps and confirm :  

1. Save the BitLocker recovery key securely outside the laptop and back up important files.
2. Install all Windows and optional driver or firmware updates.
3. Open Manage BitLocker and select Suspend protection for drive C:.
4. Restart the laptop, press F10, load the BIOS default settings, and save the changes.
5. Re-enter BIOS and confirm that TPM/AMD fTPM and Secure Boot are enabled.
6. Start Windows and check tpm.msc again.
7. If the TPM is still unavailable, contact HP Support for a guided BIOS recovery or BIOS reinstallation before considering a TPM clear.

The BitLocker recovery key may be required when BIOS updates affect TPM data: HP BitLocker and recovery-key information- Click here  for info.   

This issue means that the BIOS recognizes the firmware TPM, but Windows is currently unable to access or initialize it. For that reason, checking or repairing the BIOS configuration is the safer first approach. Clearing the TPM should only be considered later with the BitLocker key and data backup ready.

You can also review this HP Community discussion where customers reported a similar TPM-related behavior after a BIOS update and the troubleshooting steps that helped resolve the issue:

• HP Community - TPM Security Data Change Detected Issue and Sign-In Not Working

I hope this helps.