I was hoping someone could help me hide the 'Fallback boot loader' that appeared on our machines after we moved from Windows 7 to Windows 10. I thought I'd simply add 'Fallback boot loader' or 'Fallback' to my 'dont_scan_volumes' option, but that didn't work. Has anyone crossed this bridge before, and if so, how did you hide it? If I add 'EFI' to my 'dont_scan_volumes' option in the refind.conf file, it disappears, but so does the Windows 10 option.
Appreciate your help
Morgan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, not sure why my 'EFI/boot' is now 'EFI/Boot', but adding "EFI/Boot" to 'dont_scan_dirs' worked. My dont_scan_dirs config looks like this now (uncommented):
I'm having a similar issue after I upgraded Mac OSX to Sierra and Window 7 to Windows 10. I have Windows 10 in my other lab and refind doesn't detect the EFI/Boot at all. The diffrenece is that the other lab has Mac OSX El capitan installed instead of Mac OSX Sierra. I'm not sure if Refind is acting diffrently with MAcOS sierra or Windows 10.
This fallback bootloader is bootx64.efi. Not sure why is seing this now after the upgrades. I'm upgrading one of my El Capitan computer to Sierra to see if the Fallback appears after I reinstalled refind.
Thank You,
Ben
Last edit: crazyben21 2017-05-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
rEFInd hides the fallback boot loader (EFI/BOOT/bootx64.efi on x86-64 systems) if that boot loader is byte-for-byte identical with another one; but if it's not identical, rEFInd does not hide it. The idea is that a duplicate boot loader is probably just extra menu clutter, but if it's not identical, it might be a boot loader for another OS and so could be important. If the fallback loader had been hidden but suddenly appears, chances are either it or its duplicate has been updated, but not both of them.
If you know the boot loader that the fallback duplicates, you could copy the more up-to-date file over the older one. That should fix the problem. Alternatively, you could use one of the dont_scan_* options; but be aware that a careless use of this feature could end up hiding bootable USB flash drives and CD-Rs, which you might not want to do. I recommend you use a volume label with dont_scan_dirs, as in dont_scan_dirs HPESP:\EFI\BOOT to hide the EFI\BOOT directory on the volume called HPESP while enabling the fallback boot loader to be read from other volumes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good morning
I was hoping someone could help me hide the 'Fallback boot loader' that appeared on our machines after we moved from Windows 7 to Windows 10. I thought I'd simply add 'Fallback boot loader' or 'Fallback' to my 'dont_scan_volumes' option, but that didn't work. Has anyone crossed this bridge before, and if so, how did you hide it? If I add 'EFI' to my 'dont_scan_volumes' option in the refind.conf file, it disappears, but so does the Windows 10 option.
Appreciate your help
Morgan
Ok, not sure why my 'EFI/boot' is now 'EFI/Boot', but adding "EFI/Boot" to 'dont_scan_dirs' worked. My dont_scan_dirs config looks like this now (uncommented):
dont_scan_dirs ESP:/EFI/boot,EFI/Dell,EFI/memtest86,EFI/Boot
Morgan
Hello Morgan,
I'm having a similar issue after I upgraded Mac OSX to Sierra and Window 7 to Windows 10. I have Windows 10 in my other lab and refind doesn't detect the EFI/Boot at all. The diffrenece is that the other lab has Mac OSX El capitan installed instead of Mac OSX Sierra. I'm not sure if Refind is acting diffrently with MAcOS sierra or Windows 10.
This fallback bootloader is bootx64.efi. Not sure why is seing this now after the upgrades. I'm upgrading one of my El Capitan computer to Sierra to see if the Fallback appears after I reinstalled refind.
Thank You,
Ben
Last edit: crazyben21 2017-05-11
rEFInd hides the fallback boot loader (
EFI/BOOT/bootx64.efion x86-64 systems) if that boot loader is byte-for-byte identical with another one; but if it's not identical, rEFInd does not hide it. The idea is that a duplicate boot loader is probably just extra menu clutter, but if it's not identical, it might be a boot loader for another OS and so could be important. If the fallback loader had been hidden but suddenly appears, chances are either it or its duplicate has been updated, but not both of them.If you know the boot loader that the fallback duplicates, you could copy the more up-to-date file over the older one. That should fix the problem. Alternatively, you could use one of the
dont_scan_*options; but be aware that a careless use of this feature could end up hiding bootable USB flash drives and CD-Rs, which you might not want to do. I recommend you use a volume label withdont_scan_dirs, as indont_scan_dirs HPESP:\EFI\BOOTto hide theEFI\BOOTdirectory on the volume calledHPESPwhile enabling the fallback boot loader to be read from other volumes.