13.22 install issues

[5thWolf]

Well I uninstalled .net and tried to reinstall however with all .net removed from windows,  .net would not allow me to reinstall using a fresh downloaded installer because it kept telling me it was still installed "current or newer version" even though I just uninstalled it and even rebooted PC. Soooo..... I am attempting and full Windows fresh reinstall incase its a debacle with .net or Win updates or errors or whenever else it could possibly be. Will report after all done to see if anything happened.

Edited July 5 by 5thWolf

[5thWolf]

Well... Installed Windows, ran the installer, It even installed .net 3.1 something x64 during installation and same exact thing! Doesn't launch at, doesn't generate an event on viewer. Nothing happens at all.

[5thWolf]

Ran the installer for 13.21, and like @DZuroff mentioned earlier, fired right up. So as far as I can tell definitely an issue with 13.22 for mapped network drives!

Edited July 5 by 5thWolf

[Wrecks]

I'm having the same issues with Launchbox 13.22 installed on a mapped drive. Oddly enough both Big Box and Launchbox act as I've never opened them (Even choosing "Run as Administrator") but the unins000.exe file to uninstall (from same mapped drive) opens without any issues.

This is on a fresh install both locally to my C drive and also my mapped drive. As a comparison, my local C drive has 25 files and folders in the Launchbox folder, but my mapped drive only has 10 - not sure why it isn't able to fully install on a mapped drive.

I hope the issue is figured out soon and a work around is figured out. I'm uncertain if this could be something with Launchbox or Microsoft Windows updates, but have been pleased with the support Launchbox and team have provided.

[Wrecks]

Tried to simply copy the folders and files from the working installation on the C drive to the mapped drive and made no difference - wasn't holding my breath but just thought I would try.

[C-Beats]

I looked into the issue people are encountering running LB from a network location. It seems we've hit a snag with a known issue with the latest version of the .NET runtime. We're assessing how best to correct and will let you know when we do.

[5thWolf]

On 7/7/2025 at 2:53 PM, C-Beats said:

I looked into the issue people are encountering running LB from a network location. It seems we've hit a snag with a known issue with the latest version of the .NET runtime. We're assessing how best to correct and will let you know when we do.

Oh thank goodness! Love to hear that! Also please if possible put back relative file location ( ..\folder\game.rom ) instead of what it is now or UNC.

[C-Beats]

8 minutes ago, 5thWolf said:

Oh thank goodness! Love to hear that! Also please if possible put back relative file location ( ..\folder\game.rom ) instead of what it is now or UNC.

We always use relative pathing when possible so not entirely sure what you're referring to

[5thWolf]

33 minutes ago, C-Beats said:

We always use relative pathing when possible so not entirely sure what you're referring to

Before 13.19 when selecting a game file when adding a game, it would always place it as "..\sega\genesis\game.rom"

After 13.19 it randomly made it as either "E:\emulator\sega\genesis\game.rom" or "\\gaming-nas\emulation\emulator\genesis\game.rom" and this is random. I can add several a games one by one manually in the same planform and it shows up either way random every time. Here is screen of the game I just added and this will never launch.

If it labels the E: drive like the first example it works unless you open it on another computer on the network that doesn't use E: as the letter for that network drive.  Which defeats the purpose of the entire project being portable.. And the the second one, which is what this pic above shows never works at all. I have to manually change every game I add to be as I showed above before 13.19 like this: "..\Sony\PS2\Games\Legaia 2 - Duel Saga (USA).iso" then it works perfectly across all PCs on the network regardless of what drive letter is used.

[DonkeyPuncherXL]

I just ran into this issue a couple of days ago after installing 13.22. Been racking my brain trying to figure out what is wrong.

Been running my LaunchBox of a Synology NAS and after the "upgrade" it just stopped working!

Where can i download older versions of Launchbox?

Edited Wednesday at 02:54 AM by DonkeyPuncherXL

[C-Beats]

2 minutes ago, DonkeyPuncherXL said:

I just ran into this issue a couple of days ago after installing 13.22. Been racking my brain trying to figure out what is wrong.

Been running my LaunchBox of a Synology NAS and after the "upgrade" it just stopped working!

Where can i download older versions of Launchbox?

First check your \\LaunchBox\Updates folder for older installers. If that doesn't work contact support and they can get ya a link to whatever version you want.

[C-Beats]

1 hour ago, 5thWolf said:

Before 13.19 when selecting a game file when adding a game, it would always place it as "..\sega\genesis\game.rom"

After 13.19 it randomly made it as either "E:\emulator\sega\genesis\game.rom" or "\\gaming-nas\emulation\emulator\genesis\game.rom" and this is random. I can add several a games one by one manually in the same planform and it shows up either way random every time. Here is screen of the game I just added and this will never launch.

If it labels the E: drive like the first example it works unless you open it on another computer on the network that doesn't use E: as the letter for that network drive.  Which defeats the purpose of the entire project being portable.. And the the second one, which is what this pic above shows never works at all. I have to manually change every game I add to be as I showed above before 13.19 like this: "..\Sony\PS2\Games\Legaia 2 - Duel Saga (USA).iso" then it works perfectly across all PCs on the network regardless of what drive letter is used.

I'll have to test and see what's going on there. Thanks for bringing it up!

[5thWolf]

If I can help in anyway let me know.

[DonkeyPuncherXL]

Thank you! Installing 13.21 fixed the issue! I can finally relax my anus!

Avoid version 13.22 if you are running it off a NAS!

Edit: if you are downgrading don't forget to delete the 13.22 setup executable from the Launchbox Update folder  

Edited Wednesday at 03:12 PM by DonkeyPuncherXL

[Zarach]

13 hours ago, C-Beats said:

I'll have to test and see what's going on there. Thanks for bringing it up!

I put a link to a 13.19 thread with more info on this ongoing set of issues. Here it is for quick clicks!

There's some more info earlier in this thread with some of the UNC path issues I am still seeing along with some others. One notable item is going into Platforms to make any changes on a system will change relative paths to UNC paths in the Platforms.xml file. 

Edited Wednesday at 04:57 PM by Zarach

[xokia]

@faeran is who worked on and fixed this for 13.21. He had replicated the setup I had and also had me test it. It worked for 13.21 after the fixes. I stopped upgrading because this seems to continuously break super annoying.

I have a NAS with LBX on an SSD and a 10G connection. NAS is a viable option and like others have said it makes it portable so you can run on different networked machines.
Its still a bit slow my guess is because of how the database is built and the tons of small files it fetches (based on how much is pulled into memory). I would not recommend running in on a HDD NAS it would be tediously slow.

I don't know what the specific issue is here for slowness but I remember working on a similar very large database issue in my past with python.

I think i went from shelve->lmdb(fast but lots of disk space)->and then rocksdb

 

 

Edited Wednesday at 08:16 PM by xokia