-
×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
- Desktops
- Desktop Operating Systems and Recovery
- Secure Boot Violation/OS Not Found

Create an account on the HP Community to personalize your profile and ask a question
08-13-2019 07:37 PM
My desktop is an Omen 870-130VX. Immediately following a recent Windows Update, on boot my PC encountered a red warning message stating that there was a “Secure Boot Violation: Invalid signature detected. Check Secure Booty Policy in Setup”. After pressing any key to continue a blue warning screen states that “Boot Device Not Found: Please install an operating system on your hard disk.” I’ve already tried quite a few solutions, none of which have worked, including: disabling secure boot, enabling legacy boot sources , running System Recovery, running recovery from a USB, running recovery from CDs, as well as changing the battery on the motherboard.
08-13-2019 08:03 PM - edited 08-13-2019 08:18 PM
Greetings,
Welcome to the forum.
I am not a HP employee.
Wow, this is a new one for me!
Is this a failed W10 update to version 1903?
A Secure boot violation should refer to: invalid device firmware (the device key does not correspond to the Secure boot database stored in the PC's UEFI BIOS) or a non supported operating system is attempting to run at system startup. Secure boot enforces digital signatures so unauthorized code cannot run at system boot.
Disabling Secure boot and enabling Legacy support should fix this boot problem. Did you enter the confirmation code at system restart to confirm the change?
It sounds like a failing or corrupted storage device.
Have you run HP Diagnostics (Link) to check hardware?
Tap "ESC' at boot.
Select "F2".
Run fast and extensive system tests. Run component tests.
Again, this is a first time event for me.
Try resetting the BIOS or clearing CMOS.
Regards