Brief summary
RuntimeError: Attempting to open multiple IncompatibleAddonsDialog instances when installing add-on with minimumNVDAVersion > current NVDA version
Steps to reproduce
- Current NVDA version: 2025.3.1.
- Attempt to install the following add-on:
Actual behavior
The installation fails and throws an unhandled exception in the log.
Log Snippet:
IO - speech.speech.speak (06:25:22.456) - MainThread (2700):
Speaking ['日志片段开始点已标记，再按一次复制到剪贴板']
IO - inputCore.executeGesture (06:25:23.783) - winInputHook (8232):
Input: kb(laptop):enter
DEBUG - RPC process 5432 (nvda_slave.exe) (06:25:24.079) - Dummy-9 (3360):
languageHandler.setLocale:
Win32 locale string from locale code is Chinese (Simplified)_China.936
DEBUG - RPC process 5432 (nvda_slave.exe) (06:25:24.101) - Dummy-9 (3360):
languageHandler._setPythonLocale:
set python locale to Chinese (Simplified)_China.936
DEBUG - NVDAHelper.nvdaControllerInternal_installAddonPackageFromPath (06:25:24.121) - Dummy-9 (3360):
Requesting installation of add-on from D:\MyData\Download\SentenceNav-2.14.2.nvda-addon
DEBUG - gui.contextHelp.bindHelpEvent (06:25:24.137) - MainThread (2700):
Did context help binding for ErrorAddonInstallDialog
ERROR - unhandled exception (06:25:24.153) - MainThread (2700):
Traceback (most recent call last):
File "wx\core.pyc", line 3427, in <lambda>
File "gui\addonGui.pyc", line 285, in handleRemoteAddonInstall
File "gui\addonGui.pyc", line 151, in installAddon
File "gui\addonStoreGui\controls\messageDialogs.pyc", line 247, in _showAddonRequiresNVDAUpdateDialog
File "gui\addonGui.pyc", line 90, in __init__
File "gui\nvdaControls.pyc", line 331, in __init__
File "gui\message.pyc", line 466, in __init__
File "gui\addonGui.pyc", line 116, in _addButtons
File "gui\addonGui.pyc", line 320, in __init__
RuntimeError: Attempting to open multiple IncompatibleAddonsDialog instances
IO - inputCore.executeGesture (06:25:25.045) - winInputHook (8232):
Input: kb(laptop):NVDA+shift+control+f1
Expected behavior
NVDA should immediately show the incompatibility warning/installation prompt for the SentenceNav add-on currently being installed.
NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy
NVDA version
2025.3.1
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
Windows version
Windows 10 22H2 (AMD64) build 19045.6466
Name and version of other software in use when reproducing the issue
None
Other information about your system
None
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs
Brief summary
RuntimeError: Attempting to open multiple IncompatibleAddonsDialog instanceswhen installing add-on withminimumNVDAVersion> current NVDA versionSteps to reproduce
minimumNVDAVersion: 2026.1 (Higher than current NVDA).Actual behavior
The installation fails and throws an unhandled exception in the log.
Log Snippet:
Expected behavior
NVDA should immediately show the incompatibility warning/installation prompt for the
SentenceNavadd-on currently being installed.NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy
NVDA version
2025.3.1
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
Windows version
Windows 10 22H2 (AMD64) build 19045.6466
Name and version of other software in use when reproducing the issue
None
Other information about your system
None
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs