What is SEC-BOOT-VIOLATION?
Violation of Secure Boot rules ranks as a high-severity firmware issue in our database. System boot stopped due to unsigned bootloader or driver. This usually traces back to installing Linux (Grub) or modified Windows and unofficial drivers on. Follow the steps below to fix it.
Common Causes
- Installing Linux (Grub) or modified Windows
- Unofficial drivers on
Step-by-Step Fix Guide
-
1
Turn off Secure Boot in BIOS
Most reports of SEC-BOOT-VIOLATION clear up after Turn off Secure Boot in BIOS, so it's worth trying before anything more involved.
-
2
Erase the Secure Boot keys and restore the factory default DB/DBX settings
Where the fault comes back, look to the later steps — they're built around uncommon sw-bios instability triggers.
Commands & Diagnostics
systeminfo | findstr /C:"Secure Boot"
Frequently Asked Questions
SEC-BOOT-VIOLATION is most often triggered by installing Linux (Grub) or modified Windows. Other reports point to unofficial drivers on as contributing factors.
Try "Turn off Secure Boot in BIOS" first — it resolves most SEC-BOOT-VIOLATION cases on its own. Only work through the rest of the guide above if it comes back.
Rated high severity — SEC-BOOT-VIOLATION isn't immediately destructive, but recurring instances are a sign to fix it sooner rather than later.
In most cases, yes — the guide above resolves SEC-BOOT-VIOLATION without a clean install. Treat a reinstall as the last resort, not the first move.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database