Steps to reproduce:
- NVDA+ Ctrl +D to open the document format setting panel, uncheck "ReportComments" and "ReportHeadings", and then save the settings.
- In the "Use UI Automation to access Microsoft Word document controls" in the advanced settings panel, select "" "Default".
- Press Win+R and enter 'winword' to open MS Word and create a new "blank document".
Actual behavior:
MSWord crashes and quits, NVDA recovers from freeze.
P.S. This is only reproducible when Word uses object model, not UIA.
Expected behavior:
MSWord and NVDA both work fine.
NVDA logs, crash dumps and other attachments:
NVDA-log.txt
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.1, alpha-28430,3920fa58
Windows version:
Windows 10 22H2 (AMD64) build 19045.3086
Name and version of other software in use when reproducing the issue:
MSO (Version 2305 Build 16.0.16501.20074)
Other information about your system:
None
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
Steps to reproduce:
Actual behavior:
MSWord crashes and quits, NVDA recovers from freeze.
P.S. This is only reproducible when Word uses object model, not UIA.
Expected behavior:
MSWord and NVDA both work fine.
NVDA logs, crash dumps and other attachments:
NVDA-log.txt
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.1, alpha-28430,3920fa58
Windows version:
Windows 10 22H2 (AMD64) build 19045.3086
Name and version of other software in use when reproducing the issue:
MSO (Version 2305 Build 16.0.16501.20074)
Other information about your system:
None
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