Fix Secure Boot "Verification failed: (0x1A) Security Violation" with sbctl
I verified every sbctl subcommand and flag against sbctl(8): create-keys, enroll-keys with -m/--microsoft, sign with -s/--save, verify, list-files, list-enrolled-keys, status all exist as written, and sbctl is in extra (0.18). Two fixes needed. The Limine signing path is wrong: the limine package ships usr/share/limine/BOOTX64.EFI and there is no limine.efi, so sbctl sign -s /boot/EFI/limine/limine.efi fails on a nonexistent file. And the record omits sbctl's own prominent warning: some devices ship signed firmware/option ROMs that are validated under Secure Boot, and enrolling keys without Microsoft's certificates can brick them. That warning belongs next to the enroll command, not nowhere.
BRICKING RISK. sbctl enroll-keys without -m (Microsoft keys) can leave some laptops unable to run signed option ROMs (discrete GPU, Thunderbolt) or unable to boot Windows. A small number of firmwares handle custom PK enrollment badly. Always use -m on a dual-boot or OEM laptop, keep Secure Boot disabled until sbctl verify is clean, and know how to reset keys to factory defaults in your firmware setup.
Symptom
With Secure Boot enabled the firmware refuses to launch the bootloader:
Verification failed: (0x1A) Security Violation
or the machine silently falls back to the firmware setup / Windows. Turning Secure Boot off in the BIOS makes Linux boot again.
Cause
GRUB/systemd-boot/Limine as shipped by Arch are unsigned, and the kernel is unsigned. The firmware's default key database (Microsoft KEK/db) does not vouch for them, so the UEFI image is rejected. There is no shim by default on Arch.
Fix
Put the firmware into **Setup Mode** (BIOS: Secure Boot -> Erase/Clear all keys, or 'Reset to Setup Mode'). Then:
sudo pacman -S sbctl
sudo sbctl status # expect: Setup Mode: Enabled
sudo sbctl create-keys
sudo sbctl enroll-keys -m # -m is not optional in practice
**Keep the -m.** sbctl(8) warns that some devices have signed firmware/option ROMs validated when Secure Boot is on. Enrolling only your own keys without Microsoft's certificates can leave the machine unable to initialise its own hardware. If your firmware has no 'reset to factory keys' option, you have no way back.
Find what actually needs signing rather than guessing paths. The Limine binary is named BOOTX64.EFI, not limine.efi:
sudo find /boot -iname '*.efi' -o -name 'vmlinuz-*'
Sign each real file, -s to register it so pacman hooks re-sign on update:
sudo sbctl sign -s /boot/vmlinuz-linux
sudo sbctl sign -s /boot/EFI/BOOT/BOOTX64.EFI
sudo sbctl sign -s /boot/EFI/GRUB/grubx64.efi # GRUB
sudo sbctl sign -s /boot/EFI/systemd/systemd-bootx64.efi # systemd-boot
sudo sbctl sign -s /boot/EFI/limine/BOOTX64.EFI # Limine
for f in /boot/EFI/Linux/*.efi; do sudo sbctl sign -s "$f"; done # UKIs (Omarchy)
Verify **before** re-enabling Secure Boot, because an unsigned binary here means the machine will not boot:
sudo sbctl verify
sudo sbctl list-files
sudo sbctl list-enrolled-keys
On Omarchy, limine-mkinitcpio-hook optdepends on sbctl and re-signs UKIs automatically once they are registered.
After re-enabling Secure Boot, sudo sbctl status should show Secure Boot: Enabled, Setup Mode: Disabled.
If you just want to move on: disable Secure Boot in firmware and stop there. Nothing on an Arch system requires it.
Verify
sudo sbctl status shows Secure Boot enabled with your keys enrolled, sudo sbctl verify reports every file signed, and the machine boots with Secure Boot on.