EasyBCD 2.0.0.87 menu item delete error

#1
While trying to delete the following Win7 BDC 'unnamed entry' menu item an unhandled exception is always received.

---------------------------------------------------------------
Windows Boot Loader
-------------------
identifier {fe9c4b57-1b9a-11df-83a5-ef79c2757880}
A device attached to the system is not functioning.
---------------------------------------------------------------


************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at (String id)
at (Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
EasyBCD
Assembly Version: 2.0.0.87
Win32 Version: 2.0.0.87
CodeBase: file:///C:/Program%20Files%20(x86)/NeoSmart%20Technologies/EasyBCD/EasyBCD.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase:

file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase:

file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
{208a551e-ab9f-40cd-9b65-a7f5fea1d089}
Assembly Version: 0.0.0.0
Win32 Version: 2.0.0.87
CodeBase: file:///C:/Program%20Files%20(x86)/NeoSmart%20Technologies/EasyBCD/EasyBCD.exe
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase:

file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
 

mqudsi

Mostly Harmless
Staff member
#3
Do you mean an entry named "unnamed entry" or literally an unnamed entry?
 

JustinW

Super Moderator
Staff member
#4
I still can't produce a problem. Tried adding an empty named entry and deleted, added a "unamed entry" and deleted... still no exception. You might want to fix it in future builds to not allow entries with empty descriptions. Guess we'll haft to wait for Sofarider to post the requested info.
 
#5
I've been trying to delete an entry named "unnamed entry", which showed up when moving to build 86, probably due to a moved boot.wim file referenced by that entry.

-----------------------------------

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {fe9c4b4c-1b9a-11df-83a5-ef79c2757880}
resumeobject {dfb66634-1ba3-11df-90e0-806e6f6e6963}
displayorder {fe9c4b4c-1b9a-11df-83a5-ef79c2757880}
{fe9c4b59-1b9a-11df-83a5-ef79c2757880}
{fe9c4b5a-1b9a-11df-83a5-ef79c2757880}
{fe9c4b5d-1b9a-11df-83a5-ef79c2757880}
{fe9c4b5f-1b9a-11df-83a5-ef79c2757880}
{fe9c4b55-1b9a-11df-83a5-ef79c2757880}
{fe9c4b51-1b9a-11df-83a5-ef79c2757880}
{fe9c4b57-1b9a-11df-83a5-ef79c2757880}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 5

Windows Boot Loader
-------------------
identifier {fe9c4b4c-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \Windows\system32\winload.exe
description Win 7 Home Premium 64
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {dfb66634-1ba3-11df-90e0-806e6f6e6963}
nx OptOut

Real-mode Boot Sector
---------------------
identifier {fe9c4b59-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description Ubuntu 9.10 64

Real-mode Boot Sector
---------------------
identifier {fe9c4b5a-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \NST\AutoNeoGrub4.mbr
description Reflect Recovery WinPE 2.1.2525

Real-mode Boot Sector
---------------------
identifier {fe9c4b5d-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \NST\AutoNeoGrub1.mbr
description Win PE 3.0

Windows Boot Loader
-------------------
identifier {fe9c4b5f-1b9a-11df-83a5-ef79c2757880}
device ramdisk=[F:]\iso's\Win7repair\boot.wim,{fe9c4b5e-1b9a-11df-83a5-ef79c2757880}
path \Windows\System32\Boot\winload.exe
description Win 7 repair
locale en-US
osdevice ramdisk=[F:]\iso's\Win7repair\boot.wim,{fe9c4b5e-1b9a-11df-83a5-ef79c2757880}
systemroot \Windows
detecthal Yes
winpe Yes
ems Yes

Real-mode Boot Sector
---------------------
identifier {fe9c4b55-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \NST\AutoNeoGrub3.mbr
description Hiren's BootCD 10.1

Real-mode Boot Sector
---------------------
identifier {fe9c4b51-1b9a-11df-83a5-ef79c2757880}
device partition=C:
path \NST\NeoGrub.mbr
description NeoGrub Bootloader

Windows Boot Loader
-------------------
identifier {fe9c4b57-1b9a-11df-83a5-ef79c2757880}
A device attached to the system is not functioning.


 

Attachments

JustinW

Super Moderator
Staff member
#6
Ok, I was going to wait for CG's input but he's offline, so...

Only way I can think of getting rid of this entry via EasyBCD then is by resetting the BCD configuration:
BCD Install/Repair > Reset BCD Configuration > Perform Action

Of course this would also wipe out your extra entries in the process. You would need to re-add those.

Alterntively, you can use bcdedit to get rid of the entry:
Useful Utilities > EasyBCD Power Console: bcdedit /delete {fe9c4b57-1b9a-11df-83a5-ef79c2757880}

Most likely you'll need to restart EasyBCD to see the changes, or you can confirm it is gone by typing "bcdedit".

Addendum:

I've been trying to delete an entry named "unnamed entry", which showed up when moving to build 86
Bingo. Before you resort to my other instructions please give build 87 a try. Its available [thread=642]here[/thread]. That build work without exception?
 
Last edited:
#7
I am getting the exception with build 87. I'll try deleting the entry with bcdedit.

Addendum:

And I was able to successfully delete the entry using bcdedit. Thanks for the proper syntax which saved me some research time.
 
Last edited:

JustinW

Super Moderator
Staff member
#8
Well, I'm glad the entrys gone. Problem is we still don't know what was causing the error deleting it. Besides moving to the latest build was there anything you changed (like adding that entry for example?) or did it just show up on its own?
 
#9
Did I mention there was a hard drive upgrade in between builds 82 and 86? :wtf:

Using Macrium Reflect I restored everything to the new drive including the MBR and everything worked great. When upgrading EasyBCD 2 b82 to 86 I noticed the one menu entry, 'Win 7 repair', referencing boot.wim, had gotten hosed.
 

mqudsi

Mostly Harmless
Staff member
#10
Ah, that explains things :smile: