IllMethods Posted May 16, 2022 Author Share Posted May 16, 2022 Either way, I'm happy to be part of a solution Quote Link to comment Share on other sites More sharing options...
wiesshund Posted September 14, 2022 Share Posted September 14, 2022 Tried this, but did not work Windows 11 pro, new PC Copied launchbox over from old PC ran it, would not start, if brought up the requires .NET core dialog asked if it could install now Clicked Yes Nothing happened, dialog just went away Went to website as suggested here installed both 64bit runtimes core and desktop Same response from launchbox Made sure .Net 3.x and .Net 4.x were fully enabled in windows features reboot PC Same result, dialog pops up telling me this requires .NET core Would you like to download now Clicking Yes just closes the box as if No was clicked Reinstalled windows 11 from latest ISO from MS using media creation tool same exact results Tried on another PC for giggles Plugged in a spare HDD and did a fresh win 11 install Same exact results. Something is amiss Quote Link to comment Share on other sites More sharing options...
wiesshund Posted September 14, 2022 Share Posted September 14, 2022 Update So this is interesting It does not work with Core or Desktop Only with the .NET Core SDK 3.1.423 (x64) That is all well and good i guess, but i dont think the average user should need to pull down a 600mb SDK to run Launchbox as an end user. Could be due to a recent OS change by MS perhaps? Quote Link to comment Share on other sites More sharing options...
RamBRO Posted September 24, 2022 Share Posted September 24, 2022 On 9/15/2022 at 4:01 AM, wiesshund said: Update So this is interesting It does not work with Core or Desktop Only with the .NET Core SDK 3.1.423 (x64) That is all well and good i guess, but i dont think the average user should need to pull down a 600mb SDK to run Launchbox as an end user. Could be due to a recent OS change by MS perhaps? Yep same issue for me and windows 11, now works https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-3.1.423-windows-x64-installer 2 1 Quote Link to comment Share on other sites More sharing options...
Mdnttoker Posted November 30, 2022 Share Posted November 30, 2022 On 9/23/2022 at 7:21 PM, RamBRO said: Yep same issue for me and windows 11, now works https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-3.1.423-windows-x64-installer This is the only solution that worked for me. 1 1 Quote Link to comment Share on other sites More sharing options...
KSib Posted January 20, 2023 Share Posted January 20, 2023 I'm on Windows 11 and I had .NET 7 installed, but I needed this old .NET SDK it seems. Thanks! On 9/23/2022 at 7:21 PM, RamBRO said: Yep same issue for me and windows 11, now works https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-3.1.423-windows-x64-installer 2 Quote Link to comment Share on other sites More sharing options...
timekills Posted March 31, 2023 Share Posted March 31, 2023 On 1/20/2023 at 4:29 AM, KSib said: I'm on Windows 11 and I had .NET 7 installed, but I needed this old .NET SDK it seems. Thanks! I'll third that. Background: Confirmed .NET Framework 3.5 and 4.8 were installed and available in "Windows Features". Installed .NET core (SDKs) for 6 (6.04), 7 (7.04), and even the 8 preview; both 64 and 32 bit versions of all. Ran the "netfx repair tool". Got .NET Core needed each time for LaunchBox What worked was installing the dotnet-sdk-3.1.423-win-x64 file from above posts. Note: This also was on a pre-created/attached drive that I have used on other systems before. It is possible that executing the install of LaunchBox removes this issue, and it only exists when running from a portable solution. Quote Link to comment Share on other sites More sharing options...
Rh1ndle Posted July 22, 2023 Share Posted July 22, 2023 (edited) Thought I'd revive this thread instead of creating a new post since the issue is exactly the same. I have two instances of Launchbox on the same PC for testing and messing around. They are on different drives which shouldn't matter, but they have both worked fine for some time. Now suddenly, one of the instances (my test one thankfully) gives the same error: But my main Launchbox instance works fine! So it can't be .NET so any thoughts as to why one instance works fine and the other does not? It's not critical or anything I'm just bored on a Saturday and thought I'd look into it. Thanks! Edited July 22, 2023 by Rh1ndle 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.