Steps to reproduce:
- On a Windows machine with NVDA 2025.1 or 2025.2 beta (built-in Remote Access feature enabled and configured), go to Device Manager.
- Disable all audio output devices under "Sound, video and game controllers".
- Reboot the machine.
- Connect to this machine remotely from another computer using NVDA's built-in Remote Access.
Actual behavior:
The remote machine is controllable — for example, pressing Win+R or Win+E triggers the expected actions on the remote system.
However, no speech feedback is sent to the controlling computer, making it impossible to hear what is happening remotely.
Expected behavior:
Speech feedback should still be transmitted to the controller, even if the remote machine has no active audio output device.
This was the behavior with the [NVDA Remote add-on], where speech was transmitted independently of the host machine's audio status.
NVDA logs, crash dumps and other attachments:
Not applicable, since this is not a crash but a behavioral issue. Can provide logs upon request.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2025.1 stable and all 2025.2 betas (tested up to beta 4)
Windows version:
- Windows 10 24H2 (x64)
- Windows 11 24H2 (x64)
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Tested on multiple systems with different audio drivers, with consistent results.
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.
Yes, tested on:
- 2025.1 stable
- 2025.2 beta1 to beta4
All behave the same.
If NVDA add-ons are disabled, is your problem still occurring?
Yes. Only the built-in Remote Access feature is used.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Final note:
This regression might make remote support or usage scenarios more difficult, especially in cases where the remote machine has audio issues or missing drivers. This feature worked reliably in the older NVDA Remote add-on and would be highly beneficial to be supported natively as well.
Thank you for your attention.
Steps to reproduce:
Actual behavior:
The remote machine is controllable — for example, pressing Win+R or Win+E triggers the expected actions on the remote system.
However, no speech feedback is sent to the controlling computer, making it impossible to hear what is happening remotely.
Expected behavior:
Speech feedback should still be transmitted to the controller, even if the remote machine has no active audio output device.
This was the behavior with the [NVDA Remote add-on], where speech was transmitted independently of the host machine's audio status.
NVDA logs, crash dumps and other attachments:
Not applicable, since this is not a crash but a behavioral issue. Can provide logs upon request.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2025.1 stable and all 2025.2 betas (tested up to beta 4)
Windows version:
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Tested on multiple systems with different audio drivers, with consistent results.
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.
Yes, tested on:
All behave the same.
If NVDA add-ons are disabled, is your problem still occurring?
Yes. Only the built-in Remote Access feature is used.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Final note:
This regression might make remote support or usage scenarios more difficult, especially in cases where the remote machine has audio issues or missing drivers. This feature worked reliably in the older NVDA Remote add-on and would be highly beneficial to be supported natively as well.
Thank you for your attention.