Microsoft .NET - Check Failed (Vortex 1.6.7)

[mptron]

 

 

I am, sadly, having this problem as well.

 

I updated from Windows 7 to 10 late last year, so I assume that's the main reason things are screwy. However, none of the posted fixes have worked for me, and stranger still is that I wasn't having this problem at all at first.

 

---

 

To make a long story short, I opened up Vortex for the first time in a long, long while, loaded my Skyrim profile, and started downloading a few new mods. I was able to install them just fine, and could even access the sub-windows that let you pick your mod options and all that.

 

Then, suddenly, while I was trying to install a texture mod (entirely cosmetic, nothing fancy), trying to install it suddenly prompted me to download .NET. I did just that, downloading the program and clicking on Repair, but even after a second attempt-and-repair, the problem kept happening. I downloaded the newest up-to-date version, installed it, and the problem still kept happening. So on and so forth.

 

If it's of any referential help, Steam itself is installed on my C: drive, Skyrim and my other Steam-based games are on my D: drive, and I set Vortex up to direct my mods to a separate folder on the D: drive as well.

 

I'm tempted to just disable sandbox as a short-term fix, since I don't really use Vortex for any other games, but it's still kind of a bandaid solution, y'know?

 

Did you check the pinned solution?

 

 

I mean, not to be snarky, but I did straight-up say that none of the posted fixes worked for me. :U

 

To be more specific, though:

At first, I tried the Repair function that Vortex automatically gives you. That didn't work.

Next, I tried downloading the direct file to install/repair it that way. Didn't work.

Before I went to bed last night, I also just flat-out uninstalled and reinstalled Vortex. But that didn't work either.

 

After that, I attempted to fix Program Files permissions. However, when I checked the Properties/Security, it already has both All App. Packs and All Restricted App. Packs.

However, I decided to pull up the command prompt and try those icacls.exe lines anyway. Unfortunately, when I tried them, it said that it didn't have permission to do that, and failed to process the file.

 

On the other hand, I tried doing the same thing with Program Files (x86), and those permissions processed just fine. However, that still didn't help fix the Vortex problem.

 

---

 

Again, since the pinned wiki-post has a little blurb about how modifying the defaults can cause this issue, I can only assume that something happened when I upgraded from W7 to W10. I'm just not really sure what that something is, exactly.

 

 

Same, I tried all the solutions and got the same results as you. In the end I just took the unsafe route and disabled the sandbox and then it stopped having issues. It was the only way to preserve my sanity. But for me this is only the latest of endless frustrations when dealing with Vortex since the beginning. I just wanted to use collections man.

[theGenius001]

I might have found a fix for this.

I had tried everything on this forum, but then looked more into the error and realized that it was looking for dotnet in a different folder than where dotnet 6 was installed. To fix this head to the app called edit environment variables, click on environment variables, and look for "DOTNET_ROOT". Edit this to where dotnet 6 is installed.

[crossfire951]

I might have found a fix for this.

I had tried everything on this forum, but then looked more into the error and realized that it was looking for dotnet in a different folder than where dotnet 6 was installed. To fix this head to the app called edit environment variables, click on environment variables, and look for "DOTNET_ROOT". Edit this to where dotnet 6 is installed.

Thanks!

[lig76]

I have tries everything here, even the above with DOTET_ROOT and still the same error with NET Runtime missing. I've lost 2 hours with this already :nuke:

 

But this post was the real error-solver !

https://www.nexusmods.com/fallout4/mods/68372

Edited April 4, 2023 by lig76

[frogdude909]

FIXED The 6th time I reinstalled .net it worked. fml

OK, so I know that there are solutions to the issue I'm having, and here are all the ones I have tried.
1.)Reinstalling .Net 6 (several times)
2.) run the following commands on CMD as an admin
icacls.exe "C:\Program Files (x86)\dotnet" /grant "S-1-15-2-1:(oi)(ci)(rx)"
icacls.exe "C:\Program Files (x86)\dotnet" /grant "S-1-15-2-2:(oi)(ci)(rx)"
icacls.exe "C:\Program Files\dotnet" /grant "S-1-15-2-1:(oi)(ci)(rx)"
icacls.exe "C:\Program Files\dotnet" /grant "S-1-15-2-2:(oi)(ci)(rx)"
3.) Giving myself ownership of program files and programfiles (x86) through Administrators
4.)Ensure that both have access to ALL APPLICATION PACKAGES
5.)Reinstalled VCredist.x64
6.) reinstalled vortex (it is located on my D: Drive, but was on my C:)
7.)Reinstalled Skyrim, but I've had this same issue with 7 Days to Die as well (bot C: and D: drives)
8.) Turned off sandbox mode
9.) cried
Are there any other steps I could take to fix the issues I'm having?
not necissarily in that order.

https://github.com/Nexus-Mods/Vortex/issues/14168

this is the issue I'm having

I do code in c# using Visual Studio, and I don't know if I could have screwed someting up while working in that, but I haven't touched it since trying to get the mods to install.

Edited April 14, 2023 by frogdude909

[capati]

The pinned message suggests running the command in "C:\Program Files" folder, but that give me "access denied", even when running as administrator. I solved the error by pointing to the "dotnet" subfolder:

icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-1:(oi)(ci)(rx)"

icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-2:(oi)(ci)(rx)"

[sakora]

 

The pinned message suggests running the command in "C:\Program Files" folder, but that give me "access denied", even when running as administrator. I solved the error by pointing to the "dotnet" subfolder:

icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-1:(oi)(ci)(rx)"
icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-2:(oi)(ci)(rx)"

 

 

Thank you after a number of hours trying to fix, this worked for me!!!!

[blahblahdragonblah]

 

The pinned message suggests running the command in "C:\Program Files" folder, but that give me "access denied", even when running as administrator. I solved the error by pointing to the "dotnet" subfolder:

icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-1:(oi)(ci)(rx)"
icacls.exe "c:\Program Files\dotnet" /grant "*S-1-15-2-2:(oi)(ci)(rx)"

 

 

This worked for me as well.

 

[AnderzL7]

 

My solution was to check the DOTNET environment variable, which in my case was incorrect.

To check the variable in CMD use the command:

echo %DOTNET_ROOT%

It must match the path shown using the command:

dotnet --info.

Example in my case dotnet --info indicates that it is in c:\program files\dotnet

We can change the path of this variable using the command:

setx DOTNET_ROOT "C:\Program Files\dotnet" /m

I hope it is understood

 

 

 

 

Thank you good sir. I had multiple dotnet installs and this fixed my problems immediately.

Error occured as the dotnet executable referrenced in my environment variable was located in my appdata folder, which i guess does not support the sandbox feature refferenced by other users.

[BigByrd777]

I found that when I used command dotnet --info no sdks were found so I went to https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-6.0.412-windows-x64-installer

 

After I ran the installer vortex worked for me.