Brief summary

Unlike when connecting to a remote computer as a leader, if an error occurs while attempting to connect as the controlled computer, NVDA does not notify the user about the failure. It only logs it.

Steps to reproduce

1. Start NVDA.
2. Open the connection dialog.
3. Select “Control another computer” as the mode.
4. Fill in the “Host” and “Key” fields.

At this point, you’ll get an error: “Unable to connect to the remote computer.”

6. Repeat step 2.
7. Select the mode “Allow this computer to be controlled.”
8. Fill in the “Host” and “Key” fields.

You’ll notice that the user does not receive an error message indicating that the connection failed — it’s only recorded in the log.

Actual behavior

The user is not notified if connecting as the controlled computer fails.

Expected behavior

Just like when establishing a connection to a remote computer, the user should be notified if connecting as the controlled computer fails.

NVDA logs, crash dumps and other attachments

nvda.log

NVDA type

installed copy

NVDA version

alpha-53084,43dfc2ea (2026.1.0.53084)

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

No.

Windows version

Windows 11 24H2 (AMD64) build 26100.6725

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 not run the COM Registration Fixing Tool