UEFI remove unwanted boot entries from BIOS solved easily

Last month, I installed a brand new HDD and used Windows PE to partition and format it. The following photo was taken when the HDD was blank before Windows was installed. I wonder why there were two "Windows Boot Manager" entries.

Matthew Wai said:

Find the specific identifier by running the following command:<br>
<br>
<font size="3"><strong>BCDEdit /enum firmware</strong></font><br>
<br>

Code:

Firmware Application (101fffff)<br>
-------------------------------<br>
identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;{562f5076-413a-11eb-bfdb-e0d55ecc65a3}<br>
description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Generic STORAGE DEVICE 0903<br>
<br>
Firmware Application (101fffff)<br>
-------------------------------<br>
identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;{562f5077-413a-11eb-bfdb-e0d55ecc65a3}<br>
description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; CD/DVD Drive<br>
<br>
Firmware Application (101fffff)<br>
-------------------------------<br>
identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;{562f5078-413a-11eb-bfdb-e0d55ecc65a3}<br>
path &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;\EFI\Microsoft\Boot\bootmgfw.efi<br>
description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Windows Boot Manager<br>
<br>
Firmware Application (101fffff)<br>
-------------------------------<br>
identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;{562f507a-413a-11eb-bfdb-e0d55ecc65a3}<br>
description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Hard Drive<br>
<br>

Unfortunately this doesn't work for my case (legacy setup, not UEFI). I will download latest Strelec or Windows 10 PESE and boot in UEFI mode. Then I will use EasyUEFI to hopefully get rid of any unwanted entries.

You may use BCDEdit after booting into Window PE in UEFI mode.

BOOTPE.iso (598.8 MB)

I use the above Windows PE.

topgundcp said:

From time to time, BCD will grow in size and contains unwanted entry/entries. If you boot your PC from multiple sources (USB's, Win 10, Win 7, Linux etc...), EFI firmware will add an entry for each device. Open Admin command and type:

mountvol U: /s ====> assign letter U to EFI system partition (or use any unused letter)
del /s /f /q U:\efi\*.* ====> Delete everything under U:\efi folder
bcdboot c:\windows /s U: /f UEFI =-===> Rebuild a clean BCD
mountvol U: /d ====> Remove the letter U from EFI system partition

With this procedure, you don't have to mess around with bcdedit and identifier.
If there's need to add another entry for dual boot, use bcdboot command again.

Just wanted to say thank you! This simple set of steps is all that's needed in a multitude of scenarios

@EdTittel
I am now using Firefox portable on BOOTPE, which supports portable apps such as:

Firefox: Mozilla Firefox, Portable (browser) | PortableApps.com
Macrorit Partition Expert: Partition Magic Freeware to manage Disk Partitions
DiskGenius: Free Download DiskGenius Online
Auslogics Disk Defrag: Download Portable Auslogics Disk Defrag 8.0.24.0
7-Zip: 7-Zip Portable (file archiver) | PortableApps.com
VLC Media Player: VLC Media Player Portable - Free download and software reviews - CNET Download

Press the Windows key + R and run CMD to open a CMD window.
You can run commands such as:

BCDEdit
IPconfig /all
ChkDsk C: /f
SnippingTool
Paint
DevMgmt.msc
DiskMgmt.msc
DiskPart

I want to delete a useless boot entry that doesn't point to anything. I used this program to identify it. However not sure what the string correlates to in the bcdedit output.











I have 3 legitimate boot entries. One Linux (1TB in the middle). The top one should be just one for Samsung 970 and the bottom should also be just one. I have 2 false entries.




- - - Updated - - -

what is this string from EAsyUEFI?

I am aware of the bcdedit /delete {identifier} command.
The question is, what is the correct identifier to use? I do not understand how extract the identifier from the bad boot entry, or how to identify the bad boot entry. I want to be 100% certain I am deleting the correct boot entry.
The EasyUEFI does not show the "identifier" but another string and as I inquired above, how do I correlate them?



- - - Updated - - -

which two entries in this list correlate to two bad entries in the boot menu?

dictum said:

The question is, what is the correct identifier to use?

I would never touch the identifier shown under Windows Boot Manager.
I would only delete the identifiers shown under Firmware Application.