Microsoft .NET - Check Failed (Vortex 1.6.7)

[Pickysaurus]

You could try applying the same fixes to the x86 folder: https://modding.wiki/en/vortex/users/dotnet

[DarkAvengerDOA42]

Most useless mod manager in the universe atm. Cant get FCO installed without it atm. Fomm isnt picking up the supposed fomod that doesnt exist in this world either and mo2 isnt getting it right either. Ready to quit trying to play this stupid game!!!!!! Installed on my machine since 2019 and Ive never gotten to play because its always erroring!!!!!! Im not a dummy either. I know how to mod out games. 2 steps away from rage quitting! And Ive tried 6.0.8 being the one the download tells you use, the error is saying it wants 6.0.11 and Ive tried everything in bettween. Vortex is useless. Its creators are useless!!!!

Edited February 18, 2023 by DarkAvengerDOA42

[Guest deleted34304850]

Most useless mod manager in the universe atm. Cant get FCO installed without it atm. Fomm isnt picking up the supposed fomod that doesnt exist in this world either and mo2 isnt getting it right either. Ready to quit trying to play this stupid game!!!!!! Installed on my machine since 2019 and Ive never gotten to play because its always erroring!!!!!! Im not a dummy either. I know how to mod out games. 2 steps away from rage quitting! And Ive tried 6.0.8 being the one the download tells you use, the error is saying it wants 6.0.11 and Ive tried everything in bettween. Vortex is useless. Its creators are useless!!!!

basic maths tells you you're wrong and its all on you. when you're done with your tantrum how about you ask someone nicely for help and see what happens.

[RagnarokJ]

 

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

 

What specifically did you download of of https://dotnet.microsoft.com/en-us/download/dotnet/6.0? There's a LOT of things to download there! Also I tried the https://modding.wiki/en/vortex/users/dotnet guide but I keep getting this error in the cmd thing "c:\Program Files: Access is denied.

Successfully processed 0 files; Failed processing 1 files". What am i doing wrong? Why did the creators of vortex do this to us? Why aren't they creating a solution for us instead of giving us the middle finger?

[showler]

That's rude. And unfair. Vortex had its dotnet requirement updated because of security risks in the old version.

 

So it's Microsoft's security holes that necessitated the update and Microsoft's program that is having trouble updating.

 

Yet, here they are trying to help people through the problem.

[RagnarokJ]

That's rude. And unfair. Vortex had its dotnet requirement updated because of security risks in the old version.

 

So it's Microsoft's security holes that necessitated the update and Microsoft's program that is having trouble updating.

 

Yet, here they are trying to help people through the problem.

You are right, I was frustrated at the time. It's easy to vent at these times for me.

 

Edit: That said Showler, i'm noticing you haven't helped at all in this topic other than calling out ppl who are frustrated with the new vortex change. I DID start by showing my current problem followed by a mild vent.

[Guest deleted34304850]

don't vent - your frustrations are yours alone - the solutions you need are in this thread, put there by helpful people who want to assist others. as the TOS you agreed to says - if you have nothing good to say, don't say it and move on.

[SBF1]

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?

[Pickysaurus]

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?

[SBF1]

 

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.

Edited March 15, 2023 by SBF1