DotNet SDK Not Detected

[Noggog]

Even after installing the DotNet SDK as described in the installation instructions, Synthesis reports that it cannot be found:

[Noggog]

Things to not do

Uninstall/reinstall different versions of the DotNet SDK repeatedly. This is typically what causes the error in the first place, as the uninstallation of one SDK sometimes leaves the other in an "unregistered" state. If you followed the install instructions and installed an x64 DotNet 6.0 SDK already, try these other things first, before going on a reinstall spree:

Things to Try

Ensure SDK can respond to dotnet --Version

• Open a command line, and run dotnet --version. You should be getting back something like 6.x.x as a response.
• Double check that you have a single DotNet SDK installed (usually found in ProgramFiles/dotnet/), and that it is x64.
• Double check your environment variable paths have the dotnet install location listed (as this is how command lines find it). Notice in this video, the environment variable exists and points to a folder that has the dotnet.exe. If that was missing, you would want to add the path line to help the system find where your dotnet.exe was.

Running dotnet --version:
https://user-images.githubusercontent.com/24981326/102663650-20d80700-4136-11eb-80ce-8730f11da64a.mp4

Checking your environment variables:
https://user-images.githubusercontent.com/24981326/102663662-246b8e00-4136-11eb-92a6-5a6f2d06131b.mp4

At the end of the day, dotnet --version must be able to return a valid version before Synthesis can pick it up. Other internet resources related to "DotNet SDK not detected" might be able to help you, as this is a more generic problem not necessarily related to Synthesis, specifically.

Uninstalling Old Net SDKs

Users have reported that the presence of old 32bit x86 SDKs can cause problems. Users will report that they are able to run dotnet --version themselves from the command line, but Synthesis fails to.

Sometimes older x86 versions can sometimes cause conflicts like this. Try uninstalling any x86 setups and trying again:

1. Uninstall any x86 Net SDKs using the windows uninstall systems. Sometimes there is none. This is fine.

Once done, double check that your environment variables remain intact after doing so, as sometimes uninstalling can "deregister" the environment variables mentioned above.

2. Check if Program Files (x86)/dotnet still exists, and if so, delete (or move them elsewhere for backup) them manually. You might need to close some applications or restart to get it to not be in use.

Now that x86 is gone from your system, try again and see if Synthesis can run dotnet --version correctly now

[Noggog]

Hey! I would say hop on the Discord which is a better spot for 1:1 back and forth troubleshooting. If it ends up being something new I'll add it to this FAQ, but usually it's something on the above suggestion list.

Have you checked if there's an x86 installation folder? What does dotnet --info give you back?

[Tum1370]

Hi, thanks for your reply.
Yes, I checked for different installs but there was none.
I have got it working though. Maybe something that you should add, just in case.
After downloading synthesis, I un packed it into my downloads folder on my C drive, then instantly tried running it. It actually worked.
I then moved the whole folder to the drive where I want it, my M drive. And tried running it again from there.
This time it worked.

The first few times I tried, I never tried running it on my C drive, I always unpacked it, moved the folder to my M drive, then tried running.

Am not sure why this worked, but it did.

Maybe the initial run on the C drive, with my OS install, set up synthesis to know that dotnet was installed ?

Hope this helps you.

Thanks.

[Bl4ckread]

Thank you for the dotnet --info pointer. I had a 5.0 runtime which was causing a blocking error. Didn't catch it from control panel at first because it wasn't labeled as .NET.

Edit: Nvm. I uninstalled the 5.0 runtime, and dotnet --info no longer reports one being on my system, but Synthesis still keeps finding one from somewhere.

[goddessxthemis]

I installed Synthesis on my C: drive and it fixed the issue. I have a separate drive for games and modding tools, but Synthesis needs to be on the same drive as dotnet. I didn't try to move it after installation, so I can't say whether that would have worked.

[Noggog]

Hmm, glad it worked, but unsure that it matters too much. Synthesis is just running dotnet --version on the command line, which shouldnt care where the originating program is located. If you think it does, perhaps swing by the discord with some logs/details and I can take a look at what you're experiencing a bit closer

[Lannakin]

I had an issue installing the new .Net framework and was able to fix it using the repair tool provided by Microsoft..