Unhandled exception in WyUpdate

Hi - my app launches wyUpdate.exe (which runs if newer version found) and has all files getting updated correctly. WyUpdate.exe is the current (2.6.18.4 from 2012) release.

During the update process, users get 3 prompts and a .NET error occurs between 2nd and 3rd. Properties are set to use .NET 4. The prompts are:

Prompt 1 - Close Processes... (no problem here)Prompt 2 - Files in Use... (it would be nice to suppress this if Prompt 1 is confirmed)Error Message - Microsoft .NET Framework (see below for details)Prompt 3 Update Successful (if I clicking continue on error msg)

Here is the full Error Message and I have screen capture if needed:

Unhandled exception has occurred in your application. If you click Continue......Cannot access a disposed object.Object name: 'List Box'.

Details:

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

************** Exception Text **************System.ObjectDisposedException: Cannot access a disposed object.Object name: 'ListBox'. at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.Control.get_Handle() at System.Windows.Forms.Control.CreateGraphicsInternal() at System.Windows.Forms.ListBox.UpdateMaxItemWidth(Object item, Boolean removing) at System.Windows.Forms.ListBox.ObjectCollection.ClearInternal() <b>at wyUpdate.frmFilesInUse.UpdateList()</b> 🤔

************** Loaded Assemblies **************mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll----------------------------------------wyUpdate Assembly Version: 2.6.18.4 Win32 Version: 2.6.18.4 CodeBase: file:///[Path to our app]/wyUpdate.exe----------------------------------------System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------System.ServiceProcess Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll----------------------------------------

************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.

For example:

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

When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.

So.. anything suggestions?

Well, this crash will be fixed in the next version (the fix is already in the repository). This is a race condition bug that will only pop-up in the "right" (or wrong) circumstances.

In the meantime, my advice, close all apps & files that will be updated before you actually start updating.