Traceback when starting NVDA with this add-on installed

[Neurrone]

On the server running remote desktop, I have NVDA 2025.1 installed along with this add-on. I see the following message when starting it:

INFO - external:globalPlugins.rdAccess.RDGlobalPlugin.__init__ (22:02:29.424) - MainThread (10464):
Initializing rdAccess version 1.5.0
ERROR - external:addons.rdAccess.lib.rdPipe.execRegsrv (22:02:29.444) - MainThread (10464):
Error calling 'C:\\WINDOWS\\Sysnative\\regsvr32.exe' with arguments ['/s', '/i:"rc NVDA-BRAILLE NVDA-SPEECH"', '/n', 'C:\\Users\\Dickson\\AppData\\Roaming\\nvda\\addons\\rdAccess\\dll\\rd_pipe_amd64.dll']
Traceback (most recent call last):
  File "C:\Users\Dickson\AppData\Roaming\nvda\addons\rdAccess\lib\rdPipe.py", line 79, in execRegsrv
    subprocess.check_call([regsvr32, *params], startupinfo=startupInfo)
  File "subprocess.pyc", line 413, in check_call
subprocess.CalledProcessError: Command '['C:\\WINDOWS\\Sysnative\\regsvr32.exe', '/s', '/i:"rc NVDA-BRAILLE NVDA-SPEECH"', '/n', 'C:\\Users\\Dickson\\AppData\\Roaming\\nvda\\addons\\rdAccess\\dll\\rd_pipe_amd64.dll']' returned non-zero exit status 3.

I also get an error when attempting to change the synthesizer to remote speech stating that it couldn't be started.

[Neurrone]

In case this matters, the RDP server is a Windows 11 VM.

Here is the diagnostic report.

{
	"configuration": {
		"operatingMode": 7,
		"enableCitrixSupport": false,
		"connectionNotifications": 3,
		"persistentRegistration": false,
		"enableRemoteDesktopSupport": true,
		"recoverRemoteSpeech": true,
		"driverSettingsManagement": false
	},
	"addonManifest": {
		"name": "rdAccess",
		"summary": "Remote Desktop Accessibility",
		"description": "Allows using speech and braille with Microsoft Remote Desktop, Citrix Workspace and VMware Horizon",
		"author": "Leonard de Ruijter <alderuijter@gmail.com>",
		"url": "https://github.com/leonardder/rdAccess",
		"version": "1.5.0",
		"docFileName": "readme.html",
		"minimumNVDAVersion": [
			2024,
			1,
			0
		],
		"lastTestedNVDAVersion": [
			2025,
			1,
			0
		],
		"updateChannel": "None",
		"brailleTables": {},
		"symbolDictionaries": {}
	},
	"nvda": {
		"version": "2025.1.2"
	},
	"rdPipe": {
		"availablePipes": []
	},
	"system": {
		"defaultArchitecture": "AMD64",
		"nvdaArchitecture": "x86",
		"isCitrixSupported": false,
		"isRunningOnSecureDesktop": false,
		"remoteSessionMetrics": true,
		"windowsVersion": "Windows 11 24H2 (10.0.26100) workstation AMD64"
	},
	"registry": {
		"currentUser": {
			"SOFTWARE\\Classes\\CLSID\\{D1F74DC7-9FDE-45BE-9251-FA72D4064DA3}": "[WinError 2] The system cannot find the file specified",
			"Software\\Microsoft\\Terminal Server Client\\Default\\AddIns\\RdPipe": "[WinError 2] The system cannot find the file specified",
			"SOFTWARE\\Citrix\\ICA Client\\Engine\\Configuration\\Advanced\\Modules\\DVCPlugin_RdPipe": "[WinError 2] The system cannot find the file specified",
			"SOFTWARE\\Citrix\\ICA Client\\Engine\\Configuration\\Advanced\\Modules\\DvcPlugins": "[WinError 2] The system cannot find the file specified"
		},
		"localMachine": {
			"SOFTWARE\\Classes\\CLSID\\{D1F74DC7-9FDE-45BE-9251-FA72D4064DA3}": "[WinError 2] The system cannot find the file specified",
			"Software\\Microsoft\\Terminal Server Client\\Default\\AddIns\\RdPipe": "[WinError 2] The system cannot find the file specified"
		}
	}
}

[LeonarddeR]

What error are you getting in the log when changing to remote speech?

[Neurrone]

That's weird, I tried to reproduce the problem but now its working fine again. I am getting the notifications that remote speech is connected now.

I'll close this for now until it happens again.

Thanks for this add-on. I found that with RDP, there is a very slight latency at high audio quality that this add-on gets rids of entirely.

I hope this approach would work from a Linux desktop to a client running NVDA, but I'd imagine that would be much harder.

[LeonarddeR]

I've seen that running the add-on for the first time can sometimes result in these tracebacks in the log. I'm not sure why that is. May be because it calls it too early.

[Neurrone]

It just happened for me again and I can't seem to get remote speech. The following error is logged when I try to switch to using it as the synthesizer:

ERROR - synthDriverHandler.setSynth (17:25:59.752) - MainThread (9296):
setSynth failed for remote
Traceback (most recent call last):
  File "synthDriverHandler.pyc", line 487, in setSynth
  File "synthDriverHandler.pyc", line 450, in getSynthInstance
  File "C:\Users\Dickson\AppData\Roaming\nvda\addons\rdAccess\synthDrivers\remote.py", line 61, in __init__
    super().__init__(port)
  File "C:\Users\Dickson\AppData\Roaming\nvda\addons\rdAccess\lib\driver\__init__.py", line 111, in __init__
    raise RuntimeError("No remote device found")
RuntimeError: No remote device found

[LeonarddeR]

I'm afraid you'll have to repro this with debug logging on. This will give you an enormous amount of logging though.

[LeonarddeR]

The \regsvr32.exe definitely means that the dll can't be found.

[Neurrone]

I can't seem to reproduce the issue everytime I try. This is a tricky one, it seems to happen randomly, but I'm unsure what triggers this.