You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I roled back from latest alpha - 22012... to alpha - 21810... via a portable copy I found next bug:
after I ran a portable copy and went to nvda menu, tools, install nvda on this computer, in the first dialog, which has been shown, there was missing a check box to copy portable config to this account. after installing nvda, I ran portable copy again and went to menu and again pressed install nvda to this computer and now checkbox appeared.
Steps to reproduce:
assuming, that portable copy with user configuration is already built, here are my steps:
uninstall nvda on system
reboot a system
delete nvda folder in my account /appdata/roming
run portable copy, which was previously created
on nvda menu, tools press install nvda on a system or something like that
Actual behavior:
at a first time checkbox to copy portable user config to this account is missing. it appears after nvda is installed on a system and portable copy is running again.
also found, that at the first time folder "system config" is missing in program files (x86)/nvda. is appears after second install too.
Expected behavior:
this checkbox should be presented at first time, when dialog shows.
System configuration
NVDA installed/portable/running from source:
portable and then installed (need both of them to replicate this problem)
NVDA version:
tested with 22012 and 21810. but probably this issue exist longer.
Windows version:
w10 20h2
Name and version of other software in use when reproducing the issue:
n/a
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.
reported in description
If add-ons are disabled, is your problem still occurring?
n/a (part of user config)
Did you try to run the COM registry fixing tool in NVDA menu / tools?
n/a
The text was updated successfully, but these errors were encountered:
This problem appeared back in NVDA 2020.4. The check box disappears if the %APPDATA%\nvda folder does not exist. If manually create this folder and restart NVDA portable copy, the check box will appear again.
Hello,
when I roled back from latest alpha - 22012... to alpha - 21810... via a portable copy I found next bug:
after I ran a portable copy and went to nvda menu, tools, install nvda on this computer, in the first dialog, which has been shown, there was missing a check box to copy portable config to this account. after installing nvda, I ran portable copy again and went to menu and again pressed install nvda to this computer and now checkbox appeared.
Steps to reproduce:
assuming, that portable copy with user configuration is already built, here are my steps:
Actual behavior:
at a first time checkbox to copy portable user config to this account is missing. it appears after nvda is installed on a system and portable copy is running again.
also found, that at the first time folder "system config" is missing in program files (x86)/nvda. is appears after second install too.
Expected behavior:
this checkbox should be presented at first time, when dialog shows.
System configuration
NVDA installed/portable/running from source:
portable and then installed (need both of them to replicate this problem)
NVDA version:
tested with 22012 and 21810. but probably this issue exist longer.
Windows version:
w10 20h2
Name and version of other software in use when reproducing the issue:
n/a
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.
reported in description
If add-ons are disabled, is your problem still occurring?
n/a (part of user config)
Did you try to run the COM registry fixing tool in NVDA menu / tools?
n/a
The text was updated successfully, but these errors were encountered: