Jump to content

vortex isn't installing mods


sattyre
Go to solution Solved by sattyre,

Recommended Posts

Vortex is not installing mods.  After using the automatic installer, placing vortex on my F:  drive, resettting the staging folder to also be on my F game drive, resetting downloads to be on my D storage drive, Vortex is now telling me it can't install mods.  Install failed.  Windows  prevented vortex from loading files necassary to complete install.  Unblock all .exe and .dll files manually.  It also shows this:

File name: 'System.Windows.Forms, Version=6.0.2.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at ModInstallerIPC.Program.Main(String[] arg

Perhaps this will help figure out what is happening.  I shouldn't have to chase files around to enable various exe and dll files.  I will check the anti virus, but it should have an exception for all of F drive.

I thought I would try using the A storywealth mod collection for FO4.  I have windows 10 and only use windows defender's anti virus.  F drive is excluded from anti virus

All files are downloaded.  I can install manually through a file manager but vortex will not install mods even though it's showing them in the list.

Link to comment
Share on other sites

none of those is the problem.  I tried vortex before on a different computer and didn't have any issues.  I believe the issue has something to do with windows updates and the way vortex gets installed.

Just to be clear.  I used the vortex installer and simply changed where it should install.  I was surprised when it still installed into C:\Users\PC name\AppData\Roaming.  I expected it to mostly be on the F drive. 

I don't have any issues with .net that I am aware of.  It downloaded and installed to C drive

Link to comment
Share on other sites

The error message is unfortunately truncated so it's hard to tell but I can almost guarantee you that this is a broken or incomplete .NET install.

One thing to keep in mind is that you likely have multiple copies of .NET because its versions aren't usually backwards compatible and there are variants with and without UI so it's perfectly possible that one .NET application works fine because it's using the .NET 5 installation on your system while another fails because the .NET 6 install is kaputt.

And because .NET installers are such a clusterf***, many .NET applications nowadays ship with their own full copy of .NET so you might even have multiple copies of the same .NET version, one of which works the other doesn't.

 

In this case the System.Windows.Forms library - which is part of the ".NET desktop runtime" but not part of the ".NET runtime" (great job microsoft, really, great job) is either missing, broken or inaccessible. Vortex isn't imagining that, the error message is from .net itself, not from Vortex.

The solution Picky posted (or, more precisely, the wiki link it leads to) should absolutely fix all three potential problems that could cause this error.

  • Like 1
Link to comment
Share on other sites

  • Solution

Thanks Tannin, that would certainly explain why net could be broken and still functional.  I'll redownload net and see if that fixes the issue

Thank you.  That fixed the issue

 

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...