I want to run Vortex as admin (Please fix this.)

[Malevolution]

Vortex is... unique enough without this.

 

I have never heard of an application having a problem with being granted too many permissions -- much less, explicitly stating that any permissions-related issues are the user's fault (!) because the application is given permissions.

 

Thank you for your time.

 

Please fix this.

[Pickysaurus]

Why do you feel you need to run Vortex as admin?

 

Providing unnecessary rights to applications puts massive security holes in your system.

 

No game, game store, or gaming tool should ever be run as admin unless it has a very good reason.

[Malevolution]

Greetings:

 

Thanks for your reply!

 

I said nothing of feelings / needs, and while I respect your opinions, they are not germane. The issue is Vortex's inability to run properly when given adminstrative privileges.

Let me put it this way. No software that I have ever encountered in my considerable experience has had an issue with being run as an administrator. I've also never seen a warning upon installation that granting administrative privileges may cause problems -- much less a nasty, explicitly accusatory warning.

Why not just fix the software instead of making excuses and accusations? Is it that it's easier to do the latter, or that development is incapable of doing the former?

[showler]

Counter-point: Please do not make this software, that is explicitly designed to install community made content, be able to have administrator privileges.

[Pickysaurus]

I agree the message isn't great, it's potentially a holdover from very early in development, however, the point is, there's no good reason to run Vortex as admin.

 

The problems we allude to are things like this:
1. Run Vortex as admin
2. Vortex creates or modifies files with admin privileges
3. Run Vortex as intended

4. Vortex can no longer function properly as core files are now associated with an administrator level of permissions.

 

This kind of thing, on top of Showler's point about community content are good reasons not to run as admin.

 

We make every effort to ensure the mods you download are safe, but we cannot 100% promise that everything on the site is safe as malicious actors find new and exciting ways to evade detection.

[Malevolution]

Greetings:

 

Thanks again for getting back to me! :cool:

 

I agree the message isn't great, it's potentially a holdover from very early in development

 

 

"Isn't great?" That's way too mild a critique, but at least we're making progress. :happy:

 

It also isn't a "holdover." I've installed (and attempted to use) Vortex several times throughout its development -- since beta through 1.0 and beyond -- and have never before seen this message.

 

At any rate... I'm not explicitly running Vortex as an administrator. Rather, my user account is that of an administrator, because:

1. I know what I'm doing and accept the "risks."
2. Many of the tasks I routinely perform require administrative privileges
3. Many of the software titles I routinely use require administrative privileges

Honestly, I really don't care that development can't, or can't be arsed to, solve a problem of their own making. All I want is a workaround to ensure that Vortex can work properly given this bug.

 

If you could tell me how to force Vortex to be run, by an administrator, without administrative privileges, we'll be in business. I think the answer can be found in the executable's Properties under the Security tab, but I'm not sure specifically what modifications I need to make here. Given Vortex's fragility, I figured I'd ask first.

 

Thanks again for your time!

[Pickysaurus]

Greetings:

 

Thanks again for getting back to me! :cool:

 

I agree the message isn't great, it's potentially a holdover from very early in development

 

 

"Isn't great?" That's way too mild a critique, but at least we're making progress. :happy:

 

It also isn't a "holdover." I've installed (and attempted to use) Vortex several times throughout its development -- since beta through 1.0 and beyond -- and have never before seen this message.

 

At any rate... I'm not explicitly running Vortex as an administrator. Rather, my user account is that of an administrator, because:

1. I know what I'm doing and accept the "risks."
2. Many of the tasks I routinely perform require administrative privileges
3. Many of the software titles I routinely use require administrative privileges

Honestly, I really don't care that development can't, or can't be arsed to, solve a problem of their own making. All I want is a workaround to ensure that Vortex can work properly given this bug.

 

If you could tell me how to force Vortex to be run, by an administrator, without administrative privileges, we'll be in business. I think the answer can be found in the executable's Properties under the Security tab, but I'm not sure specifically what modifications I need to make here. Given Vortex's fragility, I figured I'd ask first.

 

Thanks again for your time!

 

 

We actually have a task in the backlog to review common error messages and update the text, this one isn't really a common error but should be updated all the same. It is a holdover in that so few people run Vortex as admin, it almost never comes up as a problem. Quite impressive considering the size of the userbase!

 

While I understand that you know the risks and will do what you want with your own PC, that doesn't take away from the original statement. Vortex, games, game store and modding tools have no business running as admin in most cases. Doing so opens security holes and while you may be happy with the consequences of your actions, I'm sure you'd be quite annoyed if somehow a malicious mod exploited the elevated process status and locked you out of your own PC - or worse.

 

 

If you're not deliberately running it as admin (i.e. right click -> run as admin), then it means you've made the decision to turn off User Account Control (UAC), this isn't recommended by anyone as it runs every single app as admin. Think of how systems like Windows 2000 used to work.

 

https://learn.microsoft.com/en-us/windows/security/identity-protection/user-account-control/user-account-control-overview

 

As someone who used to repair PCs for a living, the very idea of someone running everything as admin makes me wince.

[showler]

Simple solution: Make a non-administrator account and take the thirty seconds required to switch when starting your gaming.

[Guest deleted34304850]

Vortex is... unique enough without this.

 

I have never heard of an application having a problem with being granted too many permissions -- much less, explicitly stating that any permissions-related issues are the user's fault (!) because the application is given permissions.

 

Thank you for your time.

 

Please fix this.

what is it, exactly, you want "fixing"?

i'd suggest you need to "fix" your understanding of why running anything as admin is a bad idea and then see how you go.

[Malevolution]

Simple solution: Make a non-administrator account and take the thirty seconds required to switch when starting your gaming.

 

Right. I'm totally going to alter my entire operating system for one software title that can't handle adulthood.

 

Do you hear what you're saying here? Seriously. Vortex is the only software title that I have ever used that has issues with being granted administrative privileges.

 

Edit: It's extraordinary to me that every reply is either accusatory, makes excuses, or both. I'm gobsmacked. Y'all are essentially saying that you know this is a bug, you know development can't (be arsed to) fix it, and instead of handling this issue like one human being to another, done little but make excuses and direct hatred toward the person pointing out the problem.

 

Speaking of adulthood... Is shame something that is utterly absent those born either during, or at the cusp, of the 21st century?