secure boot violation

Question

i am in INSIDER PROGRAM and I AM SURE IT HAPPENED DUE TO WINDOWS CRASHED LOW QUALITY UPDATE. GET ME OUT OF THIS TESTING AND STOP RUINING MY LIFE.
after windows update i got on 10tha april 2026. i cannot launch windows . and have to manually bypasss secure boot top disabled,
due to this some apps are not running which i need.
i tried lot of steps including resetting bios, bios update, runnig various troubleshooting comands from gemini. still its not working. i have checked hardware tests are good.

Moved from <Windows for home | Windows 10 | Performance and system failures>

Answer 1

Hi Nik-7539,

I understand how frustrating it is to face a Secure Boot violation issue, especially after you’ve tried everything possible. Once Windows boots only with Secure Boot disabled, it means the current Windows boot files are no longer trusted by the firmware.

At this stage, Windows commands, BIOS resets, or leaving the Windows Insider Program cannot repair a broken Secure Boot installation. The Q&A Assist has provided some suggestions, but if they don't work, here's what you should do now:

1. Boot into Windows with Secure Boot disabled.
2. Back up all your personal files and data immediately.
3. Disconnect from the internet to prevent further updates.
4. Create standard Windows installation on bootable media (USB).
5. Boot from that USB and select Custom install option
6. Delete the existing partitions and perform a fresh installation.
7. After it completes, enter BIOS/UEFI and re‑enable Secure Boot.
8. Load the factory/default Secure Boot keys.
9. Boot back into Windows and verify that applications run normally.

Disclaimer: At this point, we have exhausted all troubleshooting and I recommend that we try to perform a clean install to get your computer back into a working condition. Please ensure that you backup any important data, including Documents, Pictures, Videos, and more. After that, you can find instructions on how to perform a clean install by navigating to the bottom of this guide: Reinstall Windows with the installation media - Microsoft Support 

Continuing to run Windows with Secure Boot disabled will cause ongoing issues with apps and security features. This is why Microsoft generally recommends a clean installation of a public (non‑Insider) build when Secure Boot violations persist after updates.

I know this isn’t the answer anyone hopes for, but once all other troubleshooting steps have failed, a clean reinstall is the most realistic and reliable fix.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

To recover from the Secure Boot Violation and stop having to disable Secure Boot, follow these steps in order.

1. Boot by temporarily disabling Secure Boot
   • Enter the firmware/BIOS menu while the device starts (keys like F1, F2, F12, or Esc, depending on the device).
   • Locate the Secure Boot setting (usually under Security, Boot, or Authentication) and set it to Disabled.
   • Save changes and restart so Windows can boot.
2. Install the fixed/re-released update The Secure Boot Violation after an update is a known issue on some devices when firmware cannot handle newer bootloader signatures. The documented workaround is:
   • With Secure Boot disabled, boot into Windows.
   • Install the re-release (fixed version) of the problematic update from Windows Update (or as provided by Microsoft for that issue).
   • After the updated boot loader is installed, restart Windows normally.
3. Re-enable Secure Boot correctly Once Windows is booting normally with the updated boot loader:
4. Uninstall any graphics cards, hardware, or operating systems that are not compatible with Secure Boot, if present.
5. Open the PC BIOS/UEFI menu:
   • Either press F1/F2/F12/Esc during startup, or
   • From Windows, hold Shift while selecting Restart, then go to Troubleshoot > Advanced Options > UEFI Firmware Settings.
6. Find Secure Boot and set it to Enabled.
   • If there is a Custom option, load the factory Secure Boot keys that are built into the PC.
   • If Secure Boot cannot be enabled, reset BIOS/UEFI to factory defaults and try again.
7. Save changes and exit so the PC reboots.
8. If the PC fails to boot after enabling Secure Boot, go back into BIOS, disable Secure Boot again, and boot Windows. In that case, contact the device manufacturer for firmware assistance.
9. If the device will not start at all after certificates/updates For devices that fail to start after Secure Boot–related certificate updates:
10. Disable Secure Boot through the firmware/BIOS menu (same steps as above) so the device can start.
11. After booting, follow Microsoft’s guidance for Secure Boot revocation/certificate updates and ensure all required updates are installed.
12. Re-enable Secure Boot as described above.
13. Insider Program and future stability The context provided focuses on fixing Secure Boot and boot issues. For Insider builds that cause boot failures, the supported path is to:

• Recover the device (as above) so it can boot.
• Then follow Microsoft’s standard guidance (outside this context) to move off Insider builds to a stable channel.

If, after these steps, Secure Boot still cannot be enabled without a violation error, the documented next step is to work with the device manufacturer, as firmware limitations or bugs can prevent Secure Boot from accepting updated bootloader signatures.

---

References:

• Disabling Secure Boot
• Re-enable Secure Boot
• TPM lockout occurs unexpectedly in Windows 8.1 or Windows RT 8.1
• Windows devices for home users, businesses, and schools with Microsoft-managed updates
• How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932
• Bug Check 0x145: SECURE_BOOT_VIOLATION
• Secure boot state is still off tried alot of things - Microsoft Q&A
• Can't enable secure boot - Microsoft Q&A