-
-
Notifications
You must be signed in to change notification settings - Fork 783
NVDA does not speak after add-on installation until it is restarted #14525
Copy link
Copy link
Closed
Labels
bug/freezefeature/addon-storeFeatures / behavior of the add-on StoreFeatures / behavior of the add-on Storep2https://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.
Milestone
Metadata
Metadata
Assignees
Labels
bug/freezefeature/addon-storeFeatures / behavior of the add-on StoreFeatures / behavior of the add-on Storep2https://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 issues without a type.
Steps to reproduce:
Actual behavior:
After step 6., NVDA does not restart and does not speak anymore. Windows is responsive though. You need to press Yes again (with no vocal feedback) to have it restarted.
Also, the following error is found in the log:
Expected behavior:
NVDA should read the dialog box.
The error should not appear in the log.
NVDA logs, crash dumps and other attachments:
nvda-old.log
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2022.4
Windows version:
Windows 10 20H2 (AMD64) build 19042.2364
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
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.
Issue reproduced on the following older versions:
If NVDA add-ons are disabled, is your problem still occurring?
N/A but tested with two different add-ons, to exclude the possibility of an issue with the add-on.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested, unrelated.