Secure Boot Violation

Fix Secure Boot Integrity Violation in Windows 11

Cybersecurity & Malware Beginner 👁 8 views 📅 Jun 24, 2026

Seeing a Secure Boot error? I'll walk you through fixes from a quick reboot to resetting keys. No fluff, just what works.

30-Second Fix: Reboot and Enter BIOS

This error pops up most often after a Windows update or when you change hardware (like a new SSD). It means your PC thinks the boot files aren't signed right. Don't panic — the fix is usually simple.

Shut down your PC completely. Turn it back on and immediately press the key to enter BIOS. For most brands:

  • Dell: F2
  • HP: ESC or F10
  • Lenovo: F1 or F2
  • ASUS: F2 or DEL
  • Others: try F2, F12, DEL, or ESC (spam them all if you're not sure)

Once inside BIOS, look for a Restore Defaults button — it's often at the bottom or under an Exit tab. Save and exit. This resets Secure Boot settings to factory values. Nine times out of ten, that's all you need.

If your PC boots normally after that, you're done. If not, move to the next step.

5-Minute Fix: Reset Secure Boot Keys Manually

The quick reset didn't work? That means your Secure Boot keys got corrupted or misconfigured. We'll rebuild them.

Enter BIOS again (same key as above). Then:

  1. Find the Security or Boot tab. Look for Secure Boot.
  2. Set Secure Boot to Disabled.
  3. Save and exit. Boot into Windows. It should start normally now, but you'll see a warning about Secure Boot being off. That's fine for now.
  4. Shut down again, go back into BIOS.
  5. Find Restore Factory Keys or Reset to Setup Mode. This option is usually under Secure Boot settings. Select it.
  6. Now Re-enable Secure Boot.
  7. Save and exit.

This clears the old keys and installs fresh ones from Microsoft. Your PC should boot with no errors. This tripped me up the first time too — the option is hidden in different places depending on the motherboard brand. On a Dell Inspiron 2022, it's under "Secure Boot Mode" set to "Custom" then "Reset to Factory Keys." On a Lenovo ThinkPad X1 Gen 10, it's under "Security" > "Secure Boot" > "Reset to Setup Mode."

15+ Minute Fix: Clear TPM and Reset UEFI

Still seeing the error? The problem is deeper — your TPM (Trusted Platform Module) might be holding onto old keys that conflict with Secure Boot. This happens after a motherboard replacement or a failed Windows 11 upgrade.

Before you start: this will clear all BitLocker recovery keys and Windows Hello data. If you use BitLocker, have your recovery key ready from your Microsoft account or a backup.

Here's the process:

  1. Enter BIOS.
  2. Find TPM settings (often under Security or Advanced).
  3. Set TPM to Disabled. Save and exit, then boot into Windows. It won't start — that's expected — but we're just clearing state.
  4. Shut down completely. Power off, unplug the power cord, wait 30 seconds. Plug back in.
  5. Enter BIOS again. Re-enable TPM (set to Enabled or Firmware TPM).
  6. Go to Secure Boot settings. Do the Restore Factory Keys step again.
  7. Make sure Secure Boot is Enabled.
  8. Save and exit.

Your PC should boot. If it asks for a BitLocker recovery key, type the 48-digit code from your account. Once you're in Windows, check that Secure Boot is active: open System Information (m sinfo32), look for Secure Boot State — it should say On.

I've seen this fix work on an HP EliteBook 840 G9 that wouldn't boot after a BIOS update. Took 20 minutes, but the error never came back.

When None of These Work

If you're still stuck, your motherboard might have a hardware fault. Try one more thing: flash the latest BIOS from the manufacturer's website. Use a USB stick and the BIOS flash tool (not from Windows). This replaces the UEFI firmware, which can fix corrupted Secure Boot modules.

If that fails, it's likely a motherboard component failure — time to contact the manufacturer or replace the board.

Quick tip: Always back up your BitLocker recovery key before messing with TPM or Secure Boot. Save it to a safe place (Google Drive or a password manager). You'll thank me later.

Was this solution helpful?