Firmware · high

How to fixSEC-BOOT-VIOLATION

Violation of Secure Boot rules

What this error means

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.

Before you begin

Save open work and back up important files. Note any recent driver or hardware changes. If Windows cannot start, use the startup guide first.

Work through these checks

0 of 2 complete
01Turn off Secure Boot in BIOS

Turn off Secure Boot in BIOS.

Use the instructions for your exact device and operating system. Check the manufacturer’s documentation before changing firmware, hardware, or system settings.

I need help
02Erase the Secure Boot keys and restore the factory default DB/DBX settings

Erase the Secure Boot keys and restore the factory default DB/DBX settings.

Use the instructions for your exact device and operating system. Check the manufacturer’s documentation before changing firmware, hardware, or system settings.

I need help

Possible causes

  • Installing Linux (Grub) or modified Windows
  • Unofficial drivers on