Arch Linux

a_manthey

Member

Registered: 2017-08-21

Posts: 40

SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

After upgrade to  2:2.12.r359.g19c698d12-1 and

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

grub does not load kernel any longer and sends the error message above.

Any help appreciated Andreas

Last edited by a_manthey (2025-09-07 10:48:26)

StarWolf3000

Member

Registered: 2025-06-23

Posts: 32

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

Either disable Secure Boot or configure your system correctly to use Secure Boot and the pacman hooks to update signatures and signed binaries.

---

Mainboard: GIGABYTE B550 AORUS ELITE V2 | CPU: Ryzen 7 5800X | RAM: 32 GB
GPU: GeForce RTX 4060 8 GB (575.64.05 proprietary) | Display: BenQ BL2405 1920x1080
Kernel: 6.15.9 stable | Boot Manager: GRUB2 | DE: KDE Plasma | Login Manager: SDDM | Window Manager: KWin (Wayland)

a_manthey

Member

Registered: 2017-08-21

Posts: 40

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

secure boot is disabled

m3rlyn

Member

Registered: 2025-09-06

Posts: 3

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

This happened to me today. Secure boot is off. I used grub-install and grub-mkconfig, which didn't fix it.

I rolled the grub version back with pacman -U.

# pacman -U /var/cache/pacman/pkg/grub-2\:2.12.r292.g73d1c959-1-x86_64.pkg.tar.zst

I've put grub in the pacman ignore list for now.

StarWolf3000

Member

Registered: 2025-06-23

Posts: 32

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

If it is a regression, then for the time being either stay at 2.12.r292.g73d1c959 or use --disable-shim-lock (even if you're not using Secure Boot and signing at all):

# grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=GRUB --disable-shim-lock
# grub-mkconfig -o /boot/grub/grub.cfg

The only other posts on the web I've found are older and designate issues with Secure Boot, or use Endeavour with the most recent version. There've been no reports on Arch Gitlab and GRUB upstream (savannah.gnu.org).

---

Mainboard: GIGABYTE B550 AORUS ELITE V2 | CPU: Ryzen 7 5800X | RAM: 32 GB
GPU: GeForce RTX 4060 8 GB (575.64.05 proprietary) | Display: BenQ BL2405 1920x1080
Kernel: 6.15.9 stable | Boot Manager: GRUB2 | DE: KDE Plasma | Login Manager: SDDM | Window Manager: KWin (Wayland)

j0inty

Member

Registered: 2025-09-07

Posts: 1

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

Hi,

I have the same problem with my laptop which is a Fujitsu Celsius H760. I updated the kernel to 6.16.5-arch1-1 and grub to 2:2.12.r359.g19c698d12-1.

The laptop stuck at the Fujitsu logo from bios, but before freezing it was possible to enter the bios setup (F2) or open the boot device menu (F12).

At first I though it is a bios settings problem, so I tried with secure boot and without it. Then I booted the archiso 2025.09.01 from USB stick.

I remember that grub was updated so I decided to downgrade grub to latest working version on my celsius.

With 2.12.r292.g73d1c959 I could boot without any problems.

On another desktop box I also updated arch linux with grub and here I do not had any problems.

regards
j0inty

a_manthey

Member

Registered: 2017-08-21

Posts: 40

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

There are many posts about the same or simalar errors. Some of them report more than one grubx64.efi in subdirs of /boot/EFI as cause for the error.
So i found:

 
$ ls -alR /boot/EFI
/boot/EFI:
insgesamt 24
drwxr-xr-x 6 root root 4096  6. Sep 10:32 .
drwxr-xr-x 4 root root 4096  1. Jan 1970  ..
drwxr-xr-x 3 root root 4096  6. Sep 10:32 EFI
drwxr-xr-x 2 root root 4096 17. Sep 2021  GRUB

/boot/EFI/EFI:
insgesamt 12
drwxr-xr-x 3 root root 4096  6. Sep 10:32 .
drwxr-xr-x 6 root root 4096  6. Sep 10:32 ..
drwxr-xr-x 2 root root 4096  6. Sep 10:32 GRUB

/boot/EFI/EFI/GRUB:
insgesamt 156
drwxr-xr-x 2 root root   4096  6. Sep 10:32 .
drwxr-xr-x 3 root root   4096  6. Sep 10:32 ..
-rwxr-xr-x 1 root root 151552  7. Sep 10:35 grubx64.efi

/boot/EFI/GRUB:
insgesamt 156
drwxr-xr-x 2 root root   4096 17. Sep 2021  .
drwxr-xr-x 6 root root   4096  6. Sep 10:32 ..
-rwxr-xr-x 1 root root 151552 18. Mai 10:20 grubx64.efi

I think i used different efi-directories in previous grub-install-commands.
In my case /boot/EFI is the original. I fixed my issue by:

# rm -r /boot/EFI/EFI

# pacman Syu grub

and using the correct efi-dir in grub-install:

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

m3rlyn

Member

Registered: 2025-09-06

Posts: 3

Re: SOLVED grub error "grub_is_using_legacy_shim_lock_protocol not found"

My issue was also due to two versions of grubx64.efi. In my case it was on a different drive. I had a backup which was a straight clone of my system drive, including the /efi partition. Deleting the duplicate /efi partition fixed the issue, and I can now use grub 2:2.12.r359.g19c698d12-1. (The latest version).