Skip to content
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

Change default Installation location to User Profile Directory #5213

Closed
nvaccessAuto opened this issue Jul 13, 2015 · 1 comment
Closed

Change default Installation location to User Profile Directory #5213

nvaccessAuto opened this issue Jul 13, 2015 · 1 comment

Comments

@nvaccessAuto
Copy link

Reported by elliott94 on 2015-07-13 07:22
When a new install is performed using the launcher package, NVDA is currently installed under Program Files. On systems where the user in question does not necessarily have administrative privileges, in the future it could be considered to change this location to install by default to a user's profile folder (%appdata%). This would introduce several benefits, the biggest of which being that a user would be able to update an installed copy of NVDA without first gaining administrator privileges. Furthermore, using this approach would mean that all files relating to NVDA would be in a single location. I understand that having access to an administrative account would still be required for certain tasks (e.g. asking NVDA to start on the logon screen), but in corporate environments where it is possible to install NVDA as an administrator but then revert to an account without these privileges it would be beneficial to be able to update NVDA from within the software itself.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2015-07-13 07:39
Assistive technology products have to be installed into Program Files in order to gain the uiAccess privilege. Initially, this was only necessary to access apps running as admin, but it is being used for a growing number of things, including access to modern apps. Also, registering with Ease of Access (#308) requires administrator privileges. This might be fine for your average app, but I'm afraid it isn't reasonable for a screen reader.
Changes:
Added labels: wontfix
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant