Microsoft .NET - Check Failed (Vortex 1.6.7)

[I2I0T]

Somewhat ready to give up. I have the .net 8.0, the newest. I try to install the 6.0.25 and I get an constant error from even that;
"the feature you are trying to use is on a network resource that is unavailable"

I own the folders, all of that, full permission, none of its working. 

[OpalBunnies]

January 2024 (For the Google search algorithms!)

You sir are a mother-loving saint! But, it took me a bit to understand a bit of what you were stating without full context into finding the dotnet installation folder. So, I'd like to clear that up, a year and a half following the post.

If you're like me and tcutchi, you like micromanaging your installs and directories. This leads to your installs like "dotnet" being installed elsewhere.

It may not be installed in a "Program Files" folder, but may instead be directly installed into another directory.
In my case, it was not installed to something similar to "B:\Program Files," but it was instead installed directly to "B:\" under it's own folder: "B:\dotnet"

So, if you can't seem to find the "Program Files" folder that has issues, it may not exist. Search instead for a "dotnet" folder, and repeat the same steps where you add "ALL APPLICATION PACKAGES" into the Security tab of the "dotnet" folder's properties.

If you find the "dotnet" folder, and everything still seems to be in order, I'd honestly try uninstalling your .NET stuff from your non-C:\ drive, and reinstall to the default path Windows ordinarily wants to install to.

 

TL:DR?
Here's the fix in plain-text steps.
                                     Or, check out this YouTube Video that covers ALL of this! 

1. Before you go rooting around your file system and adding in group permissions and the likes, double check Vortex is capable of installing mods without sandboxing. (For those unaware, Vortex downloads and installs mods to a "sandbox," or an isolated environment, just in case there's some malicious code inside a mod.)
   • To check this, open Vortex. On the left, click Settings.
   • Go to the "Workarounds" tab. The third toggle should be "Enable Sandbox." Click that so it turns grey. You've now disabled the sandbox.
     • You'll want to re-enable this before doing a lot of mod downloads - the whole point is to protect your computer. Disabling this is like downloading from piracy sites without Anti-Malware. 
   • Now, attempt to download something safe, like "NativeModLoader" for Baldur's Gate 3 for example.
     • If it downloads without issue following this, then continue down the list - you've most likely got the same issue I had.
     • If after this you STILL have an issue, you can try the steps regardless, but it's possible something else is causing problems.
2. Check your "Program Files" folder for correct permissions.
   • Navigate to your C:\ drive and locate the "Program Files" folder.
   • Select the folder, then right click and choose "Properties"
   • Go under the "Security" tab. Verify under Group or user names that 'ALL APPLICATION PACKAGES' is present, with the 'Read & execute,' 'List folder contents,' and 'Read' all set to 'Allow."
   • If 'ALL APPLICATION PACKAGES' is not present, click "Advanced." In the new window, click "Change permissions."
     • Another window will open, similar to the last. Click "Add," then "Select a principal" at the top.
     • Under "Enter the object name to select," type ALL APPLICATION PACKAGES - then press "Check Names." The text you entered in the box should become underlined if typed correctly.
     • Press "OK" and the small window will close. Press "OK" again in the larger window, and you'll be brought back to "Advanced Security Settings for Program Files." Press "Apply," then "OK." You may see another window showing a bunch of folder names; let it do its thing.
     • Press "OK" on the "Program Files Properties" window, and you're done.
3. Program Files has correct permissions?
   • Open your "Program Files" folder and search for the "dotnet" folder. If it's not there, it's likely installed elsewhere. Go to Section 3.
4. Locate and Check your "dotnet" folder for correct permissions.
   • This one may be a little bit longer, depending on how you've set up Windows, or how you customized your install. You'll need to find your "dotnet" folder, since it's not in "C:\Program Files"
   • Once you've managed to find your "dotnet" folder, wherever it may be, the steps are pretty much identical to as if it were under "Program Files," with permissions set incorrectly.
     • Firstly, verify your "dotnet" folder has the correct permissions.
       • Select the folder, then right click and choose "Properties"
       • Go under the "Security" tab. Verify under Group or user names that 'ALL APPLICATION PACKAGES' is present, with the 'Read & execute,' 'List folder contents,' and 'Read' all set to 'Allow."
     • If 'ALL APPLICATION PACKAGES' is not present, click "Advanced." In the new window, click "Change permissions."
       • Another window will open, similar to the last. Click "Add," then "Select a principal" at the top.
       • Under "Enter the object name to select," type ALL APPLICATION PACKAGES - then press "Check Names." The text you entered in the box should become underlined if typed correctly.
       • Press "OK" and the small window will close. Press "OK" again in the larger window, and you'll be brought back to "Advanced Security Settings for dotnet." Press "Apply," then "OK." You may see another window showing a bunch of folder names; let it do its thing.
       • Press "OK" on the "dotnet Properties" window, and you're done.

Edited February 2 by OpalBunnies
Added recommendation to check if turning off "Enable Sandbox" has connection to the issue. Added a YouTube Video Link with identical instructions for ease, because I had nothing better to do with my day other than record my screen and edit for 3 hours.

[loominator199]

Hey is this open source? Can someone fork this and repair? How is this still a thing after 2 years. I have this issue I did all the grants, no weird s#*! on my pc. All running as admin. tried reinstalling multiple times. And vortex keep spamming me with this nonsense. Did the permission grants, all the bs with the paths and nothing. It is clearly a bug please fork and fix someone. I would if I could.

 

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.0-rc.2.20475.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.0-rc.2.20475.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.27 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.0-rc.2.20475.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.27 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

 

[Pickysaurus]

14 minutes ago, loominator199 said:

Hey is this open source? Can someone fork this and repair? How is this still a thing after 2 years. I have this issue I did all the grants, no weird s#*! on my pc. All running as admin. tried reinstalling multiple times. And vortex keep spamming me with this nonsense. Did the permission grants, all the bs with the paths and nothing. It is clearly a bug please fork and fix someone. I would if I could.

 

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.0-rc.2.20475.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.0-rc.2.20475.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.27 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.0-rc.2.20475.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.27 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

 

It's not broken, you've just not got the correct .NET installed. Please read the linked help article. 

 

You need .NET 6.0 NOT .NETCore

[hnnnnnnmmmmmg]

been trying for not too long now, only like ~2 hours to get this working. vortex doesn't seem to like the newest version of .net desktop runtime, i finally gave up and as soon as i installed 6.0.2 (? maybe .4, i already forgot) it immediately worked. i was getting 0 files processed, 1 file failed to process in the (admin) command prompt, but that was fixed after i realized i hit the wrong download button (a different kind of .net). i did end up getting 1 file processed 0 files failed to process, but vortex still couldn't see it after i closed and restarted it. it's not really a problem anymore, but i was just wondering if anyone had any idea why this was happening.

[papikuhli]

vortex really needs to be updated to use current .net (.net 8.0 )  why has this not happened?   After struggling with this issue and getting it fixed a number of times and having it revert back to broken once a update comes along. It will literally be fine for a few updates then like recently a broken update of vortex then hot fix.  This is a bug( or design flaw with the vortex software) that takes advantage of a loop hole in a microsoft program version dot net 6.x to create a sand box.   hopeful that, the new VORTEX wont use such and will stay current.  This is really too common of a problem to be going on for this many years with out being fixed internally in vortex. This should not be something the user spends days weeks trying a 100 different possible solutions to fix.   seriously win 11 has been out for a long time why is vortex still using a outdated dot net 6?   Hell I get a message popup when attempting to install dot net 6 that is a much older version than I already have installed.

[showler]

17 minutes ago, papikuhli said:

vortex really needs to be updated to use current .net (.net 8.0 )  why has this not happened?

Because it's not Vortex.  It's Electron, the program that Vortex uses as a base.

And that's not in the control of the Nexus devs.

[Pickysaurus]

4 hours ago, papikuhli said:

vortex really needs to be updated to use current .net (.net 8.0 )  why has this not happened?   After struggling with this issue and getting it fixed a number of times and having it revert back to broken once a update comes along. It will literally be fine for a few updates then like recently a broken update of vortex then hot fix.  This is a bug( or design flaw with the vortex software) that takes advantage of a loop hole in a microsoft program version dot net 6.x to create a sand box.   hopeful that, the new VORTEX wont use such and will stay current.  This is really too common of a problem to be going on for this many years with out being fixed internally in vortex. This should not be something the user spends days weeks trying a 100 different possible solutions to fix.   seriously win 11 has been out for a long time why is vortex still using a outdated dot net 6?   Hell I get a message popup when attempting to install dot net 6 that is a much older version than I already have installed.

You should probably do a little reading up as to why .NET 6 and .NET 8 are not strictly updates of the same software and are - in fact - different variants instead. As long as you have the latest .NET 6 build you're not less secure than with the latest .NET 8. There are major differences between versions which means software that depends on specific features can't always be upgraded. 

[papikuhli]

That kind of is my point. .net 6 will become not supported/depreciated in the future (nearer than farther) dot net 6 end of life is Nov of 2024.    Notices have been sent out to developers some time ago. I am sure the vortex team received those a while ago. Is there a plan to make the changes to the current vortex or will the new one be replacing it before that happens? I have done a considerable amount  of reading, I have had to.  The Microsoft team considered the features that were removed as loopholes,  securities risk , inefficiency's or other.  I am not with Microsoft  so I can not tell you what their definitions are that  apply to the feature that vortex uses from dot net 6 or its base electron.  And I did not mention any security concern and the words used by Microsoft  : Loopholes, inefficiency's and other are verry vague at best. To me a lot of times loopholes are put in place on purpose for a number of reasons. When someone with nefarious intent finds them they could be possibly be a problem but not always. It could be a complete different definition as well. So Loophole vague.  Inefficiency  could mean memory leak, power leak, speed bump or almost anything to make newer version appear better,  again vague. Other WTH is it suppose to mean ??? Catch all parse way past vague .  Fact is dot net 6 is at the end of service and something that should be corrected in the current version or addressed in the new vortex so no one that uses it has to experience this problem.  it does not matter what you call it vortex was set up to use this depreciated feature ( Of  dot net 6) and this has been known to be a issue/problem for a long time.    

Is there a plan to use something else instead of this feature ( in dot net 6)?  is the  New vortex going to use a different base if that is the problem?  Is there going to be the Im A pro toggle that has been talked about in the past so the user can actually put a mod where they want?