-
-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Change Install Location & Remove UAC Requirement #1128
Comments
Being able to change the install location would also allow installing to a secondary drive where I won't keep losing all of my VRCX logs each time I do a clean Windows install, so I am all for this |
Install location isn't the same as database location, you can move your database by editing your |
Also the installer allows you to set a custom install location during first install, you can uninstall and install again without losing any data, this wont fix this issue regarding the UAC prompt but it is an option. |
I genuinely had no idea, it's good to know you can install to a different place and move the DB, guess I am not going to lose it anymore. Where is this documented btw? |
Ah, cheers! |
Explain in detail what your suggested feature would be used for.
Currently, the VRCX installer requires administrator privileges (UAC) and installs into
C:\Program Files\VRCX
, a system-wide directory. However, VRCX does not perform actions that require elevated permissions, such as modifying system settings or installing drivers.This feature request proposes modifying the installer to install VRCX in
%LocalAppData%\Programs\VRCX
, similar to how Discord and other modern applications operate. Doing so would:Even though this project is open source, that doesn’t justify requiring UAC if the application doesn’t actually need elevated permissions. On my system, I have a GPO policy enabled called "Require Trusted Path for Credential Entry", which makes it inconvenient to approve UAC prompts. Given that I rarely encounter UAC prompts for daily-use applications, it feels unnecessary in this case and more like an afterthought to package VRCX as an installable program rather than an actual requirement.
As always I am open to any counter arguments to my point.
The text was updated successfully, but these errors were encountered: