Microsoft .NET - Check Failed (Vortex 1.6.7)

[xyfr1201]

My brain's not too techie to understand all this. I just gave up and uninstall the thing :'( It's was fun and easy to use but not worth the frustration to fix this error. THANKS VORTEX.

[n0la]

I have fixed my permissions as according to the description, and it still didn't work. No my Windows is not "mis"configured, and no, my config worked just fine before this supposed "upgrade".

 

I just moved back to version 1.5.13, and now it just works again.

[sieg6529]

"You must install .NET Desktop Runtime to run this application.

Architecture: x64 App host version: 6.0.9

Would you like to download it now?

Learn about runtime installation: https://aka.ms/dotnet/app-launch-failed"

Is this the right place for help with this issue? I have used vortex for years without incident but, after one of the summer updates, I can no longer install any mods or even update them. Vortex is basically useless on my computer now, which is a real bummer.

[Pickysaurus]

 

"You must install .NET Desktop Runtime to run this application.

Architecture: x64 App host version: 6.0.9

Would you like to download it now?

Learn about runtime installation: https://aka.ms/dotnet/app-launch-failed"

Is this the right place for help with this issue? I have used vortex for years without incident but, after one of the summer updates, I can no longer install any mods or even update them. Vortex is basically useless on my computer now, which is a real bummer.

 

 

Did you read the highlighted answer at the top of the page?

[sieg6529]

The polite response would have been "yes, please try the steps in the highlighted answer". I'll give it a try, but I have to say that this whole experience has really soured me on Vortex. Screwing with command prompts and downloading additional programs kinda defeats the purpose of having a simple mod manager that was working just fine previously. I may as well go back to manual installations of mods.

Edited September 22, 2022 by sieg6529

[showler]

The change was to increase the security of installing mods. And it is Microsoft's update that is failing, not Vortex.

[Tannin42]

The polite response would have been "yes, please try the steps in the highlighted answer". I'll give it a try, but I have to say that this whole experience has really soured me on Vortex. Screwing with command prompts and downloading additional programs kinda defeats the purpose of having a simple mod manager that was working just fine previously. I may as well go back to manual installations of mods.

 

It's not like we had a great choice in any of this.

The decision to introduce a mod format that requires a c# compiler to be installed on every user system to support it was made with FOMM, The choice _we_ have is to either depend on .NET or not support installation of some of the most popular mods.

c# is a fully featured programming language so our choice is to expose you all to security issues or to require a sandbox that then may cause further issues for a small number of users (see below).

Microsoft decided to drop the sandbox that was previously used from .NET so our choice is to stick with a .NET version that is no longer updated or to find a new implementation for the sandbox.

Microsoft decided to no longer ship the new .NET versions with the OS so our choice is to ship .NET with every update increasing the Vortex download size by half for every download of every update for every user or ask you to install it on demand once.

 

If this did not work correctly then one of these happened:

The Microsoft updater didn't work correctly and you have a corrupted .NET installed so our choice is to inform you and ask you kindly to unbreak your system that we didn't break or let you figure it out yourself.

and/or

You chose to mess with your windows setup, messing up your file permissions on your program files directory so our choice is to inform you on how to unbreak your system that we didn't break or let you figure it out yourself.

 

 

Just to make something clear: Based on our data, probably around 99.6% to 99.8% of our users had no issue whatsoever and this experience was seamless. This is not something most users experience and if you need this, especially the latter part of these instructions, you're not innocent of being in this 0.x% group, whether you accept that or not, we are not responsible for how you maintain your system.

 

So before you complain about a response that you may not feel was perfectly polite, maybe also take a moment to appreciate the amount of time being invested into helping such a tiny tiny user group for their self-inflicted pains and how frustrating it may be to then get this kind of cr*p back.

 

You're welcome.

[Guest deleted34304850]

I may as well go back to manual installations of mods.

Do let us know how that works out for you.

[ArchaboldHarriate]

 

 

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

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:

DotNet CMD.png

 

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

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.

 

Add Folder Permissions.png

 

I ran into the failed to enumerate objects in container when I tries the above steps and also had to follow method 1 in this guide to get it to work.

https://softwarekeep.com/help-center/how-to-fix-the-failed-to-enumerate-objects-in-the-container-error-on-windows-10

Edited October 1, 2022 by ArchaboldHarriate

[xxXLink50Xxx]

 

 

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

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:

DotNet CMD.png

 

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

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.

 

Add Folder Permissions.png

 

Well that's just great... I AM using a non-English version of Windows and yes. it isn't called "ALL APPLICATION PACKAGES"... because it does not exist.... neither on C or on D... so what am I supposed to do now. google isn't giving me any helpful results either sadly.