Multiple efi partitions in boot manager

IanHHH

New Member
I am multibooting 3 drives (1 Win10 and 2 Win11) the boot manager on one win11 drive is selected in bios. It works but in addition to the named drives it also lists the three efi partitions which are unbootable -of course. I am not sure why they are there and they are a nuisance. How can I remove them from the boot manager? In bcdedit they show up as"firmware application"

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Migrating from Windows PowerShell 5.1 to PowerShell 7 - PowerShell

PS C:\Users\ihodg> bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume7
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {50afb8ea-9afd-11ee-bf01-ac220bdcf0be}
displayorder {ddd875c8-9a44-11ee-beff-806e6f6e6963}
{50afb8ee-9afd-11ee-bf01-ac220bdcf0be}
{f7e81b28-98be-11ee-befb-806e6f6e6963}
{current}
{50afb8ed-9afd-11ee-bf01-ac220bdcf0be}
{50afb8eb-9afd-11ee-bf01-ac220bdcf0be}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {ddd875c8-9a44-11ee-beff-806e6f6e6963}
device partition=\Device\HarddiskVolume5
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
custom:250000c2 1

Firmware Application (101fffff)
-------------------------------
identifier {50afb8ee-9afd-11ee-bf01-ac220bdcf0be}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
custom:250000c2 1

Firmware Application (101fffff)
-------------------------------
identifier {f7e81b28-98be-11ee-befb-806e6f6e6963}
description Hard Drive
custom:250000c2 1

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Work
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {4296dc80-9955-11ee-befc-d22bfb1a9cab}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {50afb8ed-9afd-11ee-bf01-ac220bdcf0be}
device partition=E:
path \Windows\system32\winload.efi
description Games2
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=E:
systemroot \Windows
resumeobject {50afb8ec-9afd-11ee-bf01-ac220bdcf0be}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {50afb8eb-9afd-11ee-bf01-ac220bdcf0be}
device partition=D:
path \Windows\system32\winload.efi
description Games
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \Windows
resumeobject {50afb8ea-9afd-11ee-bf01-ac220bdcf0be}
nx OptIn
bootmenupolicy Standard
PS C:\Users\ihodg>

Thanks.
 
I'm assuming that each of these disk had windows setup on them while being the only disk in the system at the time of install? Under that condition you would then have 3 EFI partitions as well as the current 3 boot manger entries. You should simply be able to delete the EFI partitions on the other devices. You will want to be careful to not delete the one on Vol7.

BCD and many parts of Windows index volumes from 1 while diskpart starts it's index from 0. So you would need to figure out what disk Vol7 is on and remove the other EFI parts. Do so at your own risk though. Messing with the boot process is non-trivial and you could easily put the system in a non functioning state. Also be aware if the EFI partitions are at the beginning of the disk you won't be able to reclaim that space with a native windows tool. You would need to boot offline to move the other partitions.
 
Back
Top