CDBlue Posted February 13, 2018 Share Posted February 13, 2018 (edited) 31 minutes ago, Goldug said: No, I'm on Windows 10 v.1703 build 15063.877. Hmm, isn't the latest release version of Windows 10 v.1709 build 16299.192? Maybe that's the issue, if windows isn't up to date, maybe a needed file for LB/BB (.net maybe?) is also out of date and causing the crash? Edited February 13, 2018 by CDBlue Quote Link to comment Share on other sites More sharing options...
Goldug Posted February 13, 2018 Share Posted February 13, 2018 9 minutes ago, CDBlue said: Hmm, isn't the latest release version of Windows 10 v.1709 build 16299.192? Maybe that's the issue, if windows isn't up to date, maybe a needed file for LB/BB (.net maybe?) is also out of date and causing the crash? I really doubt that's the issue since .net has nothing to do really with what version of Windows 10 you're using. However, I've tried updating to the latest Windows build with no luck. I've done everything except a complete re-install and it still won't work. I've even been in contact with Microsoft who can't figure out what the h* is going on... Quote Link to comment Share on other sites More sharing options...
Goldug Posted February 13, 2018 Share Posted February 13, 2018 17 minutes ago, Jason Carr said: Beta 10 is out now guys; please let me know if it fixes it for you. If you're unable to update it normally because of the crashes, you can download the latest beta from the link below and manually install over top: Yep, seems to work now. It took a long time getting through initializing though, even though it didn't seem to use any disk activity or cpu really, just 18mb ram. What was the fix? I'm really curious. If you don't want to share that info with us, that's okay 1 Quote Link to comment Share on other sites More sharing options...
The Papaw Posted February 13, 2018 Author Share Posted February 13, 2018 @Jason: That updated for me as normal, will let ya know if anything else creeps up. Thank you sir. 1 Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted February 13, 2018 Share Posted February 13, 2018 1 minute ago, Goldug said: Yep, seems to work now. It took a long time getting through initializing though, even though it didn't seem to use any disk activity or cpu really, just 18mb ram. What was the fix? I'm really curious. If you don't want to share that info with us, that's okay Good deal. The initializing process is the portion that extracts files; it's normal for that portion of the process to be much longer on the first launch after an update. The issue was caused by a glitch in the latest version of our deployment system, believe it or not. It had nothing to do with the LaunchBox code lol. 1 Quote Link to comment Share on other sites More sharing options...
Goldug Posted February 13, 2018 Share Posted February 13, 2018 (edited) 2 minutes ago, Jason Carr said: The issue was caused by a glitch in the latest version of our deployment system, believe it or not. It had nothing to do with the LaunchBox code lol. Haha, yeah those things happen sometimes I guess Some more good news: I can finally import my Steam games! Edited February 13, 2018 by Goldug 2 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.