Ryusen85 Posted May 25 Share Posted May 25 Hi all! I'm not new to Launchbox, but I am recently having issues with opening the program after the version 13.12 dropped. I can go to my local install folder and install older version at 13.2 and it opens. What am I missing? Something has been introduced in these new versions that my system doesn't like and is not wanting to open Launchbox. I have some attached error log files upon crash when attempting to open newest build 13.14. Please I appreciate any help from anyone who happens to know what is causing this. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 Reads like you're trying to load a bad theme XML file. What theme are you using? If using Default, did you try to edit something in the files? Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 3 hours ago, C-Beats said: Reads like you're trying to load a bad theme XML file. What theme are you using? If using Default, did you try to edit something in the files? No I have default theme. I don't really mess with themes. The last time I used Launchbox to play was on the previous build that worked. When I opened the program recently I did an update to latest build and after install I get this error. If I roll back the update to previous build it loads just fine. Only new build crashes after opening. I've read through forums and kinda at a loss. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 Does running the current version installer over top work? Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 18 minutes ago, C-Beats said: Does running the current version installer over top work? If I understand this correctly, no. So If I navigate to local drive/user/launchbox/update and then run installer from previous version, 13.08 I think, it works and loads just fine. Once I am in and run update to latest version from help menu, or download and run latest version .exe still same problem. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 The 13.14 installer should be in the updates folder as well. Just run it and point it to the current install (make sure you don't point to a LaunchBox folder WITHIN the current LaunchBox folder when doing it) and then see if it corrects the issue. Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 (edited) 12 minutes ago, C-Beats said: The 13.14 installer should be in the updates folder as well. Just run it and point it to the current install (make sure you don't point to a LaunchBox folder WITHIN the current LaunchBox folder when doing it) and then see if it corrects the issue. So I tried to do that and same problem happens. It is so frustrating cause I haven't had any problem like this with multiple systems since I first got LaunchBox back in 2018. Just on my current PC build alone I got in 2019, I have current build all the way back to 9.7. You have been awesome helping me try to figure this out. Mad props my dude. Any other thoughts on what I can try? Edited May 28 by Ryusen85 Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 What file system format is your drive? NTFS or exFAT? Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 13 minutes ago, C-Beats said: What file system format is your drive? NTFS or exFAT? NTFS on Windows 11 Pro Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 Can you open up \\LaunchBox\Data\Settings.xml and look for the <Theme> tag and change that value from Default to Old Default and then save the file and attempt to open LaunchBox and let me know if you still encounter it? Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 11 minutes ago, C-Beats said: Can you open up \\LaunchBox\Data\Settings.xml and look for the <Theme> tag and change that value from Default to Old Default and then save the file and attempt to open LaunchBox and let me know if you still encounter it? I did that and I get the same error, but now the LauchBox loading dialog stays on screen. Doesn't do anything so I have to force close in task manager. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 Can you use the 13.14 installer to install a new instance of LaunchBox some where on your computer and let me know if the new instance works? Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 8 minutes ago, C-Beats said: Can you use the 13.14 installer to install a new instance of LaunchBox some where on your computer and let me know if the new instance works? IT WORKED! Ok Ok Ok.. hold the phone. One you are not only a gentleman among dudes, but you are also a bro amongst brethren, and yet you are a turkey leg amongst chicken wings! Aside from this being great news, I am confused on how this could be happening. Would I have to completely uninstall all instances and do a fresh install on the drive with issues to fix the problem there? Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 For starters I'd close all instances of LaunchBox. Then navigate to an old instance of LB and copy it's data folder to the new instance, (delete the folder in the new instance and then copy the old over). Then start the app again. If it still works you probably have a corrupted file some where in the install. Sounds like it could be either a plugin, or some no longer needed files lingering in the core or metadata folders causing an issue. If you're feeling adventurous delete the following folders from an existing install and then run the installer over top the location and see if it corrects anything: LBThemes Metadata Plugins ThirdParty Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 22 minutes ago, C-Beats said: For starters I'd close all instances of LaunchBox. Then navigate to an old instance of LB and copy it's data folder to the new instance, (delete the folder in the new instance and then copy the old over). Then start the app again. If it still works you probably have a corrupted file some where in the install. Sounds like it could be either a plugin, or some no longer needed files lingering in the core or metadata folders causing an issue. If you're feeling adventurous delete the following folders from an existing install and then run the installer over top the location and see if it corrects anything: LBThemes Metadata Plugins ThirdParty So I was able to copy data folder from old instance to new instance and it worked just fine. I did feel adventurous and tried the deletion of the LBTheme, Metadata, Plugins, and ThirdParty folders in the old instance then did a install over the top with 13.14. I still had the same problem happen. It is so weird that it keeps happening. If I were to copy to My Documents the data folder from the old instance and completely delete the old Lauchbox folder to remove all traces, then do a fresh install of 13.14 and replace the new data folder with the old backup I made, would that be a recommendation? Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 What file location is the new and old installs at? I know some locations have caused issues in the past, like installing directly to the root of the drive. Curious if WHERE it's being installed is the problem. Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 35 minutes ago, C-Beats said: What file location is the new and old installs at? I know some locations have caused issues in the past, like installing directly to the root of the drive. Curious if WHERE it's being installed is the problem. Well I got frustrated at it and just removed the whole install instance, restarted my PC, installed again annnnnnd same thing. To answer your question, it's installed at the local C drive where OS is installed. I have it here cause it loads the fastest on my NVME drive. Basically entire path is C:\\Users\User\Launchbox, but for some reason on the same OS with same system file dependencies it works just fine when installed on a separate internal SSD. It's really curious and annoying at the same time. Quote Link to comment Share on other sites More sharing options...
Ryusen85 Posted May 28 Author Share Posted May 28 On a side note, it seems to be something when trying to load the interface, cause I notice when I see splash screen with loading info parsing, I notice as soon as I see loading interface it crashes. Idk if this makes any difference but noticed this also. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.