Jump to content
LaunchBox Community Forums
anickname

Launchbox, BigBox, Launchbox.Next crashes with latest version

Recommended Posts

Hello,

it seems that all the executables are crashing with the latest versions.

I am using Windows 10 Enterprise LTSB 1607 and running from a network share.

With version 7.x it ran without problems.

I have tested also on Windows 10 Pro 1709 and seems to work fine (also from network share).

Any suggestions ?

Thank you.

 

Edited by anickname

Share this post


Link to post
Share on other sites

Hi @anickname, I'm sorry to hear about the trouble. The only thing I can figure is that maybe 1607 has issues with the latest version of the .NET framework. We're on the very latest version of the framework in order to take advantage of the latest performance improvements. I know there have been some issues in the past for people who haven't kept up to date. It also looks like Microsoft has ended support for version 1607, so that could explain the issues with the framework.

Share this post


Link to post
Share on other sites

No that isn't it 1607 commercial support ended yesterday (so would still have the latest .net framework) and enterprise is still getting supported for a while longer.

Share this post


Link to post
Share on other sites

As stated here:

https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet

the support for Windows 10 Enterprise 2016 LTSB ends on October 13, 2026, so this should not be the case.

I installed, a clean version (8.2) with no games.

The one that is run from the network share (mapped drive), crashes.

The one from the local hard drive is working fine.

Thanks.

 

Edited by anickname

Share this post


Link to post
Share on other sites

No, just for home use.

With version 7.x I had no problems.

I sent you a crash dump file over email (maybe it helps).

Share this post


Link to post
Share on other sites
4 minutes ago, anickname said:

No, just for home use.

With version 7.x I had no problems.

I sent you a crash dump file over email (maybe it helps).

Sadly those dumps aren't very helpful for .NET applications. Thanks for sending it though. Just to clarify, the same collection and data works fine on another machine?

Share this post


Link to post
Share on other sites

Assuming you have no issues updating, I would first try updating that machine. I'm guessing it would resolve the issues, though I can't say for certain. All I can figure is it's one of these three possibilities:

  • The .NET framework or a related library is somehow corrupted
  • There's a missing our out of date library of some sort
  • There's some kind of odd configuration issue causing the problem

You could also try reinstalling the latest version of the .NET framework to see if that helps.

Share this post


Link to post
Share on other sites

Launchbox clean install (8.2), no games:

- W10 ENT LTSB 1607, network drive - crash

- W10 ENT LTSB 1607, local drive - working

- W10 PRO 1709, same network drive as LTSB - working

- W10 PRO 1709, local drive - working

Hope, is clear now.

Thanks.

Share this post


Link to post
Share on other sites

I see, thanks. So there's some kind of specific issue with running it over a network drive on that older version of Windows 10. Are you able to update? That's a pretty specific use case that I probably won't be able to dive into.

Share this post


Link to post
Share on other sites

You're welcome.

Nothing specific.

I have a NAS where I store the games and Launchbox.

The NAS has a smb/cifs share that is mapped as drive X: on my desktop.

I always ran Launchbox from X: drive without problems.

Edited by anickname

Share this post


Link to post
Share on other sites

LTSB is a windows 10 version without those fancy stuff like Cortana, Windows Store ...

Is more like Windows 7, 8 ...

It receives security updates normally and features updates from 2 to 2 years.

Share this post


Link to post
Share on other sites

@anickname Ah, well that hopefully gets us a lot closer. I haven't seen this anywhere else yet, but that is most likely a security issue where Windows is refusing to load the DLL over a network path. The first thing I would try is "unblocking" the DLL using the method described here: https://stackoverflow.com/questions/21753979/visual-studio-could-not-load-file-or-assembly-operation-is-not-supported-erro

@ForsakenZaroc What version were you using before upgrading? I assume Big Box worked previously? Are you running it over a network path?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...