What is SECURE-BOOT-VIOLATION?
Violation of Secure Boot is a high-severity hardware BIOS/UEFI issue. Secure Boot blocked unsigned boot code from running. This usually traces back to old bootloader and corrupted EFI. Use the steps below to track down and fix the cause.
Common Causes
- Unsigned Linux
- Old bootloader
- Corrupted EFI
Step-by-Step Fix Guide
-
1
Turn off Secure Boot in BIOS
Turn off Secure Boot in BIOS tends to be the quickest win here, addressing the most typical cause of SECURE-BOOT-VIOLATION.
-
2
Register the IOC key
Repeat occurrences typically trace back to less obvious bios instability factors, addressed in the steps ahead.
-
3
Reinstall the OS with SB support
"Reinstall the OS with SB support" covers a less common but documented cause of SECURE-BOOT-VIOLATION.
Commands & Diagnostics
No specific commands required for this error. Follow the step-by-step guide above.
Frequently Asked Questions
Unsigned Linux accounts for the majority of SECURE-BOOT-VIOLATION reports; old bootloader and corrupted EFI come up less often but are documented.
"Turn off Secure Boot in BIOS" clears up most SECURE-BOOT-VIOLATION reports by itself. The remaining steps above cover what's left.
SECURE-BOOT-VIOLATION is a high-severity error. It won't damage your PC instantly, but repeated occurrences usually point to a deeper problem worth addressing soon.
Usually. SECURE-BOOT-VIOLATION is fixable with the steps above; a full Windows reinstall is rarely necessary unless everything else has failed.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database