MasterMarkVGC Posted Wednesday at 08:14 PM Posted Wednesday at 08:14 PM (edited) Hello, I've had this issue for a while where Launchbox tries to open and then closes. I try to open it, and I see it under processes in my Task Manager for a few seconds which then says "Suspended" before closing. Big Box still opens fine, but I don't know how to fix this problem with Launchbox. I assume this happened from a recent update and I trying reinstalling the latest update over my Launchbox location which unfortunately didn't work. Quick Edit: This started happening after Update 13-17. Does anybody have a fix for this? Edited Wednesday at 08:31 PM by MasterMarkVGC Quote
C-Beats Posted 23 hours ago Posted 23 hours ago Sorry to hear you're having this issue. Typically the best way to start troubleshooting things like is to try to open the app again and let it crash. Then go into Windows Event Viewer and look at your application logs. There will typically be two errors back to back. One says something like ".NET Runtime Error" both should say it's for LaunchBox. One will just have a generic, "stuff broke" message with a lot of random useless stuff in it. The other should have an actual readable error message. If you could provide THAT (assuming there is one) it'd give us a good starting point as to why you're seeing what you are. The current version of LB is also 13.21. You could try to upgrade to the latest to see if that helps at all. Quote
MasterMarkVGC Posted 18 hours ago Author Posted 18 hours ago Thank you for the reply. This is probably the first time I used Event Viewer to troubleshoot issues so it's pretty new to me. I attached what the Event Viewer shows and I'm not sure where the issue could be. I'm thinking a file somewhere needs to be changed or deleted. This is from the 13.21 version of Launchbox. Quote
C-Beats Posted 17 hours ago Posted 17 hours ago This may be because it's installed in documents. We've seen occasion doing that causes permissions issues. Can you try to install in a folder on one of the drives (like C:\LaunchBox\) and see if you can open the app there? Quote
MasterMarkVGC Posted 17 hours ago Author Posted 17 hours ago I tried that the other day and I tried it again just now and the same thing happened. It's strange because the earlier versions still work. Quote
C-Beats Posted 17 hours ago Posted 17 hours ago Can you do the same steps you did with the one you've installed on a drive NOT in documents? The error should be different. Hoping it gets ya one step closer. Quote
MasterMarkVGC Posted 16 hours ago Author Posted 16 hours ago I tried opening Launchbox in the new drive location and I these are the errors that came up. I saw this error code in one of the last errors in my real location, but it probably wasn't shown in the errors I last displayed. I did a Google search, and it says something about SuperFetch in the Services which I don't think I see at all. Quote
C-Beats Posted 29 minutes ago Posted 29 minutes ago First two can be ignored, that's just Windows being Windows, annoying vague and overflowing with misnomer information. The part that has me confused is why you seem to have permission issues launching the app.... Do you have the same issue if you open the executable C:\LaunchBox\Core\LaunchBox.exe? Quote
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.