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

Important error in NVDA2020.4RC1: The "Copy portable configuration to current user account" checkbox is missing when installing a portable copy on a computer that has never installed NVDA #12071

Closed
cary-rowen opened this issue Feb 13, 2021 · 5 comments · Fixed by #12076
Milestone

Comments

@cary-rowen
Copy link
Contributor

Steps to reproduce:

  1. Run the installed NVDA and create a portable version.
  2. Check the "Copy current user configuration" option.
  3. Uninstall the installed NVDA and make sure there is no nvda directory in %appdata% after uninstalling.
  4. Run the portable copy created in (1) and select "Install NVDA" under the "Tools" menu.
    PS: You can also omit (3) and install the created portable copy in Windows Sandbox.

Special attention is needed to ensure that there is no NVDA directory in %appdata%

Actual behavior:

"Copy portable configuration to current user account" is missing.

Expected behavior:

"Copy portable configuration to current user account" is displayed normally and can be checked.

System configuration

NVDA installed/portable/running from source:

only portable version

NVDA version:

NVDA2020.4RC1, alpha-21753

Windows version:

Windows 10 20H2 (64-bit) build 19042.746

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 computer?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

alpha-21753

If addons are disabled, is your problem still occuring?

yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

none

@ABuffEr
Copy link
Contributor

ABuffEr commented Feb 13, 2021

Hi,
I confirm to have noticed this issue some alpha versions ago, thanks @cary-rowen for investigation and STR.

@LeonarddeR
Copy link
Collaborator

Just to make sure, is this a regression in 2020.4?

@LeonarddeR
Copy link
Collaborator

Related to #9679

@cary-rowen
Copy link
Contributor Author

I am not sure if this is a regression of pr9679, this problem has not been reproduced on nvda2020.3.
@lukaszgo1 @LeonarddeR @feerrenrut Can you comment on this?

@feerrenrut
Copy link
Contributor

If the issue does not show up in 2020.3 then it is a regression, I haven't verified this. That said, given the late stage of discovery I don't think this is serious enough to delay the release.

feerrenrut added a commit that referenced this issue Apr 21, 2021
Related PR #9679
Fixes #12071
Fixes #12205 

Co-authored-by: Reef Turner <reef@nvaccess.org>
@nvaccessAuto nvaccessAuto added this to the 2021.1 milestone Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants