Skip to content

NVDA Remote should keep retrying connection after startup failures instead of failing immediately #20122

@patrick-barboza

Description

@patrick-barboza

Brief summary

Actual behavior

In NVDA 2026.1, if the initial connection attempt fails because the network is not yet available, NVDA Remote immediately reports a connection error and stops trying to reconnect automatically.

The user must later reconnect manually.

Steps to reproduce

Steps to reproduce

  1. Configure NVDA Remote to connect automatically during Windows startup.
  2. Leave the computer at the Windows login screen (secure desktop).
  3. Start Windows in a situation where network access is not immediately available.
  4. Observe the behavior of NVDA Remote.

Actual behavior

Actual behavior

In NVDA 2026.1, if the initial connection attempt fails because the network is not yet available, NVDA Remote immediately reports a connection error and stops trying to reconnect automatically.

The user must later reconnect manually.

Expected behavior

Expected behavior

NVDA Remote should continue retrying the connection automatically for some time after an initial failure, similarly to the behavior observed in older versions such as NVDA 2025.3.3.

Ideally, this could be:

  • the default behavior again;
  • or an optional configurable setting;
  • or a retry/reconnect timeout option.

NVDA logs, crash dumps and other attachments

No response

NVDA type

installed copy

NVDA version

2026.1

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

No response

Windows version

Version 10.0.19045 Build 19045

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 System Accessibility Repair Tool (COM Registration Fixing Tool in older versions) in NVDA's tools menu?

I have run the System Accessibility Repair Tool and the issue still occurs

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions