Configure Boot or Add/Remove Entries= crash on Vista

Thanks for this great little app that works brilliantly on my desktop:grinning:. My problem is that everytime I open EasyBCD on my Laptop & click on Configure Boot or Add/Remove Entries, it crashes.

I am using a HP laptop with Vista Business installed & using EasyBCD 1.6. I've tried using 1.61 and an earlier version of EasyBCD and get the same problem. With 1.6 & 1.61, after the crash it asks me to send off and error report which is what I do. With the earlier version I get the following error information:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: item
   at System.Windows.Forms.ComboBox.ObjectCollection.AddInternal(Object item)
   at System.Windows.Forms.ComboBox.ObjectCollection.Add(Object item)
   at EasyBCD.TabRules.Tab1()
   at EasyBCD.EasyBCD.ConfigureBCD_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.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.OnMessage(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 **************
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    Assembly Version: 1.52.2550.18717
    Win32 Version: 1.52
    CodeBase: file:///C:/Program%20Files/NeoSmart%20Technologies/EasyBCD/EasyBCD.exe
    Assembly Version:
    Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/
    Assembly Version:
    Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the section.
The application must also be compiled with debugging
For example:
    < jitDebugging="true" />
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Any ideas what is going on here?


Hi again,
Just tried 'VistaBootPro' and get exactly the same problem when I press 'manage os entries' or 'advanced configuration'. Searching around people, who are reporting similar problems, nearly always seem to be using a laptop computer from one of the major manufacturers like HP.:??

I've managed to get the dual boot working using bcdedit.exe directly but would love to know what the problem is that's stopping editor programs working. So here's hoping someone much smarter than me can eventually shed some light.:grinning:


Hi Mick, welcome to NeoSmart Technologies.

Can you please run "bcdedit.exe" in the command line and paste the output here? It would be a world of help.

Thanks :smile:
That bug should have been fixed in the latest builds, but it does sound similar...

I should be able to pin it down if I get the output of bcdedit.exe.
Sorry I've taken so long to get back to you, I've been away for a couple of days. Here's what I get when I run bcdedit.exe:

C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bcdedit
Windows Boot Manager
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {3fb6bf64-700d-11db-8409-0016d303c867}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 3
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
recoverysequence {572bcd55-ffa7-11d9-aae2-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {3fb6bf64-700d-11db-8409-0016d303c867}
nx OptIn
Windows Boot Loader
identifier {572bcd55-ffa7-11d9-aae2-0007e994107d}
Windows Legacy OS Loader
identifier {ntldr}
device partition=C:
path \ntldr
description Windows XP

Hope this helps.

Thanks very much for the help.

Last edited by a moderator:
Got it :smile:

Bug found - should be fixed in the next build we upload :smile:

Thanks for getting back to me - and no worries about the delay :smile: