Secure Boot violation after changing BIOS settings, what should I check?

November 8, 2026 4 answers
Asked by K__9Baffle

I changed Secure Boot from “Other OS” to “Standard” on an ASUS dual-boot PC with Windows and Arch Linux, and now I get a Secure Boot Violation. The Secure Boot and key-management options are locked, even after trying a few BIOS changes. What should I check before changing anything else?

Answers

R__2Muffle

Changing to Standard can enable Secure Boot keys that reject a bootloader not signed by a key the firmware trusts. That can affect the Linux boot path even if Windows is fine. If you can reach firmware setup, look for the board’s documented option to restore or manage Secure Boot keys, but don’t clear or replace keys without understanding what it will do to both operating systems.

Reply to this answer
81__Turbine

A CMOS reset is one possible recovery step when firmware settings seem stuck, but check your motherboard manual for the exact procedure first. It can reset other BIOS settings too, so note anything you rely on, such as boot order, storage mode, or memory settings. Afterward, check whether Secure Boot controls are available before saving more changes.

K__9Baffle:

If I reset CMOS, should I update the BIOS right away?

F6.Plotter:

First see whether the reset restores access and whether the system boots. Only consider a BIOS update if there’s a relevant reason, and use the board’s official instructions with stable power. Don’t treat it as a guaranteed fix for a Secure Boot key or bootloader mismatch.

Reply to this answer
7M!Dromedary

Before changing more firmware settings, check whether the Windows boot entry still works from the one-time boot menu. If it does, that helps narrow this to the Linux boot path rather than a general failure to start. If neither system boots, the exact motherboard model and the wording of the firmware screen would help identify the next safe step.

Reply to this answer
2b__Skillet

Be cautious about guides that recommend clearing keys or switching between key modes without explaining the consequences. Secure Boot configuration is separate from ordinary crash troubleshooting, and a Windows minidump usually won’t explain a firmware rejection that happens before Windows starts. First establish which boot entry is being rejected and what firmware options are actually available.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions