Jump to content

Microsoft .NET - Check Failed (Vortex 1.6.7)


abysswalkersoul

Recommended Posts

Another thing to check is that you have dot net *6* installed.
Although the installer claims 6 or later, later does not work.
Either they have mistakenly set it to 6 *only*, or they have used something that works in 6 that doesn't work in later versions.

Hope this will help.

Link to comment
Share on other sites

  • 4 weeks later...

 

 

Hi, I'm having .NET issues as well after updating, but I'm seeing a different window:

attachicon.gif Vortex_2022-08-17_07-36-07.png

 

I've tried both links and the CMD Repair method with no change. Reverting Vortex to 1.5.13 works.

 

If it helps, here is my dotnet --info:

attachicon.gif DotNet CMD.png

 

Edit: Disabling Sandbox in Settings did fix it, but my Program Files security window matches the screenshot above:

attachicon.gif explorer_2022-08-17_07-44-32.png

 

Not sure what the issue is...

 

 

EDIT #2 - Figured it out.

I have my default install path set to my E drive (via the registry), so DotNet was installing to E:\Program Files instead of C:\Proram Files. I had to add "ALL APPLICATION PACKAGES" and the aforementioned permissions, and now the error is gone without the workaround in place.

 

Leaving this here in case it helps someone else with this very specific issue. :smile:

Can you elaborate on how you were able to do this? Because the only thing working for me is disabling the sandbox, and my Program Files Properties are the same in the previous post. Still getting the access denied thing with certain mods just not installing. So far this thread is the only thing that has gotten me anywhere.

 

 

Sure. Open a Command Prompt window, and type "dotnet --info". This should list the runtimes you have installed and their locations, hopefully all in a single Program Files folder. You can see this in my second screenshot above.

 

Next, find that Program Files folder (in my case, E:\Program Files), right click on it, Properties, Security tab.

Click on Advanced, then Change Permissions on the new window that opens. Click on Add, then Select a Principal, and type "ALL APPLICATION PACKAGES" into the bottom box. Then Check Names to confirm it's typed correctly. Click ok, and it'll return to that previous window. Make sure to hit Apply here before hitting Ok. It'll apply the change to everything in that folder, though some items may fail, which is fine.

Hopefully this screenshot explains the process well enough (ignore the fact that there's 2 locations, I just had to open a couple Properties windows to get it all in one shot).

 

In case someone reads this that's using a non-English version of Windows, yours may not be called "ALL APPLICATION PACKAGES". Look at the Properties > Security tab for C:\Program Files. and copy the name from there in that case.

 

attachicon.gif Add Folder Permissions.png

 

Thank you soooooo much, I was so frustrated trying to get this fixed and I couldn't find anything anywhere to my problem, you're a legend! <3

Link to comment
Share on other sites

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.

This did the trick for me. After editing, Vortex worked fine. Error with my Windows, not Vortex

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

 

I finally got it working!

 

I installed the .NET SDK from https://dotnet.microsoft.com/en-us/download/dotnet/6.0

 

After that I entered these two commands in CMD as Admin:

 

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)"

 

Sir, you are a lifesaver! After hours of trying various tips from this thread, I finally managed to solve this problem.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...