Steps to reproduce:

1. Start NVDA and enable Remote Access.
2. Connect to the locally hosted server, allow this computer to be controlled. Use any key you like.
3. Wait 5 minutes.
4. Go to tools, view log, and check the log output, which will likely be on the last line.

Actual behavior:

Within the log, messages like this are received:

WARNING - logging.Logger.warn (07:19:52.888) - Thread-3_connector_loop (13428):
Received message with unhandled type: ping {}

My log was in debug mode to see if more information could be logged, so the message response may be slightly different.

Expected behavior:

This should quietly be ignored or logged under debug level, as via the server spec as documented in comments, periotic pings are sent to verify connection health. This should be a known type, and since they are one way pings via the servers commented docs, no warning should be entered into the log, since it is expected and should be a known, not an unknown type.

NVDA logs, crash dumps and other attachments:

Relevant log entry is above.

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

2025.2

Windows version:

Windows 11 24H2

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

None, only NVDA.

Other information about your system:

This was tested on two different systems with different hardware specifications with the same results, both running Windows 11. I have tested this on remotely hosted relay servers, only those that send ping type have warnings entered into the log, and the locally hosted server always sends ping types, and thus always warns of an unknown type.

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.

2025.1 and other stable NVDA releases with Remote Access built in, they all have the same behavior.

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?

Untested, but likely not relevant here.

Final comments

This could probably be a developer facing change as well, but since it is noticeable by anyone viewing the log, I've placed this in the bug report category for the moment.