+<p>Some EFI implementations do a poor job of honoring the boot options set via Linux's <tt>efibootmgr</tt> or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. Broadly speaking, there are two alternative names that are most useful:</p>
+
+<ul>
+
+<li><tt class="userinput">EFI/BOOT/boot<i>arch</i>.efi</tt>—This name
+ is the official EFI fallback filename. It's most commonly used on
+ bootable removable disks, but it can be used on hard disks. It's
+ typically used only if no NVRAM entry points to a valid boot
+ loader.</li>
+
+<li><tt class="userinput">EFI/Microsoft/Boot/bootmgfw.efi</tt>—This
+ filename has no official special standing in the EFI specification, but
+ as a practical matter, many EFI implementations use it as a fallback
+ boot loader in addition to or instead of
+ <tt>EFI/BOOT/boot<i>arch</i>.efi</tt>. In fact, some give it such a
+ high precedence that you can't boot anything that's not given this
+ name!
+
+</ul>
+
+<p>If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can <a href="#mvrefind">use the <tt>mvrefind.sh</tt> script</a> to move your installation in one step, or you can <a href="#manual_renaming">move and rename your files manually.</a></p>
+
+<a name="mvrefind">
+<h3>Using <tt>mvrefind.sh</tt></h3>
+</a>
+
+<p>The easiest way to move a rEFInd installation, at least in Linux, is to use the <tt>mvrefind.sh</tt> script. If you installed from one of my RPM or Debian packages, this script should be installed in <tt>/usr/sbin</tt>, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux <tt>mv</tt> command, but you pass it the directory in which a rEFInd installation appears and a target location:</p>
+
+<pre class="listing">
+# <tt class="userinput">mvrefind.sh /boot/efi/EFI/BOOT /boot/efi/EFI/refind</tt>
+</pre>
+
+<p>This example moves rEFInd from <tt>/boot/efi/EFI/BOOT</tt> to <tt>/boot/efi/EFI/refind</tt>. It differs from <tt>mv</tt> in several ways:
+
+<ul>
+
+<li>The script renames rEFInd in a way that's sensitive to its source and
+ destination directories—for instance, <tt>mvrefind.sh</tt> knows
+ that rEFInd (or shim, for Secure Boot installations) must be called
+ <tt>bootx64.efi</tt> on a 64-bit installation in
+ <tt>/boot/efi/EFI/BOOT</tt>, so it looks for rEFInd under that name
+ when copying from this directory, or it renames rEFInd to that name
+ when copying to it.</li>
+
+<li>The script creates a new NVRAM entry for rEFInd when it copies to any
+ location but <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt>. It
+ refuses to copy to such locations if it's not run from an EFI-mode
+ boot.</li>
+
+<li>The script knows enough to back up existing boot loaders stored in
+ <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt> when copying to these
+ locations. For the former location, the script backs up
+ <tt>EFI/BOOT</tt> as <tt>EFI/BOOT-rEFIndBackup</tt>; for the latter, it
+ moves <tt>EFI/Microsoft/Boot/bootmgfw.efi</tt> to
+ <tt>EFI/Microsoft/bootmgfw.efi</tt>.</li>
+
+</ul>
+
+<p>The <tt>mvrefind.sh</tt> script is likely to be useful in resolving boot problems—if your system won't boot, you can try copying the installation to <tt>/boot/efi/EFI/BOOT</tt>, <tt>/boot/efi/EFI/Microsoft/Boot</tt>, and <tt>/boot/efi/EFI/refind</tt> in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at <tt>/boot/efi</tt>.) You could also copy a BIOS-mode install from <tt>/boot/efi/EFI/BOOT</tt> or <tt>/boot/efi/EFI/Microsoft/Boot</tt> to <tt>/boot/efi/EFI/refind</tt> to make it more robust against Windows repairs (assuming your firmware isn't broken).</p>
+
+<a name="manual_renaming">
+<h3>Renaming Files Manually</h3>
+</a>
+