I've been trying to install Linux Mint, but first, I need to clean up my UEFI boot entries. After a failed attempt to set up Linux Mint, I've ended up with a cluttered boot menu containing configurations I no longer need. I've wiped my SSD clean, clearing out both Windows and Linux, and I want to delete unnecessary entries via efibootmgr. When I run `efibootmgr`, I see a list of boot entries, including Windows, Ubuntu, and a couple of other mysterious entries labeled as Boot0002 and Boot0006. I'm not sure what these two are — any ideas? I recognize that Boot0003 is my CD/DVD drive and Boot0007 is my USB stick. I'm looking for guidance on safely removing those unknown UEFI entries!
3 Answers
You can simplify this process using a tool I found: [EFIBOOTMGR-NVRAM-ENTRY-EDITOR](https://github.com/LINUX-OASIS/EFIBOOTMGR-NVRAM-ENTRY-EDITOR). Just download it, run the program, and you can manage your UEFI entries directly — super easy! Just remember to press space to select options and then hit enter to execute.
Thanks for the tip! I'm not super familiar with running scripts, though. Do I just save the file and run it in terminal with a `.sh` extension or what?
You should be able to clear those entries easily! Boot0002 might be just a generic entry for fallback purposes, but if you’re not using it, no harm in getting rid of it. As for Boot0006, it usually indicates a USB device that might not be relevant if it’s not showing in your boot menu anymore. If it's not causing any problems, I'd suggest just leaving it be since you have your Mint installer all set up! Just double-check that nothing vital gets wiped!
For Boot0002, it likely points to a fallback bootloader at `EFIBootbootx64.efi`, or it could just be a BIOS booting from the hard drive. If you want it gone, you might want to disable CSM or Legacy Boot, which could clean it up. Boot0006 is probably linked to a USB device. Make sure you verify these entries before you remove anything to avoid boot issues!
Exactly! Just make sure it has execute permissions set. You can do that with `chmod +x filename.sh` before running it.