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

Can not copy settings to system profile [fresh install] #9448

Closed
feerrenrut opened this issue Apr 3, 2019 · 3 comments
Closed

Can not copy settings to system profile [fresh install] #9448

feerrenrut opened this issue Apr 3, 2019 · 3 comments
Assignees
Milestone

Comments

@feerrenrut
Copy link
Member

@feerrenrut feerrenrut commented Apr 3, 2019

Steps to reproduce:

  1. Uninstall NVDA
  2. Remove user profile from %appdata%/nvda
  3. Remove system configuration profile from C:\Program Files (x86)\NVDA\systemConfig
  4. Install NVDA
  5. Attempt to "Use currently saved settings on the logon and other secure screens (requires administrator privileges)" (button on the general settings panel [NVDA+control+g])

Actual behavior:

An error sound is heard, and the following error in the log:

ERROR - unhandled exception (18:46:34.341):
Traceback (most recent call last):
  File "gui\settingsDialogs.pyc", line 730, in onCopySettings
WindowsError: [Error 3] The system cannot find the path specified: u'C:\\Users\\Reef\\AppData\\Roaming\\nvda\\appModules\\*.*'

Expected behavior:

The configuration should be copied to the system profile.

System configuration

NVDA installed/portable/running from source: Installed

NVDA version:

2019.1

Windows version:

Windows 10

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA?

2018.4 - The issue does not occur

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Apr 3, 2019

@feerrenrut
Copy link
Member Author

@feerrenrut feerrenrut commented Apr 3, 2019

Thanks Joseph. Yep, I have a fix on it's way.

@ehollig
Copy link
Collaborator

@ehollig ehollig commented Apr 23, 2019

Closing as fixed in #9449

@ehollig ehollig closed this Apr 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants