Update causes problem with rEFInd bootloader

It’s possible that an update of Windows or of Manjaro’s Grub has reset the default boot entry in BIOS.

Reinstalling rEFInd, and then booting to your BIOS to make sure rEFInd UEFI Bootloader is selected as first in boot order, should correct that.


To avoid this happening again, consider installing rEFInd to the fallback location (i.e: $ESP/EFI/BOOT) – All files currently in $ESP/EFI/refind would then reside under $ESP/EFI/BOOT instead.

Generally, another OS will not write it’s EFI boot files to the fallback location when it differs from the main boot file (example when $ESP/EFI/Manjaro/grubx64.efi differs from $ESP/EFI/boot/refind_x64.efi) and when rEFInd is then set as the default bootloader, it tends to stay that way.

(I’ve been doing exactly this for many years.)

The following is taken from my related article [Multiboot] Windows and Linux on Separate Disks:

More in-depth information can be found on Rod Smith’s site The rEFInd Boot Manager and specifically Keeping rEFInd Booting.


Note that despite it’s name manjaro-refind-installer actually has little to do with installing rEFInd. However, you can use this package to easily select the kernel rEFInd should boot.

Beyond that, it’s usefulness is questionable.


Do this for a typical rEFInd installation from Manjaro:

1. Install the rEFind package from the official Manjaro repo:

sudo pacman -S refind

2(a). Install rEFInd to the usual location (/ESP/refind):

sudo refind-install

:point_right:or:point_left:

2(b). Install rEFInd to the fallback location (/EFI/BOOT):

sudo refind-install --usedefault /dev/sdXY

I hope this helps.

Regards.


(Note:- it’s also possible you have another issue entirely.)

1 Like