Multiboot menu has "Windows Boot Manager" entries that can't be remove

x509 · 27 Aug 2021

I use EasyBCD to multiboot between my "production" Windows partition and a "scratch" partition for doing test installs, etc. Sometime soon, I would like to add a Win 11 pre-release, for learning purposes.

I use the "classic" boot menu, which is just a list of bootable partitions, Besides the two real windows partitions I now have 4 bogus "Windows Boot Manager" entries. if I select one of these entries, I get an error message, nothing more. I can't seem to find a way to remove these entries using EasyBCD.

What did I do to create these bogus entries?

What do I need to to to remove them, which is what I really care about?

AddRAM · 28 Aug 2021

When I converted from MBR to GPT on my X299, it still shows the MBR install on the 970 Pro listed in the Boot Options, as well as the new Windows Boot Manager entry.

I`d like to remove any unneeded boot entries from the list in the Bios too.

Let me know if and how you removed it from the Boot Option list.

NavyLCDR · 28 Aug 2021

@x509,

In a command prompt with Admin privileges run:

Code:

bcdedit

Take note of the identifier of the entry you want to delete:

Code:

C:\Windows\system32>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
flightsigning           Yes
default                 {current}
resumeobject            {37faee11-e520-11eb-a5f8-010101010000}
displayorder            {current}
                        {37faee0d-e520-11eb-a5f8-010101010000}
toolsdisplayorder       {memdiag}
timeout                 3

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {37faee11-e520-11eb-a5f8-010101010000}
nx                      OptIn
bootmenupolicy          Standard
quietboot               No

Windows Boot Loader
-------------------
identifier              {37faee0d-e520-11eb-a5f8-010101010000}
device                  partition=E:
path                    \Windows\system32\winload.efi
description             Windows Server
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=E:
systemroot              \Windows
resumeobject            {37faee0c-e520-11eb-a5f8-010101010000}
nx                      OptOut

C:\Windows\system32>

Then run:

Code:

bcdedit /delete <identifier>

For example:

Code:

C:\Windows\system32>bcdedit /delete {37faee0d-e520-11eb-a5f8-010101010000}

x509 · 31 Aug 2021

@NavyLCDR

Thanks. Your suggestion worked just fine.

Some tips for the next person with this problem.

Run a backup first with bcdedit /export.
Get a text file capture of the bcdedit output, e.g. bcdedit > /C:bcd.txt

When you do the actual delete operations, it's easy to the identifiers from that text file,

SoFine409 · 31 Aug 2021

x509 said:

@NavyLCDR

Thanks. Your suggestion worked just fine.

Some tips for the next person with this problem.

Run a backup first with bcdedit /export.
Get a text file capture of the bcdedit output, e.g. bcdedit > /C:bcd.txt

When you do the actual delete operations, it's easy to the identifiers from that text file,

Good tip. In the past I’ve just copy/pasted into notepad.

NavyLCDR · 01 Sep 2021

You can also just highlight and copy the identifiers directly in the command prompt window and then paste it after the bcdedit /delete command.

x509 · 11 Oct 2021

NavyLCDR said:

You can also just highlight and copy the identifiers directly in the command prompt window and then paste it after the bcdedit /delete command.

Those unwanted Boot Manager entries just showed up again in my Classib Boot Menu.

Is some obscure Windows process regenerating those entries?

SIW2 · 12 Oct 2021

Code:

@echo off
bcdedit -enum -v >bcdinfo.txt
echo.
echo OSGUID                                    Description >bcdosguids.txt
echo.
for /f "tokens=1,2,3,4,5,6,7,8,9 delims= " %%i in (bcdinfo.txt) do (
IF /I "%%i"=="Identifier" set/p=%%j<nul >>bcdosguids.txt
IF /I "%%i"=="description" echo     %%j %%k %%l %%m %%n %%o>>bcdosguids.txt
)
notepad bcdosguids.txt
:: or
:: Type bcdosguids.txt
:: pause