EasyBCD - menu ordering bug - firmware items displayed (but not manageable) - v2.3.0.207

#1
I've just tried to use your tool to (only) change the ordering of my boot items (- nothing more than that), and it has ended-up adding 'firmware application' items, that are now been displayed, but are not manageable (/visible) using MsConfig.

BCDEdit displays them. Now I don't know if I can delete them or whether they were always there but (somehow) hidden from view (or not "ACTIVE" ?!?).

I have Windows 10 Pro Anniversary Edition (- with Developer features enabled), and it's a custom-build laptop:

I seem to have two entries for my Killer NIC & two probably for my WSL (Windows Subsystem for Linux) instance of Ubuntu. Here's my BCDEdit output:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume5
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
displayorder {068aaf6b-f62f-11e6-89a5-806e6f6e6963}
{068aaf6c-f62f-11e6-89a5-806e6f6e6963}
{1292f450-7839-11e6-b435-d6d1d4e923da}
{1292f451-7839-11e6-b435-d6d1d4e923da}
{current}
{3df0ac28-fc69-11e7-be37-db0da1cd690a}
{3df0ac25-fc69-11e7-be37-db0da1cd690a}
{3df0ac26-fc69-11e7-be37-db0da1cd690a}
{3df0ac24-fc69-11e7-be37-db0da1cd690a}
toolsdisplayorder {memdiag}
timeout 36

Firmware Application (101fffff)
-------------------------------
identifier {068aaf6b-f62f-11e6-89a5-806e6f6e6963}
device partition=\Device\HarddiskVolume5
path \EFI\UBUNTU\SHIMX64.EFI
description ubuntu
custom:250000c2 1

Firmware Application (101fffff)
-------------------------------
identifier {068aaf6c-f62f-11e6-89a5-806e6f6e6963}
device partition=\Device\HarddiskVolume5
path \EFI\UBUNTU\GRUBX64.EFI
description ubuntu
custom:250000c2 1

Firmware Application (101fffff)
-------------------------------
identifier {1292f450-7839-11e6-b435-d6d1d4e923da}
description UEFI: IP4 Killer PCIe Network Controller
badmemoryaccess Yes
custom:250000c2 1

Firmware Application (101fffff)
-------------------------------
identifier {1292f451-7839-11e6-b435-d6d1d4e923da}
description UEFI: IP6 Killer PCIe Network Controller
badmemoryaccess Yes
custom:250000c2 1

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {3df0ac22-fc69-11e7-be37-db0da1cd690a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

Windows Boot Loader
-------------------
identifier {3df0ac28-fc69-11e7-be37-db0da1cd690a}
device partition=C:
path \WINDOWS\system32\winload.efi
description No HyperV
locale en-GB
inherit {bootloadersettings}
recoverysequence {3df0ac22-fc69-11e7-be37-db0da1cd690a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off

Windows Boot Loader
-------------------
identifier {3df0ac25-fc69-11e7-be37-db0da1cd690a}
device partition=C:
path \WINDOWS\system32\winload.efi
description Safe Mode with Networking
locale en-GB
inherit {bootloadersettings}
recoverysequence {3df0ac22-fc69-11e7-be37-db0da1cd690a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

Windows Boot Loader
-------------------
identifier {3df0ac26-fc69-11e7-be37-db0da1cd690a}
device partition=C:
path \WINDOWS\system32\winload.efi
description Safe Mode with Command Prompt
locale en-GB
inherit {bootloadersettings}
recoverysequence {3df0ac22-fc69-11e7-be37-db0da1cd690a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

Windows Boot Loader
-------------------
identifier {3df0ac24-fc69-11e7-be37-db0da1cd690a}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10 Safe Mode
locale en-GB
inherit {bootloadersettings}
recoverysequence {3df0ac22-fc69-11e7-be37-db0da1cd690a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {3df0ac20-fc69-11e7-be37-db0da1cd690a}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

I don't believe BCDEdit was displaying any firmware-applications before (- unless one was displayed and I missed it, but certainly none were been displayed upon the Boot menu upon booting-up).


(A recent re-install of Windows 10 caused drive D to be recognised as now been Disk-0 & drive C now been Disk-1 - it seemed to switch them, not sure if that's anything to do with it / whether your software is assuming that drive C is always Disk-0?)
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#2
EasyBCD doesn't make any assumptions about your disk letters, it just reads them from your registry, and reflects what Windows calls everything.
All that apparent junk in your boot menu is a function of UEFI, nothing to do with EasyBCD either.
Whatever you do, don't try to "clean it up". Not if you still want your PC to boot.
EasyBCD does cosmetically clean it for you. If you look in "view settings" under detailed mode, you'll find it all like you do with bcdedit, but overview mode ignores it all and just displays your OS options.
 

mqudsi

Mostly Harmless
Staff member
#3
1519697757960.png

Make sure "Expert Mode" is unchecked (default state) to keep these entries hidden.