Zarach

I rolled back to 13.21 and the installer doesn't offer any input once it's done, it simply opens LB after it finishes and everything is back to working for me. If I recall this is the normal process when installing all versions of LB. There's not much happening with the installer itself. It's just extracting files and folders to the specified path and it puts a couple icons in the start menu like a shortcut to the LaunchBox.exe and uninstall .exe. It also checks to see if the .net and codecs are installed and if not it installs either or both. Since LB was designed to be portable they didn't have it installing tons of registry keys or registering .dll files all over your system drive. When I went back into 13.21 I started doing a couple changes as I wanted some different icons for a couple of my systems. Totally unrelated to the discussions we've had here today. I noticed each platform I edited and saved caused seemingly random fields in the platform such as the path to "Square" to become a UNC path but the rest of the fields were still relative paths. I don't know what "Square" is, and I never touched that field! It caused me to have to go back into my Platforms.xml file and remove the UNC paths yet again. There's definitely a few strange items happening when LB is sitting on a network drive even aside from the latest 13.22 issues. Hopefully this thread will get some attention and we'll see some updates. Until then, I hope everyone has a great and safe July 4th!!

My update to 13.22 has the same results yours does. The installer just disappears. Usually the update finishes and it launches the new version with the news window in the foreground to see the goodies they added for the version. Mine doesn't do anything, it just disappears. No errors, no logs, no AV behavior, nothing. Clicking the .exe from my network drive - either LB or BB does nothing.

Since 13.19 it has been a little dicey when adding systems and importing games with a mapped network drive. I imported some games yesterday running 13.21 and it imported them all using their UNC path rather than the relative paths that were used in the past. I then had to open the platform.xml file and related .xml files and do a find/replace and get rid of all my UNC paths and change them back to relative paths. I've been combing through my other .xml files for any residue since 13.19 was released for UNC paths as well. The UNC path being ANYWHERE completely negates the "portable" concept which is why I've been hoping and waiting that they would revert back to the behavior of 13.18 and prior versions. There's still an old post here that hasn't been answered in months: I'm super appreciative for LaunchBox and the dedicated staff, you guys rock! Please don't take anything I say the wrong way. If you could give a little more attention to network drive setups in future revisions we would be eternally grateful! I'd be happy to share any of my own configurations with you if that will help at all.

Same exact issue here. Event log is clear, run as Admin doesn't do anything different, The .exe never shows up in task manager. Windows Defender shows no recent threats. I've tried running it from multiple computers as it's on a network drive "R:\LaunchBox" and the behavior is the same. This was also an upgrade from 13.21. Edit: Just tried a fresh install locally to the default install folder (AppData) and everything works fine. I then tried a fresh install to my network drive (R:\) and the .exe won't run. Hopefully that will help pinpoint the issue!

I'm having the exact same behavior with 3.19. I upgraded to 3.20 today and the issue persists. I can confirm rolling back to 3.18 fixes the ability to import ROMs. When 3.19 / 3.20 are installed all my platform game folders are displayed as a UNC path rather than the relative path that was shown in 3.18 and before when choosing Tools --> Manage --> Platforms. Importing ROMs whether it be a folder or file always prepends file:\\\ as described above. It's worth mentioning also that every time the import process starts, it defaults to "network" in file explorer and immediately shows a UNC path as the current directory before allowing me to browse to the network drive that inevitably results in a crash with again the same error described above (The specified path is invalid). I store all my ROMs on a file server accessible by a mapped network drive (R:\). My Windows PC is domain joined to a home lab / network