Tanooki_Style Posted August 31, 2021 Share Posted August 31, 2021 Hello. I just recently went to start Launchbox for the first time in maybe a week (I generally open it once a day or every other day) and I'm getting the following error "To run this application, you must install .NET Core. Would you like to download it now?" I've tried installing the runtimes that the program links to if you select yes to the prompt. They were version 3.1.18. Still the same error. I tried finding out which versions of it I have and then uninstalling them all and only installing 3.1.18. Still nothing. I'm running Windows 10 on the latest update. Not sure what else to try here so thanks for any tips I can get. Quote Link to comment Share on other sites More sharing options...
faeran Posted August 31, 2021 Share Posted August 31, 2021 Hi @Tanooki_Style. LaunchBox does need that version of .NET core. Are you able to confirm whether you downloaded and installed the .NET Desktop Runtime 3.1.18 (middle one on the right, x64 version more than likely). https://dotnet.microsoft.com/download/dotnet/3.1 Quote Link to comment Share on other sites More sharing options...
Tanooki_Style Posted September 1, 2021 Author Share Posted September 1, 2021 I can indeed confirm. X64 versions as you surmised. I have no sdks installed. I have 2 runtimes installed: Microsoft.NETCore.App 3.1.18 Microsoft.WindowsDesktop.App 3.1.18 Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 1, 2021 Share Posted September 1, 2021 Not sure it will help but can you run Command Prompt as administrator and then type "sfc /scannow" (without the quotes) and press enter and let that process run. Once it's done restart your computer and then see if you still have the issue. Quote Link to comment Share on other sites More sharing options...
Tanooki_Style Posted September 1, 2021 Author Share Posted September 1, 2021 Still nothing. Looks like I got some system files uncorrupted out of that though, so thanks! That's a good command to try and add to the memory banks. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 1, 2021 Share Posted September 1, 2021 If it found something it may be worth while to try installing the dependencies again, also make sure you have the most recent version of the runtime, they just released one not long ago so you may not have the most up-to-date and so Windows may be throwing a fit because of it Quote Link to comment Share on other sites More sharing options...
Tanooki_Style Posted September 1, 2021 Author Share Posted September 1, 2021 Yeah, that was the first thing I tried after the system scan. Same ol error message. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 1, 2021 Share Posted September 1, 2021 3 minutes ago, Tanooki_Style said: Yeah, that was the first thing I tried after the system scan. Same ol error message. Have you tried uninstalling the runtimes completely, then reinstalling? Quote Link to comment Share on other sites More sharing options...
Tanooki_Style Posted September 1, 2021 Author Share Posted September 1, 2021 I did reinstall the runtimes, after the system scan had completed and I restarted. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 1, 2021 Share Posted September 1, 2021 1 minute ago, Tanooki_Style said: I did reinstall the runtimes, after the system scan had completed and I restarted. Yeah, but did you just install over the top of an existing install, or completely remove it, then install? Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted September 1, 2021 Share Posted September 1, 2021 Unfortunately we have seen very rare issues where Windows or the .NET Core framework get corrupted and just refuse to work. I wish we had a solution for this, but at least it's rare. There have been a couple of instances in the past where only a reinstall of Windows would fix the issue. Our apologies, but really there's nothing we can do in this situation, as it's clearly a Microsoft/Windows problem. Quote Link to comment Share on other sites More sharing options...
Tanooki_Style Posted September 1, 2021 Author Share Posted September 1, 2021 I uninstalled them first. Quote Link to comment Share on other sites More sharing options...
GrantBillington Posted September 18, 2021 Share Posted September 18, 2021 (edited) I have this same problem. I am running a fresh Windows 10 x64 install and I have tried all the steps outlined above. The LaunchBox installer can't detect my .net Core v3.1.19 install. I've tried both x64 and x86 versions. Re-downloaded, uninstalled, reinstalled, "sfc /scannow" and rebooted. What am I to do? I've paid for the lifetime version and I would very much like to use this software. Edited September 18, 2021 by GrantBillington Quote Link to comment Share on other sites More sharing options...
GrantBillington Posted September 18, 2021 Share Posted September 18, 2021 FIXED Installing the .NET Core 3.1 SDK (v3.1.413) - Windows x64 fixed it for me. https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-3.1.19-windows-x64-installer 1 1 Quote Link to comment Share on other sites More sharing options...
Launchboxaccount Posted April 10, 2022 Share Posted April 10, 2022 If anybody else runs into this and installing the SDK or latest .NET Core doesn't work for you, I fixed it by downloading the latest Launchbox version and re-installing it into the same directory as my existing Launchbox installation. I was then able to run Launchbox and Bigbox and none of my settings changed. Quote Link to comment Share on other sites More sharing options...
jyoungun76 Posted March 3, 2023 Share Posted March 3, 2023 This one... https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-3.1.32-windows-x64-installer I have no idea why you can't just post the installer link... Quote Link to comment Share on other sites More sharing options...
Retro808 Posted March 3, 2023 Share Posted March 3, 2023 13 hours ago, jyoungun76 said: This one... https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-3.1.32-windows-x64-installer I have no idea why you can't just post the installer link... The second post one of the staff did post a proper link. Please do not resurrect a 10 month old thread to provide information already in the thread. 1 Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted March 3, 2023 Share Posted March 3, 2023 5 hours ago, Retro808 said: The second post one of the staff did post a proper link. Please do not resurrect a 10 month old thread to provide information already in the thread. That link is actually slightly easier to use. Sometimes it's just hard to trust that MS won't change those links. They want you to link the one on top of the thread. Quote Link to comment Share on other sites More sharing options...
BoomerGaming Posted March 4, 2023 Share Posted March 4, 2023 Something simple that fixed this issue, Uninstall all .net cores. and launchbox Download net core 3.1. In your downloads folder be sure to install the core as administrator, pay attention to which folder it installs usually Program Files x86, when you re install as administrator Launchbox be sure to change the install folder to the same folder as dotnet again in windows 11 this is Program files x86. I think the issue is the installer puts it in your users folder for windows and the .net runtime, framework, and core are installed in the C:/ drive. Its like the program looks for the dotnet within the same subfolder installed. Hope this helps Quote Link to comment Share on other sites More sharing options...
flubous Posted March 5, 2023 Share Posted March 5, 2023 I uninstalled all .net and launchbox So I´ve installed from this link: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 First, I installed "ASP.NET Core Runtime 3.1.32" So I installed ".NET Runtime 3.1.32" In the end - already sad by the situation - I installed ".NET Desktop Runtime 3.1.32". And it worked! (Installed all as administrator, don´t know if it matters) I don´t know if you have to install the three. My guess is that "Desktop Runtime" alone can solve the problem. Didn´t reinstalled Lauchbox in C:\ (I´m running it separatedly from eXoDOS). 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.