Jump to content

Vortex 1.7.1 Beta wont allow me to run any .exe as admin


OlasMarz

Recommended Posts

I already submitted a bug report with my log via Vortex, but I needed to make corrections to it and didn't know how to find it to add information.

 

It seems that ever since I updated to Vortex 1.7.1 Beta yesterday, I have not been able to run skse64_loader.exe, SSEEdit, Bodyslide, or Nemesis. I have narrowed it down to programs that have the "Run this program as an administrator" checked in Properties > Compatibility. When I try to run them through Vortex and select "Yes" after the admin prompt....nothing happens.

 

I have (personally) always run all four as admin and can manually uncheck them. However,"skse64_loader.exe" actually requires the admin access ....so I can not run Skyrim through Vortex.

 

 

A few things I've noted:

- All of my other tools run ok with the update (not run as admin)

- If I uncheck the "Run this program as an administrator" box for SSEEdit, Bodyslide, or Nemesis they run fine through Vortex.

- I have been able to run "skse64_loader.exe" externally though.

 

 

FYI, In the log I always notice the following:

 

1. ".....child process exited with code: -ffc" (but even after googling I'm not exactly sure what "-ffc" is)

 

2. Vortex always creates a temp file in "C:\Users\....\AppData\Local\Temp" and tries to open it when a program is marked to "run as admin" (which I don't think is normal, but I'm no expert)

Link to comment
Share on other sites

why would you run them as admin?

You should never run any game or modding tool as admin. Doing so opens your PC up to security risks.

 

I run only those as admin to

 

1. prevent any type of blocked privileges to prevent errors (which I've had in the past)

2. to give myself some type of "Are you sure you want to open this?" (in case I change my mind last minute about opening an application)

 

 

I have never had to run SKSE as admin. For any version of Skyrim, including Skyrim VR. Nor for Fallout New Vegas.

 

 

Whenever I've tried to run it without admin access I get this message:

 

"Launching N:\....\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe failed (740). Please try running skse64_loader as an administrator."
..which is probably Windows Defender blocking it somehow if not run as admin.
_______________________________________________________________________________________
My method has always worked fine for me..
But since TanninOne replied to my bug report saying the following I guess it must me something on my end:
"If the windows admin prompt comes up then Vortex did start the application, Vortex is out beyond that point.

It's not possible for Vortex to monitor or get any further success/failure information about a process being run as admin, that's just how windows works. If the application then doesn't work or quits immediately that's not a Vortex problem."

Link to comment
Share on other sites

You should ensure, Steam, SKSE, the game and any other EXEs are all not running as admin. That SKSE error is caused because something was run as admin which now requires admin permissions for it to work properly. I'm not sure if there's much you can do to fix the admin privileges now that wouldn't involve manually resetting folder permissions for directories used by the tools.

 

If you install your game outside of Program Files, there's very rarely anything that will stop you and require admin elevation.

Link to comment
Share on other sites

Guest deleted34304850

running any program as admin is such a bad idea.

doing that to prevent issues that have occurred is such a bad idea.

 

sad to say that its taken vortex throwing errors to illustrate that there are serious deficiencies in your environment.

you should never use admin access as a workaround for anything. especially for modding tools which can come from various sources.

 

i hope you can figure this out on your system eventually and you get everything working correctly, but i would urge you, seriously, to review your method of running tools as admin.

Link to comment
Share on other sites

You should ensure, Steam, SKSE, the game and any other EXEs are all not running as admin. That SKSE error is caused because something was run as admin which now requires admin permissions for it to work properly. I'm not sure if there's much you can do to fix the admin privileges now that wouldn't involve manually resetting folder permissions for directories used by the tools.

 

If you install your game outside of Program Files, there's very rarely anything that will stop you and require admin elevation.

 

running any program as admin is such a bad idea.

doing that to prevent issues that have occurred is such a bad idea.

 

sad to say that its taken vortex throwing errors to illustrate that there are serious deficiencies in your environment.

you should never use admin access as a workaround for anything. especially for modding tools which can come from various sources.

 

i hope you can figure this out on your system eventually and you get everything working correctly, but i would urge you, seriously, to review your method of running tools as admin.

 

I appreciate all the help and insight. Thanks ppl!!

Link to comment
Share on other sites

Is there

 

 



 

I have never had to run SKSE as admin. For any version of Skyrim, including Skyrim VR. Nor for Fallout New Vegas.

 

 

Whenever I've tried to run it without admin access I get this message:

 

"Launching N:\....\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe failed (740). Please try running skse64_loader as an administrator."

Is there are reason there are two slash, "\\" characters in your path right before the executable name?

Link to comment
Share on other sites

  • 4 weeks later...

Is there are reason there are two slash, "\\" characters in your path right before the executable name?

Whenever I've tried to run it without admin access I get this message:

 

"Launching N:\....\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe failed (740). Please try running skse64_loader as an administrator."

 

 

no idea. that's just what the error message said. my paths look good.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...