Launchbox/BigBox not running after update

[44am]

Hi all,

Am a lifetime license user. Updated to the latest version of LB (13.22 the latest version showing in Launchbox/Updates) but now the program simply won't start.

Checked in Task Manager - the Launchbox icon shows, then appears to be running two tasks - shows as Launchbox (2) - then both close with no further action.

Have tried copying an old version of Settings.xml from Backups folder to Data folder but to no avail. FWIW BigBox won't launch either.

All running from a local drive - no network involved. Any advice/help appreciated.

Edited 19 hours ago by 44am

[C-Beats]

Can check Windows Event Viewer and see if in the application logs if there an error pointing to LB. Should say ".NET Runtime Error". There will be two, one just saying it crashed, and the other with the error. If you can post up that error it'd be easier to track down the cause.

[44am]

Thanks for the reply, C-Beats. Have located WEV and app logs, but unsure where to go from there.

Where specifically would I find events pertaining to Launchbox?

[C-Beats]

2 hours ago, 44am said:

Thanks for the reply, C-Beats. Have located WEV and app logs, but unsure where to go from there.

Where specifically would I find events pertaining to Launchbox?

In WEV if a an error is thrown it'll say LB was the failing app, then the error stack trace would help determine what is actually happening.

[44am]

Thank you. This is what I see. 

 

[C-Beats]

1 minute ago, 44am said:

Thank you. This is what I see. 

 

On the left you want to click Windows Logs so it opens up, then press application like so...

[44am]

Thanks C-B. So, it appears I have a few!

 

Hope that helps...

[C-Beats]

Looking for logs that look like the third one. Looks like you have some missing DLLs. You may have a AV quarantining things willy nilly. Try and run the installer on your folder again and see if it can put em back. Make sure when you do so the installed isn't pointing to \\LaunchBox\LaunchBox like it likes to do when you do that.

[44am]

I ran the 13.22 installer again as per your suggestion and that appears to have done the trick. 

All operational once again. Thanks again for your help, C-B. 👍