-
-
Notifications
You must be signed in to change notification settings - Fork 783
NVDA does not warn about downgrading portable copies #18291
Copy link
Copy link
Closed
Labels
component/installerfeature/portableRelated to using NVDA as a non-installed, portable copy.Related to using NVDA as a non-installed, portable copy.p5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Metadata
Metadata
Assignees
Labels
component/installerfeature/portableRelated to using NVDA as a non-installed, portable copy.Related to using NVDA as a non-installed, portable copy.p5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for Bug.
Steps to reproduce:
Actual behavior:
NVDA notifies the user that there is already a copy of NVDA at that location, and asks them whether they would like to update it. The message reads:
Expected behavior:
The user should be shown a similar message to that shown when attempting to downgrade an installed copy of NVDA. For example:
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Portable
NVDA version:
Tested with NVDA 2024.4.2 and 2025.1.1.
Windows version:
Windows 11 Business Insider Preview Version 24H2 (OS Build 26200.5641) x64
Name and version of other software in use when reproducing the issue:
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.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes