No longer able to launch FNIS, BodySlide or Wrye Bash from Vortex after recent update.

[HadToRegister]

 

 

YOu shouldn't run Vortex as Admin.

 

Do you have UAC turned off? IF so, turn it on

 

UAC turned off??? Who says that?

 

So far UAC has been a pain in the buttock for ALL mod manager, and for tools like FNIS and Bodyslide. I doubt that this is any different for Vortex. Since years we are preaching beginners to move Steam out of "C:\Program Files(x86)" so they can't run into UAC problems.

 

 

 

I asked if they had it turned off, because some people, for whatever reason, think turning off UAC is good.

 

That is why I asked, and told them if they had it turned off, to TURN IT BACK ON

[Zanderat]

This definitely an elevation issue. I have Vortex not set as admin, but for some reason (I don't remember setting this) Wrye was set to run as admin. Since 18.9, Wrye wouldn't run in that configuration. I just set Wrye to not admin and now it launches through Vortex again.

[Tannin42]

 

UAC turned off??? Who says that?

 

So far UAC has been a pain in the buttock for ALL mod manager, and for tools like FNIS and Bodyslide. I doubt that this is any different for Vortex. Since years we are preaching beginners to move Steam out of "C:\Program Files(x86)" so they can't run into UAC problems.

 

 

It doesn't have to be, Vortex, FNIS, Bodyslide can all work fine as long as the regular user has write permissions to the data directory (or the entire game directory if you want to install enbs/skse through the mod manager), Vortex will even help set up the proper permissions. Whether you acquire the permissions by having games installed in a location that has full write permissions in the first place or you give yourself permissions to a game inside the program files directory makes no real difference.

What you shouldn't do (and shouldn't advice others to do, unless you hate them) is run applications/games as admin or disable UAC entirely.

[Tannin42]

And yes, this problem with Vortex is caused by elevation. it will be fixed in 0.18.10, for now start the tools outside Vortex or (much better!) stop running them as admin.

[fore]

 

 

UAC turned off??? Who says that?

 

So far UAC has been a pain in the buttock for ALL mod manager, and for tools like FNIS and Bodyslide. I doubt that this is any different for Vortex. Since years we are preaching beginners to move Steam out of "C:\Program Files(x86)" so they can't run into UAC problems.

 

It doesn't have to be, Vortex, FNIS, Bodyslide can all work fine as long as the regular user has write permissions to the data directory (or the entire game directory if you want to install enbs/skse through the mod manager), Vortex will even help set up the proper permissions. Whether you acquire the permissions by having games installed in a location that has full write permissions in the first place or you give yourself permissions to a game inside the program files directory makes no real difference.

What you shouldn't do (and shouldn't advice others to do, unless you hate them) is run applications/games as admin or disable UAC entirely.

 

With all due respect for your experience, but I think this is theory. I remember (and I quote that in the FNIS instruction) DuskDweller complaining a couple of years ago about the rising number of issues with Windows 10 UAC. And if I google "problems with windows 10 UAC" I get 1.7m hits. And this is just complemented by all the FNIS users reports reporting access issues and similar Windows problems. Why?

 

A "simple" users will not play around with file permissions. And they usually have logins with admin rights. And if you ask them for an FNIS output they are very likely to have Steam and Skyrim installed in "C:\Program Files(x86)".

[HadToRegister]

 

 

A "simple" users will not play around with file permissions. And they usually have logins with admin rights. And if you ask them for an FNIS output they are very likely to have Steam and Skyrim installed in "C:\Program Files(x86)".

 

 

We've been telling people to NOT install stuff to "Program Files (x86)" because windows is far too protective of it.

[fore]

 

 

 

A "simple" users will not play around with file permissions. And they usually have logins with admin rights. And if you ask them for an FNIS output they are very likely to have Steam and Skyrim installed in "C:\Program Files(x86)".

 

 

We've been telling people to NOT install stuff to "Program Files (x86)" because windows is far too protective of it.

 

Ok. But when you are telling people to turn on UAC without telling them not to use "Program Files(x86)", then your intention can easily be misunderstood. Like in my case. :)

[Siglendyn]

Well as it turns out I in fact did have FNIS, BodySlide and Wrye Bash all set to "Run as Administrator". I don't even remember why I did that (this old brain gets foggy sometimes lol)

 

Anyway, removing that privilege has solved the problem and they all now start from within Vortex.

 

Steam is installed on my C drive but all games are installed in libraries on several internal hard drives. As far as UAC, I hate it and it's disabled,

have been doing that without problems since Windows 7 (I'm on Windows 10 now)

 

Thanks for all the help people, much appreciated :yes:

[mechro]

And yes, this problem with Vortex is caused by elevation. it will be fixed in 0.18.10, for now start the tools outside Vortex or (much better!) stop running them as admin.

What about people who run F4SE, which i dont know about others, but on my machine it will not launch if not run as admin? I guess we just wait for a fix because this is an issue (the first i've had with vortex).

 

 

[AugustaCalidia]

All the Windows permissions horror stories notwithstanding, since Windows 7 I have run my computers with one Administrator account only, UAC turned on, and "Programs Files(x86)" as the destination for all my Steam game installations. I have never had any significant issues. I guess I must have slipped through the cracks.