Launchbox crash at startup

Issue #7825 invalid
Steve Trice created an issue

Common Language Runtime detected an invalid program.

App: LaunchBox
Version: 13.5
Type: System.InvalidProgramException
Site: Void RestartFailurePublisher(System.Object, System.Net.DownloadStringCompletedEventArgs)
Source: LaunchBox

at Unbroken.LaunchBox.Windows.Desktop.ViewModels.MainViewModel.<>c__DisplayClass320_0.RestartFailurePublisher(Object sender, DownloadStringCompletedEventArgs args)
at System.Net.WebClient.OnDownloadStringCompleted(DownloadStringCompletedEventArgs e)
at System.Net.WebClient.<StartAsyncOperation>b__78_2(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Recent Log:

16:46:39 Exception

Comments (4)

  1. Steve Trice reporter

    Hi I have only downloaded software from your website and I purchased a lifetime license to Launchbox in November 2019, so I believe I have a legitimate copy of the software. I trust the email attached will confirm this. I do have Launchbox installed on a couple of machines, but have never shared with any friends etc. I believe in supporting developers whenever I can.

    I don't recall having a significant issue with the software until this one time crash, so hoped reporting the problem would help. If there's any more information I can provide, let me know. Steve

  2. Christian

    You can reach out to support@unbrokensoftware.com and get a clean link to our installer then download there and compare with the hash of the file and ensure they match. If they don’t match you have something corrupting your file system, if they do you can use the installer over the existing and see if that corrects your issue. This error only has popped up when a dll/exe in the core folder doesn’t match the hash of an officially released library/executable and so we’d need to confirm whether that’s the case or not in this.

  3. Log in to comment