Siouxsie Sioux Posted June 28, 2022 Share Posted June 28, 2022 Hey guys, just got back into roms again after my Retropie days but i'm having issues, I can't seem to get passed the install process, it says "to run this application you must install .NET Core" i click the link, download and install and i get the same error message, any idea, i'm running Windows 11 and my PC is only 3 month old, thought it would install no problems at all ? Any help would be greatly appreciated. Cheers. Quote Link to comment Share on other sites More sharing options...
Siouxsie Sioux Posted June 28, 2022 Author Share Posted June 28, 2022 Sorry for the white highlight, not sure how that happened. Quote Link to comment Share on other sites More sharing options...
Siouxsie Sioux Posted June 28, 2022 Author Share Posted June 28, 2022 Sorted now guys, cheers Quote Link to comment Share on other sites More sharing options...
Retro808 Posted June 28, 2022 Share Posted June 28, 2022 4 hours ago, Siouxsie Sioux said: Sorted now guys, cheers Apologies you did not get any response on this. Glad you got sorted. Would you mind advising what you ended up doing in case someone else runs across the same issue with Win 11. Quote Link to comment Share on other sites More sharing options...
k_rollo Posted June 29, 2022 Share Posted June 29, 2022 3 hours ago, Retro808 said: Would you mind advising what you ended up doing in case someone else runs across the same issue with Win 11. Based on his error message, I would suggest manually installing the .NET Runtime then the desktop version - https://dotnet.microsoft.com/en-us/download/dotnet Personally, I'd go for the SDK since it has everything for dev purposes (including runtime) but may be a bigger install for those who just wants to run .NET apps. Eitherway should work. Leaving this for the newbies who may come across the same issue. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted June 29, 2022 Share Posted June 29, 2022 10 hours ago, k_rollo said: Based on his error message, I would suggest manually installing the .NET Runtime then the desktop version - https://dotnet.microsoft.com/en-us/download/dotnet Personally, I'd go for the SDK since it has everything for dev purposes (including runtime) but may be a bigger install for those who just wants to run .NET apps. Eitherway should work. Leaving this for the newbies who may come across the same issue. I am familiar with what his error message is and the Windows Runtime 3.1 is what we commonly link to for users with .net install issues to manually install. Was curious to what the original poster did as there have only been a couple Win 11 issues. Also SDK is not needed. The runtime has everything needed for LB. The SDK is just used to create and compile applications using .Net Core. So it os recommended to just download the runtime. Quote Link to comment Share on other sites More sharing options...
k_rollo Posted June 29, 2022 Share Posted June 29, 2022 (edited) On 6/29/2022 at 1:19 PM, Retro808 said: I am familiar with what his error message is and the Windows Runtime 3.1 is what we commonly link to for users with .net install issues to manually install. Was curious to what the original poster did as there have only been a couple Win 11 issues. Also SDK is not needed. The runtime has everything needed for LB. The SDK is just used to create and compile applications using .Net Core. So it os recommended to just download the runtime. Ah yeah, that wasn't mainly pointed at you but to tell people in general what the error message is about. Nonetheless, manually installing the runtime should be a universal solution for Win10/11 regarding this issue. Still, would be cool to know what exactly the OP did. I did say I would "personally" pick the SDK because I do code in C# (which I didn't imply the first time lol). For most end-users, the runtime is enough. Thought I'd tell the newbies the difference. Edited June 30, 2022 by k_rollo Quote Link to comment Share on other sites More sharing options...
C-Beats Posted June 29, 2022 Share Posted June 29, 2022 The link to the correct runtime version is here: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 The screenshot above shows .NET 6 which is not what LaunchBox uses. For Windows 11 users having issues with the runtime not detecting you can do the following: Navigate to Add/Remove Programs Look for an entry that starts with "Microsoft .NET Core" and remove them. Restart your computer. Download and apply the 3.1 desktop runtime (x64) from the link provided and then restart your computer again. You should then be able to open LaunchBox. We've had a few users have to go through this process (unsure if the OP had to or not) for some reason on Windows 11. Quote Link to comment Share on other sites More sharing options...
k_rollo Posted June 29, 2022 Share Posted June 29, 2022 5 minutes ago, C-Beats said: The link to the correct runtime version is here: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 The screenshot above shows .NET 6 which is not what LaunchBox uses. For Windows 11 users having issues with the runtime not detecting you can do the following: Navigate to Add/Remove Programs Look for an entry that starts with "Microsoft .NET Core" and remove them. Restart your computer. Download and apply the 3.1 desktop runtime (x64) from the link provided and then restart your computer again. You should then be able to open LaunchBox. We've had a few users have to go through this process (unsure if the OP had to or not) for some reason on Windows 11. .NET 6 is backwards compatible with 3.1 is it not? Technically, the runtime doesn't necessarily have to be the same with the SDK it was written on. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted June 29, 2022 Share Posted June 29, 2022 8 minutes ago, C-Beats said: We've had a few users have to go through this process (unsure if the OP had to or not) for some reason on Windows 11. Yeah, this is why I was asking if the OP could post what fixed the issue. In case it is something other than what we have commonly known to be needed. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted June 29, 2022 Share Posted June 29, 2022 11 minutes ago, k_rollo said: .NET 6 is backwards compatible with 3.1 is it not? Technically, the runtime doesn't necessarily have to be the same with the SDK it was written on. To be honest I'm not entirely sure. The .NET core run up was pretty different to what Microsoft did with .NET Framework and many of the SDKs/Runtimes weren't fully backward compatible. Also .NET 6 is just simply "dot net" while 3.1 is "dot net core" in moniker and I'm unsure if there was anything done in that transition that makes the newer runtimes not as compatible. Pointing to 3.1 runtime ensures they have a version that WILL run the app and eliminates the possibility of a newer runtime causing potential issues that we then have to get past to troubleshoot any future issues. If the user HAS to have that runtime to run other apps and the OS overwrites the 3.1 runtime there is of course little the user can do, but if it isn't required it eliminates a possible issue for them to get tripped up on moving forward. 1 Quote Link to comment Share on other sites More sharing options...
k_rollo Posted June 29, 2022 Share Posted June 29, 2022 3 minutes ago, C-Beats said: To be honest I'm not entirely sure. The .NET core run up was pretty different to what Microsoft did with .NET Framework and many of the SDKs/Runtimes weren't fully backward compatible. Also .NET 6 is just simply "dot net" while 3.1 is "dot net core" in moniker and I'm unsure if there was anything done in that transition that makes the newer runtimes not as compatible. Pointing to 3.1 runtime ensures they have a version that WILL run the app and eliminates the possibility of a newer runtime causing potential issues that we then have to get past to troubleshoot any future issues. If the user HAS to have that runtime to run other apps and the OS overwrites the 3.1 runtime there is of course little the user can do, but if it isn't required it eliminates a possible issue for them to get tripped up on moving forward. Ah, .NET was Microsoft's attempt to eliminate the need for .NET Framework and .NET Core. They started doing this in .NET 5 but .NET 6 is the LTS version like 3.1. Microsoft will officially end its support for 3.1 on Dec 2022. Hence, updating to the new .NET 6 LTS is a good consideration if looking into the future. I recently updated my dev env from 3.1 to 6 at work and none of the code broke, so that looks promising haha. Microsoft release cycle - https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core Quote Link to comment Share on other sites More sharing options...
k_rollo Posted June 30, 2022 Share Posted June 30, 2022 To those interested, this is Microsoft's technical documentation why they made the monicker change from .Net Core to simply .NET - https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-5 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.