Secure boot violation

[Cesar70]

I have an HP Omen 30L GT13-0024. After updating to BIOS F.32, Secure Boot no longer works. With Secure Boot enabled, the system displays “Secure Boot Violation – Invalid signature detected.” With Secure Boot disabled, Windows boots normally. TPM is enabled, Platform Key is enrolled, DISM and SFC pass, and Call of Duty fails attestation because Secure Boot cannot be enabled.

[Deep_World]

Hi  @Cesar70,
 
Welcome to the HP Support Community!

Thanks for reaching out!

I understand how  it must feel to run into a Secure Boot violation after updating your BIOS. Thank you for sharing the details you’ve already tried

Could you confirm:

• Whether Windows was installed in UEFI mode (not Legacy).
• If you’ve made any custom changes to boot entries or keys beyond the default HP settings.

Here are a few  steps you can try:

1. Clear and re‑enroll Secure Boot keys: In BIOS, look for the option to restore factory default keys under Secure Boot. This often resolves signature mismatches after updates.
2. Check Boot Mode: Ensure the system is set to UEFI only, with Legacy disabled.
3. Windows Boot Manager priority: Confirm that Windows Boot Manager is the first boot option in BIOS.
4. HP Support Assistant: Run diagnostics to ensure firmware and drivers are aligned with the new BIOS.

I hope this helps. 

[sagarp0301]

I know this is going to sound crazy but follow these instructions posted by ASUS and it will be fixed. I have spent around 4 hours figuring this stuff out and this link saved me. 

Edited