Restore Linux boot priority after a Windows update hijacks the UEFI boot order
The efibootmgr diagnosis and -o reordering are correct. The manual entry-creation example names a loader file that does not exist: I checked the file list of the limine package (extra, 12.6.1) and it ships usr/share/limine/BOOTX64.EFI. There is no limine.efi. Omarchy's own scripts reference /boot/EFI/limine/ and /boot/EFI/BOOT/, both holding BOOTX64.EFI. A user pasting --loader '\EFI\limine\limine.efi' creates a boot entry pointing at nothing, which on many firmwares is worse than the original problem.
efibootmgr writes NVRAM. A malformed --create can leave a dead entry. On a handful of buggy laptop firmwares, filling NVRAM with entries has caused firmware corruption. Delete stale entries with efibootmgr -b XXXX -B rather than accumulating them.
Symptom
The machine booted GRUB/Limine fine for months. After a Windows feature update (or a BIOS update, or a CMOS reset) it now boots straight into Windows, or shows grub rescue>. The Linux entry is still in the firmware's boot list but sits below Windows Boot Manager.
Cause
Windows Setup writes \EFI\Microsoft\Boot\bootmgfw.efi and pushes Windows Boot Manager to the front of the UEFI BootOrder variable. Some firmware also rewrites \EFI\BOOT\BOOTX64.EFI (the removable fallback), clobbering a Linux loader that was installed there.
Fix
Boot Linux via the firmware's one-time boot menu (F12/F11/Esc), then inspect:
sudo efibootmgr -v
Put your Linux loader first (use the numbers from *your* output):
sudo efibootmgr -o 0002,0000
If the Linux entry is missing entirely, recreate it:
# GRUB
sudo grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
# systemd-boot
sudo bootctl install
# Limine: confirm the real filename first — it is BOOTX64.EFI, not limine.efi
sudo find /boot/EFI -iname '*.efi'
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 \
--label "Limine" --loader '\EFI\limine\BOOTX64.EFI'
On Omarchy prefer the supported path, which rewrites the NVRAM entry for you:
sudo limine-mkinitcpio
Then verify with sudo efibootmgr -v that the new entry's File() path matches a file that actually exists before rebooting.
Verify
sudo efibootmgr | head -3 shows BootOrder: beginning with your Linux entry, and a cold boot lands on the Linux boot menu.