Unhandled exception has occurred after last update

Ristogod · Jul 19, 2009, 05:13 AM

The last time I run Live Update.Net I got some crazy errors.

Now when I try to run Driver Cleaner I get this:

Code:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.BadImageFormatException: Could not load file or assembly 'DCLibrary, Version=2.0.3434.39773, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'DCLibrary, Version=2.0.3434.39773, Culture=neutral, PublicKeyToken=null'
   at DriverCleanerDotNET.frmMain.45xnchVGu(Object , EventArgs )
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.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)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
DriverCleanerDotNET
    Assembly Version: 2.0.3486.15079
    Win32 Version: 3.4.1.0
    CodeBase: file:///C:/Program%20Files%20(x86)/DriverCleanerDotNET/DriverCleanerDotNET.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    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.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    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.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** 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 system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

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.

Then when I click continue, the cleaning selection of the tool is empty:

I am running on Vista x64 Ultimate.

Ristogod · Jul 19, 2009, 05:25 AM

I uninstalled the application and reinstalled. I ran Live Update again, and here is the error I get while trying to update.

Code:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'DCLibrary, Version=2.0.3333.16575, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'DCLibrary, Version=2.0.3333.16575, Culture=neutral, PublicKeyToken=null'
   at ReplaceDotNET.frmMain.Bw8lq4eB3(Object , EventArgs )
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.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)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
ReplaceDotNET
    Assembly Version: 2.0.3486.15241
    Win32 Version: 3.2.2.0
    CodeBase: file:///C:/Program%20Files%20(x86)/DriverCleanerDotNET/ReplaceDotNET.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    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.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    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.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** 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 system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

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.

**Spike** · Jul 19, 2009, 08:46 AM

It looks like something didn't go right in the update process. What you can do is download the latest installer from the link in the email with the registration info and see if that full installer fixes it.

xxJackxx · Jul 19, 2009, 06:20 PM

I am having the same problem. Looks like DCLibrary.dll is corrupt in the update. I downloaded the full install from the link in my email and that seems to have fixed it.

OnTheRocks · Jul 19, 2009, 07:32 PM

Same problem here also.

**Spike** · Jul 19, 2009, 08:17 PM

Just a small update, i have reverted back to 3.4.0.0 for now to have some more time to look into this problem and the other unhandled exception. So please use the download link in the email to get the 3.4 version and that should work.

Sorry for the inconvenience.

OnTheRocks · Jul 19, 2009, 09:33 PM

Thank You Spike,
For the download link.Works great now,even after I ran and installed two updates.

Galizzi Giampiero · Jul 20, 2009, 09:41 AM

Quote:

Originally Posted by Spike

Just a small update, i have reverted back to 3.4.0.0 for now to have some more time to look into this problem and the other unhandled exception. So please use the download link in the email to get the 3.4 version and that should work.

Sorry for the inconvenience.

I have the same problem, exactly as described in the first post.
Please, can I have a download link where to find the version 3.4 of the program or the latest one?

Regards

EarlZ · Jul 20, 2009, 12:29 PM

Im getting the very same error with the latest version, reverting to version 3.4.0 solved that issue but my fonts on the program are all messed up.. probably a corruption on my installer.. where can i download a fresh and error free 3.4.0 ?

**Spike** · Jul 20, 2009, 04:46 PM

You can use the link in the email that was send when purchased. In case you don't have the email anymore just send me an email or pm with the name and email used to purchase and i will resend the email with the details.

EarlZ · Jul 21, 2009, 04:37 AM

Im just configuring this system for a friend who left me a copy if his tools, i guess ill let him sort this out instead. thanks

Rainey · Nov 1, 2009, 12:23 AM

I get the same problem after i clean it list the file cleaned then i get this error and i click continue and i have to close the program as everything in it is dead.

If i check the advance checkbox then click the scan button then i get this error right off the bat and have to clost the app as everything is dead.

Rainey

**Spike** · Nov 5, 2009, 07:30 AM

Rainey what version of the program are you using?

Jul 19, 2009, 08:46 AM	#3
Spike Driver Cleaner Maker Join Date: Jul 2002 Location: Netherlands Posts: 2,088 Rep Power: 70 System Specs	Re: Unhandled exception has occurred after last update It looks like something didn't go right in the update process. What you can do is download the latest installer from the link in the email with the registration info and see if that full installer fixes it. __________________

Jul 19, 2009, 06:20 PM	#4
xxJackxx HardwareHeaven Newbie Join Date: Jul 2009 Location: Midwest Posts: 11 Rep Power: 0 System Specs	Re: Unhandled exception has occurred after last update I am having the same problem. Looks like DCLibrary.dll is corrupt in the update. I downloaded the full install from the link in my email and that seems to have fixed it.

Jul 19, 2009, 07:32 PM	#5
OnTheRocks DriverHeaven Newbie Join Date: Jul 2009 Location: Central New York State Posts: 2 Rep Power: 0 System Specs	Re: Unhandled exception has occurred after last update Same problem here also.

Jul 19, 2009, 08:17 PM	#6
Spike Driver Cleaner Maker Join Date: Jul 2002 Location: Netherlands Posts: 2,088 Rep Power: 70 System Specs	Re: Unhandled exception has occurred after last update Just a small update, i have reverted back to 3.4.0.0 for now to have some more time to look into this problem and the other unhandled exception. So please use the download link in the email to get the 3.4 version and that should work. Sorry for the inconvenience. __________________

Jul 19, 2009, 09:33 PM	#7
OnTheRocks DriverHeaven Newbie Join Date: Jul 2009 Location: Central New York State Posts: 2 Rep Power: 0 System Specs	Re: Unhandled exception has occurred after last update Thank You Spike, For the download link.Works great now,even after I ran and installed two updates.

Jul 20, 2009, 12:29 PM	#9
EarlZ DriverHeaven Newbie Join Date: Jul 2009 Posts: 2 Rep Power: 0	Re: Unhandled exception has occurred after last update Im getting the very same error with the latest version, reverting to version 3.4.0 solved that issue but my fonts on the program are all messed up.. probably a corruption on my installer.. where can i download a fresh and error free 3.4.0 ?

Jul 20, 2009, 04:46 PM	#10
Spike Driver Cleaner Maker Join Date: Jul 2002 Location: Netherlands Posts: 2,088 Rep Power: 70 System Specs	Re: Unhandled exception has occurred after last update You can use the link in the email that was send when purchased. In case you don't have the email anymore just send me an email or pm with the name and email used to purchase and i will resend the email with the details. __________________

Jul 21, 2009, 04:37 AM	#11
EarlZ DriverHeaven Newbie Join Date: Jul 2009 Posts: 2 Rep Power: 0	Re: Unhandled exception has occurred after last update Im just configuring this system for a friend who left me a copy if his tools, i guess ill let him sort this out instead. thanks

Nov 1, 2009, 12:23 AM	#12
Rainey DriverHeaven Newbie Join Date: Oct 2009 Posts: 1 Rep Power: 0	Re: Unhandled exception has occurred after last update I get the same problem after i clean it list the file cleaned then i get this error and i click continue and i have to close the program as everything in it is dead. If i check the advance checkbox then click the scan button then i get this error right off the bat and have to clost the app as everything is dead. Rainey

Nov 5, 2009, 07:30 AM	#13
Spike Driver Cleaner Maker Join Date: Jul 2002 Location: Netherlands Posts: 2,088 Rep Power: 70 System Specs	Re: Unhandled exception has occurred after last update Rainey what version of the program are you using? __________________