Unhandled Exception error / GRUB ...

T

temple

Member
Hi there,
I searched the forums prior to posting this - but didn't find anything - so bear with me if this was already answered. I am running Vista with Unbuntu installed on a different partition. Vista loads fine, but when I add the Linux entry, choose the correct partition that it's installed on and check "GRUB isn't installed to the bootsector" I receive an unhandled exception error. I also seem to receive this error if I choose to Install NEOGrub. Any thoughts on this? Error pasted below...


************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: path
at System.IO.File.CreateText(String path)
at ..()
at ..()
at ..(String )
at ..?(Object , EventArgs )
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 **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
EasyBCD
Assembly Version: 1.7.1.6
Win32 Version: 1.7.1.6
CodeBase: file:///C:/Program Files/NeoSmart Technologies/EasyBCD/EasyBCD.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSI...0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSI....0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSI..._b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSI....0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
msfeeds
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/msfeeds/1.0.0.0__7df935e7b230192c/msfeeds.dll
----------------------------------------
 
Hey temple, welcome to NST.

Can you paste the output of EasyBCD | Diagnostics Center | Copy Debug Data?
 
Thanks for taking a look - here's the paste from the debug...

Code: 
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {f5211655-c86e-11dc-b564-001a6b7d100e}
resumeobject            {c9c0cf57-c870-11dc-a200-806e6f6e6963}
displayorder            {f5211655-c86e-11dc-b564-001a6b7d100e}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
Windows Boot Loader
-------------------
identifier              {f5211655-c86e-11dc-b564-001a6b7d100e}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows Vista
osdevice                partition=C:
systemroot              \Windows
resumeobject            {c9c0cf57-c870-11dc-a200-806e6f6e6963}
 
Aha..

This should fix it:
EasyBCD | Useful Utilities | Power Console:
Code: 
bcdedit.exe /set {9dea862c-5cdd-4e70-acc1-f32b344d4795} device boot
bcdedit.exe /set {9dea862c-5cdd-4e70-acc1-f32b344d4795} osdevice boot
exit

Then restart EasyBCD.

For some reason your Vista bootloader's configuration has no idea what drive to boot from... This should fix that.

Please let me know how it goes.. I'll add a check in the next version of EasyBCD as well.
 
Thanks for the quick reply! The first command seems to take, but the second provides an error. Here's the text...


C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bcdedit.exe /set {9dea862c-5c
dd-4e70-acc1-f32b344d4795} device boot
The operation completed successfully.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bcdedit.exe /set {9dea862c-5c
dd-4e70-acc1-f32b344d4795} osdevice boot
The element data type specified is not recognized, or does not apply to the
specified entry.
Run "bcdedit /?" for command line assistance.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>
 
hmm - okay - I end up with the same result it seems. After a reboot it goes right back into Vista with no options. Here's the latest debug...

Code: 
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  boot
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {f5211655-c86e-11dc-b564-001a6b7d100e}
resumeobject            {c9c0cf57-c870-11dc-a200-806e6f6e6963}
displayorder            {f5211655-c86e-11dc-b564-001a6b7d100e}
                        {f5211658-c86e-11dc-b564-001a6b7d100e}
bootsequence            {f5211658-c86e-11dc-b564-001a6b7d100e}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
Windows Boot Loader
-------------------
identifier              {f5211655-c86e-11dc-b564-001a6b7d100e}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows Vista
osdevice                partition=C:
systemroot              \Windows
resumeobject            {c9c0cf57-c870-11dc-a200-806e6f6e6963}
Real-mode Boot Sector
---------------------
identifier              {f5211658-c86e-11dc-b564-001a6b7d100e}
path                    \NST\NeoGrub.mbr
description             Ubuntu Linux
 
I don't recall ever taking any action like that - it's possible though! Should I remove neogrub, and the entry and then re-add them?
 
When you added the Linux entry, EasyBCD added the NeoGrub install for you.

The question is, did you add the Linux entry before or after you issued the bcdedit.exe commands above?
 
Execute this as well:
Code: 
bcdedit.exe /set {f5211658-c86e-11dc-b564-001a6b7d100e} device partition=C:
 
Back
Top