Jump to content

Getting "Startup failed" error when launching Vortex


zachypoobear

Recommended Posts

As the title says, I'm getting a "Startup failed" error when trying to launch vortex. The error message says Vortex seems to be running and to check task manager. Obviously, I checked task manager and there are no processes from Vortex running, so there is nothing for me to close out.

 

Restarting my computer, uninstalling reinstalling Vortex, and running Vortex as admin all don't solve the issue.

 

Any idea as to what could be causing this, and how to fix it? Fortunately, I had already modded my target game, but would like to be able to update mods in the future through Vortex.

Link to comment
Share on other sites

Guest deleted34304850

you shouldn't run vortex as admin - or any program for that matter. i'd bet dollars to donuts thats your root cause.

Link to comment
Share on other sites

you shouldn't run vortex as admin - or any program for that matter. i'd bet dollars to donuts thats your root cause.

I normally don't ever run programs as admin, just trying it as a troubleshooting step. and no, this is not the cause as the issue persists while not running in admin. As a side note, not sure what your opposition to running a program as admin is. All it does really is ignore any permissions to run. It's a pretty common troubleshooting step for a program not running correctly as Windows can be weird about permissions at times.

 

Try restarting your PC. That usually clears anything like this

As I stated in my post, I did try restarting my PC, several times I might add, and no luck.

 

I appreciate both of your feedback, but unfortunately neither suggestions work.

Link to comment
Share on other sites

Guest deleted34304850

 

you shouldn't run vortex as admin - or any program for that matter. i'd bet dollars to donuts thats your root cause.

I normally don't ever run programs as admin, just trying it as a troubleshooting step. and no, this is not the cause as the issue persists while not running in admin. As a side note, not sure what your opposition to running a program as admin is. All it does really is ignore any permissions to run. It's a pretty common troubleshooting step for a program not running correctly as Windows can be weird about permissions at times.

that's empiracally false. windows is fine with permissions, its users who are weird about how they work.

if you run a program as admin - it gets allsorts of lovely permission to do allsorts of lovely things such as compromise your data. that's my opposition (and everyone else's who understands how this stuff works), opposition. and it is never, not ever, considered to be a "troubleshooting" step.

but what do i know, i only do this for a living............

Link to comment
Share on other sites

 

 

you shouldn't run vortex as admin - or any program for that matter. i'd bet dollars to donuts thats your root cause.

I normally don't ever run programs as admin, just trying it as a troubleshooting step. and no, this is not the cause as the issue persists while not running in admin. As a side note, not sure what your opposition to running a program as admin is. All it does really is ignore any permissions to run. It's a pretty common troubleshooting step for a program not running correctly as Windows can be weird about permissions at times.

that's empiracally false. windows is fine with permissions, its users who are weird about how they work.

if you run a program as admin - it gets allsorts of lovely permission to do allsorts of lovely things such as compromise your data. that's my opposition (and everyone else's who understands how this stuff works), opposition. and it is never, not ever, considered to be a "troubleshooting" step.

but what do i know, i only do this for a living............

 

While I'm not sure I would be worried about Vortex compromising my data (although nowadays, who can be too sure about anything), I do see your point.

 

Regardless, I had never run Vortex as admin before the one time I did after I got this error mentioned. Hence why running as admin could not possibly be the cause for this error as running normally causes the error as well.

 

It's a very strange issue as I can't understand why Vortex would think it's already running when it clearly isn't, at least from what I can tell anyway.

Link to comment
Share on other sites

  • 4 months later...
  • 1 month later...

Archived

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

  • Recently Browsing   0 members

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