Get past Secure Boot blocking the Omarchy ISO or the installed system
Checked on this Omarchy 4.0.2-1 workstation (limine 12.6.0-1, limine-mkinitcpio-hook 1.37.1-1, systemd 261.2-1, kernel 7.1.9) and against upstream. The record's central advice is right and is upstream's own position: the getting-started manual page says "You must turn off Secure Boot and/or TPM in the BIOS", and the manual-installation page says "remember to turn off Secure Boot in the BIOS". Both cited learn.omacom.io URLs return HTTP 200 and both contain that text, so they stand. Two claims in the cause are wrong. Unsigned DKMS modules are not what Secure Boot rejects: zgrep MODULE_SIG /proc/config.gz on this machine shows CONFIG_MODULE_SIG_FORCE unset and /sys/kernel/security/lockdown reads [none], so Arch's kernel does not enforce module signatures under Secure Boot. What is rejected is the unsigned EFI binary, Limine's BOOTX64.EFI and the UKI. The TPM-measurement claim is also wrong for Omarchy 4: /etc/kernel/cmdline reads cryptdevice=PARTUUID=...:root and /etc/mkinitcpio.conf.d/omarchy_hooks.conf uses the busybox encrypt hook, so nothing is sealed to the TPM and no PCR change can lock anyone out. In the fix, mokutil --sb-state is not available: pacman -Q mokutil returns not found, and mokutil targets shim, which Omarchy does not ship. I replaced it with the EFI variable read that Limine's own /usr/lib/limine/limine-common-functions:271 performs, and confirmed the encoding on this box (the variable reads 0, Secure Boot off). Two gaps mattered more than the errors. First, the danger omitted BitLocker, which is the real lockout risk: disabling Secure Boot or TPM triggers a BitLocker recovery prompt, and upstream's dual-boot manual page requires BitLocker off for a free-space install. Second, the record offered no recovery if the installed machine does not boot, so I added the three real routes read off this machine: Limine's Snapshots submenu (BOOT_ORDER="*, *fallback, Snapshots" in /etc/limine-entry-tool.d/omarchy-defaults.conf), the \EFI\BOOT\BOOTX64.EFI fallback path (ENABLE_LIMINE_FALLBACK=yes), and /usr/share/omarchy/bin/omarchy-setup-direct-boot, whose source I read and which refuses on AMI and Apple firmware. I also added a labelled section on running with Secure Boot on, because it is achievable: limine-common-functions defines sb_sign and calls it on the Limine binary, limine-mkinitcpio-install line 186 notes the UKI is signed by sbctl's own mkinitcpio hook, sbctl 0.18-2 is in extra, and sbctl upstream ships contrib/mkinitcpio/sbctl and contrib/pacman/ZZ-sbctl.hook. That section is ordered so that signing completes before Secure Boot is re-enabled, which is the sequence that avoids an unbootable machine. grep -rni 'secure.boot|tpm' /usr/share/omarchy returns only an unrelated blog link in install/hardware/fix-surface-keyboard.sh, so Omarchy itself documents no position beyond the manual. I confirmed the pacman guard (/usr/bin/omarchy-update-pacman-guard) blocks only -S combined with -u, so pacman -S --needed sbctl is allowed. Dropped the GitHub issue search URL, which is a live query rather than a page and asserts nothing checkable. Not exercised: I ran no sbctl command, enrolled no key, touched no firmware setting, and could not list /boot because it is a vfat ESP mounted dmask=0077, so the UKI path comes from /usr/share/omarchy/bin/omarchy-setup-direct-boot and the environment notes rather than a directory listing. Severity high and frequency very-common both still fit.
**BitLocker.** If this machine also boots Windows, turning Secure Boot or TPM off will trigger a BitLocker recovery prompt, because BitLocker seals its key to firmware state. Have the recovery key in hand, or better, turn BitLocker off in Windows first under **Settings > Privacy & Security > Device encryption**. Omarchy's dual-boot manual page requires this anyway: a free-space install is not compatible with BitLocker, which encrypts the whole drive rather than a partition.
**Intel RST to AHCI.** Switching an existing Windows install from Intel RST to AHCI makes Windows blue-screen on boot unless you enable safe-mode boot in Windows first.
**The installer wipes the drive.** The full-disk option erases the selected drive and applies full-disk encryption. Back up before selecting a disk that has data on it, and use the free-space install if you mean to keep another OS.
**Enrolling Secure Boot keys.** sbctl enroll-keys without -m removes Microsoft's keys, which can brick a graphics card whose option ROM is signed by them. Never re-enable Secure Boot before sbctl verify reports every EFI binary signed, or the machine will not boot. Recovery from that is turning Secure Boot back off in firmware, which always works, so keep the firmware password handy if you have set one.
Symptom
The Omarchy ISO won't boot at all ("Security Violation", "Invalid signature detected", or it drops straight back to the firmware menu), or the install completes but the machine refuses to boot the new Limine entry afterwards.
Cause
Omarchy ships an unsigned boot chain. Secure Boot in user mode refuses to execute an EFI binary it cannot verify, and on Omarchy 4 that is Limine's BOOTX64.EFI and the unified kernel image at /boot/EFI/Linux/omarchy_linux.efi. That is what produces "Security Violation" or "Invalid signature detected", both for the ISO and for the installed system.
Unsigned DKMS modules are **not** the reason. Arch's kernel is built with CONFIG_MODULE_SIG_FORCE unset and does not enter lockdown under Secure Boot, so unsigned out-of-tree modules still load. Nor is anything on Omarchy 4 sealed to the TPM: the root is unlocked by passphrase through the busybox encrypt hook, with cryptdevice=PARTUUID=...:root in /etc/kernel/cmdline, so no PCR change can invalidate the boot chain. Omarchy's manual asks for TPM to be off alongside Secure Boot, and gives the reason as these being Microsoft security schemes rather than any measurement Omarchy depends on.
Fix
## Turn Secure Boot off, which is the supported path
Omarchy's manual is explicit: "You must turn off Secure Boot and/or TPM in the BIOS. You have to turn these off to be able to install Omarchy." Read the BitLocker warning under danger first if this machine also boots Windows.
Enter firmware setup (usually F2, Del or F10 at power-on) and:
- Set **Secure Boot** to *Disabled*. Some vendors require setting **OS Type** to *Other OS* first, or clearing the keys with "Delete all Secure Boot variables" or "Reset to Setup Mode".
- Disable **TPM / PTT / fTPM** if present.
- Set SATA/NVMe mode to **AHCI**, not *RAID* or *Intel RST*. Linux cannot see the disk in RST mode.
- Disable **Fast Boot**.
- Save and exit, then boot the USB.
Confirm from the live shell that it really is off. systemd is always present, so this needs no extra package:
bootctl status | grep -i 'secure boot'
# expect: Secure Boot: disabled (disabled)
The dependency-free equivalent is to read the EFI variable directly. This is the exact check Limine's own tooling makes in /usr/lib/limine/limine-common-functions:
od -An -t u1 -j4 -N1 \
/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
# 0 = disabled, 1 = enabled
Do not use mokutil --sb-state on Omarchy 4. mokutil is not installed, and it is a tool for shim, which Omarchy does not ship.
## If the installed machine will not boot afterwards
Omarchy 4 boots a UKI through Limine, so there is no GRUB to reinstall and no /boot/loader/entries to repair. Three routes back, in order of least effort:
- Pick an older entry from Limine's **Snapshots** submenu.
/etc/limine-entry-tool.d/omarchy-defaults.confsetsBOOT_ORDER="*, *fallback, Snapshots". There is no fallback initramfs behind that:MKINITCPIO_FALLBACKis unset andlimine-mkinitcpio-installdeletes a fallback UKI when it is, so the snapshot entries are the recovery route. - If the firmware dropped the Limine boot entry, Limine is also installed at the default fallback path
\EFI\BOOT\BOOTX64.EFI(ENABLE_LIMINE_FALLBACK=yesin the same file), so selecting the disk itself in the firmware boot menu still reaches it. - Register the UKI as its own EFI entry, which helps on firmware that keeps discarding custom entries:
omarchy-setup-direct-boot
It refuses on American Megatrends and Apple firmware by design, and it warns that snapshot booting then has to go through the firmware boot menu.
## Running with Secure Boot on, which Omarchy does not support but which does work
Omarchy documents no Secure Boot position and ships no signing setup. The Limine hook it uses does: /usr/lib/limine/limine-common-functions defines is_sb_installed and sb_sign, and signs the Limine binary with sbctl whenever it deploys one, while /usr/share/libalpm/scripts/limine-mkinitcpio-install notes the UKI is signed by sbctl's own mkinitcpio hook. So once sbctl is set up, signatures survive kernel and Limine updates without further work.
**Order matters, and getting it backwards leaves an unbootable machine.** Install, enrol and sign while Secure Boot is still **off**, and turn it back on in firmware only after sbctl verify is clean.
omarchy update # bring the system and the pacman databases current
sudo pacman -S --needed sbctl # allowed: the guard only blocks -S combined with -u
Put the firmware in Setup Mode (the "Delete all Secure Boot variables" or "Reset to Setup Mode" option), boot back in, then:
sudo sbctl status
sudo sbctl create-keys
sudo sbctl enroll-keys -m # -m keeps Microsoft's keys
sudo sbctl verify # lists every unsigned EFI file on the ESP
Sign each path sbctl verify names, then run it again until it reports nothing unsigned:
sudo sbctl sign -s <path reported by sbctl verify>
sudo sbctl verify
Only then re-enable Secure Boot in firmware. Enrolling without -m drops Microsoft's keys, which can brick option ROMs on some cards, so keep -m unless you know the hardware.
Verify
bootctl status reports Secure Boot: disabled (disabled), or the EFI variable reads 0:
bootctl status | grep -i 'secure boot'
od -An -t u1 -j4 -N1 \
/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
The ISO then boots to the installer, and after the install the machine comes up in Limine with an **Omarchy** entry. Confirm the UKI it booted:
sudo ls /boot/EFI/Linux/
# expect omarchy_linux.efi
If you took the sbctl route instead, sudo sbctl verify reports every EFI binary signed and bootctl status reports Secure Boot: enabled (user).
Sources
- https://learn.omacom.io/2/the-omarchy-manual/50/getting-started
- https://learn.omacom.io/2/the-omarchy-manual/96/manual-installation
- https://github.com/omacom/omarchy/blob/quattro/manual/02-getting-started.md
- https://github.com/omacom/omarchy/blob/quattro/manual/50-dual-boot-install.md
- https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot
- https://github.com/Foxboron/sbctl