Hello, when I recently installed Solus I had to fix something using the efibootmgr application and took the opportunity to delete redundant entries of the ESP listed via sudo efibootmgr -b 0002 –B
. As it stands they all disappeared from the firmware boot options currently presented when hitting f12 on startup, except for a Fedora entry. I've tried the above efibootmgr from my installed Solus as well as a live USB version and while it disappears from efibootmgr's list it reappears at the next reboot.
Since I dual boot win10 ( for the sake of one game and one old friendship ) I tried another bit of advice I found:
From an admin cmd: bcdedit /enum all
and then with the Fedora boot entry UUID: bcdedit /delete { }
and it disappears..but it still present when I reboot the machine and hit f12 for efi boot entries.
If it helps any then the output of bcdedit enum /all in windows calls both the "Linux Boot Manager" (solus) and "Fedora" entries "Firmware Application (address)" but they have different identifiers and different Paths: EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI for Solus and /EFI/FEDORA/SHIM.EFI for the orphan Fedora entry. Those paths, as well as others of redundant boot entries are present on the file system of the ESP.
Any suggestions on how to get rid of the Fedora entry? : )