◆Error Codes Wiki

Secure Boot Violation — Security Boot Fail or Invalid Signature Detected

Criticalboot

Overview

Fix Secure Boot violation errors that prevent Windows from booting, caused by unsigned drivers, modified bootloader, or incorrect BIOS settings.

Key Details

  • Secure Boot verifies that all boot software (bootloader, drivers, OS kernel) is signed with trusted keys
  • A violation means unsigned or improperly signed code was detected during the boot process
  • Secure Boot is required for Windows 11 and is part of the UEFI specification
  • Linux dual-boot setups can trigger Secure Boot violations if the Linux bootloader is not signed
  • Some hardware drivers and firmware updates may temporarily break Secure Boot chain of trust

Common Causes

  • Unsigned or modified bootloader detected (common with Linux dual-boot or custom bootloaders)
  • BIOS/UEFI firmware update changing the Secure Boot keys database
  • Driver or kernel not properly signed after a Windows update
  • MOK (Machine Owner Key) not enrolled for third-party signed bootloaders

Steps

  1. 1If Windows will not boot: enter BIOS/UEFI and temporarily disable Secure Boot to boot normally
  2. 2Check Secure Boot status in Windows: msinfo32 > System Summary > Secure Boot State
  3. 3For Linux dual-boot: enroll the MOK (Machine Owner Key) using mokutil --import key.der
  4. 4Re-enable Secure Boot after fixing the signature issue: BIOS > Security > Secure Boot > Enable
  5. 5If caused by a driver: update or remove the unsigned driver from Safe Mode

Tags

secure-bootuefibootsignaturesecurity

Related Items

windows-tpm-2-0-not-detected-error

More in Boot

windows-error-0xc0000034Windows Boot Error 0xC0000034 — Missing Boot Configuration Data
Critical
windows-error-0xc00000e9Windows Boot Error 0xC00000E9 — Unexpected I/O Error
Critical
windows-error-0xc0000098Windows Boot Error 0xC0000098 — BCD Missing OS Entry
Critical
windows-error-0xc00000e-boot-configWindows Error 0xc00000e — Boot Configuration Data Missing or Corrupted
Critical
windows-error-startup-repair-loopWindows Startup Repair Loop — Automatic Repair Cannot Fix Your PC
Critical
windows-safe-mode-boot-issuesSafe Mode Boot Issues — Windows Cannot Start in Safe Mode Troubleshooting
Critical

Frequently Asked Questions

Temporarily for troubleshooting, yes. Permanently disabling Secure Boot reduces security as any bootloader code can run. Windows 11 requires Secure Boot, and disabling it may trigger activation or update issues. Re-enable it after fixing the issue.