Not Launching

Issue #5690 new
Jono Robert created an issue

App: LaunchBox
Version: 11.6
Type: System.IO.IOException
Site: Void Lbocpx3uPd(System.Object, System.Object)
Source: Unbroken.LaunchBox.Windows

at Unbroken.LaunchBox.Windows.Data.DataManager.Lbocpx3uPd(Object , Object )
at ofBueBuFxQfdDsLfZOI.FQwqYTgBS(DataSet , String , ofBueBuFxQfdDsLfZOI )
at Unbroken.LaunchBox.Windows.Data.DataManager.Xp8c8KuZHx(String )
at AHqcM3ClIsoaGPY4GlJ.FQwqYTgBS(Object , String value, AHqcM3ClIsoaGPY4GlJ )
at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass173_0.UxLSVfxgkUK()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Recent Log:

3:57:53 PM Exception

โ€Œ

Wont boot application ๐Ÿ˜ž

Comments (5)

  1. Christian

    Could you try running the installer in a different location and see if it works there? Typically we see IO errors when permission on a folder is wonky or a drive is failing. Would be nice to rule out it was the location causing the error and not the application itself. I will look into the code and see if there anything we can do from there.

    Thanks for the report.

  2. Jono Robert reporter

    Launched fine when installed in a different location on the same drive. Any chance of copying my data across? Or i have to start again?

    Cheers so much for getting back.

    โ€Œ

  3. Christian

    Would depend on where the roms were relative to the locations. You can copy over the Data, Images, and Video folder from the previous install to the new one but the rom paths may not be right when doing so.

  4. Jason Carr repo owner

    Hi Jono, you might want to run chkdsk to make sure that you donโ€™t have any drive failing issues. Otherwise, it could be a file permissions issue.

  5. Log in to comment