OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel critical common DISPUTE

GRUB 'error: symbol grub_is_shim_lock_enabled not found' after a grub update

archendeavouroscachyosmanjarogrubuefi
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

All four sources were read. bbs 287024 has the exact error block, Secure Boot off, and mneiner's fix: three grubx64.efi copies from different --efi-directory choices, cleaned up to one. bbs 286980 was fixed by reinstalling with --efi-directory=/boot. bbs 308079 has the 2025 grub_is_using_legacy_shim_lock_protocol variant, the /boot/EFI/GRUB plus /boot/EFI/EFI/GRUB duplicate, and the cloned drive's ESP. The GRUB wiki warning says a new configuration 'might use a function unknown to the existing GRUB binary', which supports the cause. One claim in the fix is overstated. It says two reporters fixed it with --disable-shim-lock. In 287024 one reporter (mneiner) confirmed it worked and another (Flex) said it did not. In 308079 it was only suggested, and both confirmed fixes there were removing duplicates. The fix is rewritten to say that. The rest is kept, including the note that Omarchy 4 boots Limine (grub is not installed here). Not exercised: there is no GRUB system to test on.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Deleting the grubx64.efi that the firmware actually boots, before a working replacement is installed, leaves the machine with no boot loader. Delete stray copies only after efibootmgr -v confirms they are unused. Downgrading grub with pacman -U while the rest of the system stays current is a deliberate partial downgrade, so return to the current version once the root cause is fixed.

Symptom

After updating, GRUB shows its menu but every entry fails:


Loading Linux linux ...
error: symbol 'grub_is_shim_lock_enabled' not found.
Loading initial ramdisk ...
error: symbol 'grub_is_shim_lock_enabled' not found.
Press any key to continue...

A 2025 variant reads grub_is_using_legacy_shim_lock_protocol not found. Secure Boot is usually off, and re-running grub-install and grub-mkconfig "did nothing".

Cause

GRUB's EFI core image (grubx64.efi) and the modules in /boot/grub/x86_64-efi/ come from different GRUB versions. A newer grub.cfg or module calls a symbol the old core does not export. The usual reason is that the firmware boots a different grubx64.efi from the one grub-install just updated: an earlier install used another --efi-directory or --bootloader-id, leaving copies such as /boot/EFI/GRUB/grubx64.efi and /boot/EFI/EFI/GRUB/grubx64.efi, or a cloned backup drive carries its own ESP. The Arch wiki warns that a configuration using a function unknown to the existing GRUB binary makes the system unbootable.

Fix

Boot a live USB and chroot if the system cannot boot (see chroot-recovery-btrfs-missing-subvol). Then:


# 1. which loader does the firmware actually start?
efibootmgr -v

# 2. how many GRUB cores are lying around?
find /boot /efi -iname 'grubx64.efi' 2>/dev/null

Re-run grub-install with the same ESP mount point and the same --bootloader-id as the entry the firmware boots, and regenerate the config. This example assumes the ESP is mounted at /boot and the entry is GRUB:


grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg

Remove the stray copies you found in step 2 that no boot entry uses, and delete their stale NVRAM entries with efibootmgr --bootnum XXXX --delete-bootnum. The confirmed fixes in the forum threads came from this: deleting a duplicate EFI/EFI/GRUB directory, cleaning three copies down to one, or removing a cloned backup drive's ESP.

If it still fails with Secure Boot off, you can add --disable-shim-lock to the grub-install line. One reporter fixed it this way, and another in the same thread said it did not help. As a last resort, downgrade from the cache:


ls /var/cache/pacman/pkg/grub-*
pacman -U /var/cache/pacman/pkg/grub-<previous-version>-x86_64.pkg.tar.zst

Omarchy 4 boots with Limine and is not affected.

Verify

find /boot /efi -iname grubx64.efi lists exactly the one path that efibootmgr -v shows for the BootCurrent entry, and a reboot loads the kernel without the symbol error.

Sources

grub-symbol-shim-lock-not-found