MVREFIND(8)

🎀 MVREFIND(8) 🎀 — the rEFInd manual, but make it bestie-friendly 💖

okay so you're in the rEFInd manual, section 8, and the whole vibe here is moving your rEFInd install around without breaking your boot. lowkey iconic. also there's a license fragment floating at the top that just says "any later version" — yes bestie, we're keeping that, it's giving "you may redistribute under the GPL, any later version" 🫶

---

✨ NAME ✨

mvrefind — moves a rEFInd installation from one location to another. that's it, that's the whole job 💅

---

🌸 SYNOPSIS 🌸

mvrefind SOURCE DEST

---

🦋 DESCRIPTION 🦋

So you wanna move a rEFInd installation from SOURCE to DEST, where both SOURCE and DEST are directories on the EFI System Partition (ESP), and SOURCE is holding a working rEFInd installation. simple, right? not so fast, because this operation entails taking several actions, and every single one of them matters:

• Renaming the SOURCE directory to DEST. 🏠➡️🏡
• Renaming the rEFInd binary to a suitable value given the new destination. For instance, if DEST is EFI/BOOT on the EFI System Partition (ESP), the rEFInd binary should be bootx64.efi (or something similar but with a different architecture code). 🏷️
• Altering the computer's NVRAM entries to point to rEFInd at its new location. 🔧
• If Shim is detected, renaming operations and NVRAM entry pointers are adjusted appropriately. 🛡️
• If the DEST exists, its contents are preserved. (we're not deleting anybody's stuff here, bestie, no cap 🙈)

Broadly speaking, mvrefind understands three types of locations for both SOURCE and DEST, relative to the root of the ESP:

• EFI/BOOT — the bootx64.efi (or similar for other architectures) filename in this location is the "fallback filename," which is used by removable boot media and as a boot loader of last resort on hard disks. Some EFIs can't remember their normal boot entries, and on them, rEFInd must be installed here (or as the Windows boot loader). When this directory is the DEST and it already exists, the existing EFI/BOOT is backed up to EFI/BOOT-rEFIndBackup; and if the SOURCE is EFI/BOOT and EFI/BOOT-rEFIndBackup exists, it is renamed to EFI/BOOT after rEFInd is moved to its destination. 🗂️
• EFI/Microsoft/boot — the bootmgfw.efi file in this location normally holds the Windows boot loader. Machines with broken EFIs may refuse to accept or remember proper boot entries and will instead boot this entry in preference to all others. In such cases, using rEFInd requires moving the Microsoft boot loader elsewhere and replacing it with rEFInd. When this directory is the DEST, mvrefind moves the original bootmgfw.efi file down one level (to EFI/Microsoft) and stores refind_x64.efi (or Shim) in that location. When moving from EFI/Microsoft/boot, this process is reversed. 🪟➡️🦋
• Anything else — any other SOURCE or DEST location is treated as a regular rEFInd installation, with a proper NVRAM entry created by efibootmgr. 🧚

mvrefind attempts to identify the ESP and refuses to move between the ESP and any other partition. (vibe check: failed, request denied 💀) When it does move files, it moves the main rEFInd binary, the refind.conf file, any identified Shim binary, and the icons, icons-backup, drivers_*, and keys subdirectories. If other rEFInd files or directories are present in SOURCE (such as a custom theme/icons directory), they will not be moved. If SOURCE is empty after the specified files and subdirectories are moved, SOURCE will be deleted. 👋

---

👑 AUTHORS 👑

Primary author: Roderick W. Smith (rodsmith@rodsbooks.com)

---

💜 SEE ALSO 💜

mkrlconf(8), refind-install(8), refind-sb-healthcheck(8).

https://www.rodsbooks.com/refind/

---

🌈 AVAILABILITY 🌈

The mvrefind command is part of the rEFInd package and is available from Roderick W. Smith.

---

okay that's the whole page, bestie, you ate that 🍓✨ and for the cute sign-off: this was the rEFInd Manual, version 0.14.2, brought to you by Roderick W. Smith — the <rainbow>MVREFIND(8)</rainbow> of it all 💖 no cap, go move some bootloaders responsibly 🎀