-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Gaming
- Gaming Desktops
- Secure boot violation when enabling secure boot

Create an account on the HP Community to personalize your profile and ask a question
09-07-2026 04:39 PM
OMEN 25L GT12-0xxx, System Board ID 8704, BIOS F.29. Secure Boot keys are enrolled (PK/KEK/DB/DBX are present), Windows is UEFI with the Microsoft bootloader, but enabling Secure Boot produces “Secure Boot Violation.”
09-08-2026 10:32 AM - edited 09-08-2026 11:09 AM
Greetings @Glockx
I'm scratching my head when I see this problem in the Forum.
Disabling Secure Boot/enabling Legacy support may be the only workaround. This is not advisable but it may be the only choice you have.
UEFI Secure Boot violations normally happen if unsigned or blacklisted code (drivers, bootloaders, or other Ring 0 and lower code) attempts to run during the POST process.
Now, the PC's UEFI may be detecting malware during the POST process. Or you need to update drivers. I don't know.
But I'm also wondering if this error is related to a UEFI firmware/Windows Secure Boot 2023 certificate mismatch??
Your PC is using the latest available BIOS version. BIOS version F.29 may be the last BIOS update your PC will receive.
HP GT12-0xxxa AMD PCs are now classified as Legacy PCs; no BIOS updates.
But your PC sports an Intel H470 MB. So I don't know what's happening??
HP may have designated H470 MB PCs as Legacy hardware (no more BIOS updates). However, I haven't seen any documentation to confirm this.
Regards