Edit._get_ITextDocumentObject raises OSError (E_FAIL) on RICHEDIT50W controls (regression from 2025.3)

[dnz3d4c]

Brief summary

When focusing on a RICHEDIT50W edit control, NVDA 2026.1beta2 logs an ERROR in NVDAObjects.window.edit.Edit._get_ITextDocumentObject with OSError: [WinError -2147467259] (E_FAIL). This error does not occur in NVDA 2025.3 stable. No functional impact was observed — the error is only logged, and speech/navigation continue to work — but the traceback indicates a regression in how NVDA obtains the ITextDocument COM interface from RichEdit controls.

Steps to reproduce

1. Open any application that contains a RICHEDIT50W edit control
2. Start NVDA 2026.1beta2 with --disable-addons --debug-logging
3. Focus on the RICHEDIT50W edit field
4. Check the NVDA log

Actual behavior

The log contains:

ERROR - NVDAObjects.window.edit.Edit._get_ITextDocumentObject (16:03:59.371) - MainThread (27800):
Error getting ITextDocument
Traceback (most recent call last):
  File "NVDAObjects\window\edit.pyc", line 1055, in _get_ITextDocumentObject
  File "_ctypes/callproc.c", line 1033, in GetResult
OSError: [WinError -2147467259] unspecified error

NVDA speech works normally; no user-facing error sound or disruption.

Expected behavior

No ERROR should be logged when focusing on a standard RICHEDIT50W control. NVDA 2025.3 stable handles the same control without this error.

NVDA logs, crash dumps and other attachments

debugLog.txt

NVDA type

installed copy

NVDA version

2026.1 beta2

Have you tried any other versions of NVDA? If so, please report their behaviors.

NVDA 2025.3.1 No error sound

Windows version

Windows vversion 25H2(OS build 26200.7840)

Name and version of other software in use when reproducing the issue

No response

Other information about your system

No response

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