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

Jump to bottom

userConfig directory automatically gets copied to installation directory for non-portable installs #2891

Closed
nvaccessAuto opened this issue Dec 22, 2012 · 2 comments
Closed

userConfig directory automatically gets copied to installation directory for non-portable installs #2891

nvaccessAuto opened this issue Dec 22, 2012 · 2 comments
Labels
bug component/installer

Comments

@nvaccessAuto
Copy link

Reported by elliott94 on 2012-12-22 23:43
If installed from the launcher package, it seems that the userConfig directory is automatically copied to the installation directory during the install. Since this is only used for portable versions, is their any other reason it's included? This doesn't occur if using the launcher to upgrade an already installed version, i.e. that was installed using the old installer.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-12-01 05:45
Can you still reproduce this? If so, do you mean you end up with a userConfig directory in your Program Files\nvda directory? Note that you'll need to delete any existing userConfig directory before testing this again, as the installer won't remove anything it doesn't know about.

@nvaccessAuto
Copy link
Author

Comment 2 by elliott94 (in reply to comment 1) on 2015-07-13 07:13
Replying to jteh:

Can you still reproduce this? If so, do you mean you end up with a userConfig directory in your Program Files\nvda directory? Note that you'll need to delete any existing userConfig directory before testing this again, as the installer won't remove anything it doesn't know about.

No; this no longer seems to occur. Closing as fixed.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug component/installer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nvaccessAuto