Clicking DeFogger button throws an unhandled exception
Reported by Steve | March 15th, 2011 @ 12:37 PM | in 0.9.0 (closed)
Clicking the button opens the following error message:
Unhandled exception has occurred in your application. If you click Continue....blah
%1 is not a valid Win32 application.
Details below:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
Exception
Text
System.ComponentModel.Win32Exception: %1 is not a valid Win32
application
at
System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo
startInfo) at System.Diagnostics.Process.Start() at
System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at
System.Diagnostics.Process.Start(String fileName) at
SetupAssistant.Form1.runFromCacheOrDownload(String filename, String
url) at SetupAssistant.Form1.button76_Click_1(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
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3615 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
SetupAssistant
Assembly Version: 0.8.4090.40294
Win32 Version: 0.8.*
CodeBase: file:///C:/Documents%20and%20Settings/Steve/Desktop/SetupAssistant.exe
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3614 (GDR.050727-3600)
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.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.1 built by: SP
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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:
<system.windows.forms 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.
Comments and changes to this ticket
-
Luke Maciak March 15th, 2011 @ 11:11 PM
- State changed from new to open
- Milestone set to 0.9.0
- Assigned user set to Luke Maciak
- Milestone order changed from 1 to 0
Thanks. This could be a download issue, but I definitely should handle that exception being thrown.
Couldn't replicate this on my system but I will try again.
Could you provide some additional info:
What Windows version were you using? XP, Vista, Win7?
What version of .NET do you have installed?Have you tried clearing the cache in the Misc tab and trying this again?
In either case I'm not handling the exception properly. Will get that fixed.
-
Luke Maciak March 15th, 2011 @ 11:12 PM
- Title changed from DeFogger to Clicking DeFogger button throws an unhandled exception
-
Luke Maciak March 15th, 2011 @ 11:20 PM
- Tag set to exception handling
-
Steve March 16th, 2011 @ 07:36 AM
Am using Windows XP SP3 with .NET 3.5 SP1. Yes, cache was cleared. I can test using .NET 4 if you want.
-
Luke Maciak April 5th, 2011 @ 04:29 PM
- State changed from open to resolved
Added exception handling code. If a cached app crashes, exception will be caught and user will be asked if she wants to clear cache.
This fix will be in 0.9
-
Luke Maciak January 11th, 2012 @ 10:39 AM
- Tag changed from exception handling to bug
-
Luke Maciak August 14th, 2013 @ 08:29 PM
(from [462d715ef3d9]) Added AdwCleaner. Fixes #12
https://bitbucket.org/maciakl/lukes-setup-assistant/changeset/462d7...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The Ultimate Configuration and Diagnostics Tool