Add support for Windows App

[scottm-levelaccess]

Remote Access is not working when using the Windows App instead of Remote Desktop. The Windows App supports virtual channels and I can successfully use Freedom Scientific's products in remote access mode using the Windows App.

[LeonarddeR]

This is interesting. I'm pretty sure that I tested with Windows App in the past. Have you also tried the modern Remote Desktop app?

[scottm-levelaccess]

Yes I’ve tried with the modern RDP app and it works but since MS is in the process of deprecating the app (they’ve already removed the store version and will be phasing out the MSI version in February 2026) and pushing the Windows App I would like to get this working for my users. I’ve tested with Jaws and the Windows App and it is able to communicate and works as expected but NVDA with the add-on does not. This setup does work correctly with the RDP app so either the add-on doesn’t support the Windows App or there is some security setting blocking something but I doubt that since Jaws is working with the same setup. FWIT I am testing this with a Windows 365 machine but we also use AVD VMs as well From: Leonard de Ruijter ***@***.***> Sent: Wednesday, September 17, 2025 11:50 AM To: LeonarddeR/rdAccess ***@***.***> Cc: Scott McCormack ***@***.***>; Author ***@***.***> Subject: Re: [LeonarddeR/rdAccess] Add support for Windows App (Issue #39) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. [https://avatars.githubusercontent.com/u/3049216?s=20&v=4]LeonarddeR left a comment (LeonarddeR/rdAccess#39)<#39 (comment)> This is interesting. I'm pretty sure that I tested with Windows App in the past. Have you also tried the modern Remote Desktop app? — Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AW3QJK2MOWUJC7E42T3DNCL3TF7KDAVCNFSM6AAAAACGYXKCN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBTGYYTONRUGE>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[LeonarddeR]

Could you share some additional info?

• On what OS are you, I assume Windows 11? Are you using an Arm64 system by any chance?
• I hope you are somewhat comfortable with the registry editor (regedit). Could you share what subkeys you have under the following registry paths:
  • HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns
  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\Addins, if it exists

[scottm-levelaccess]

Yes Windows 11 x64 (not ARM) No HKLM addin keys Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\JAWS Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\JAWS32 Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\RDPDR Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\RDPDR\HP Color LaserJet Pro M478f-9f [02D3F9] (Fax) Key Name: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\RDPDR\HP LaserJet 400 colorMFP M475dn (D52B0C) From: Leonard de Ruijter ***@***.***> Sent: Wednesday, September 17, 2025 4:04 PM To: LeonarddeR/rdAccess ***@***.***> Cc: Scott McCormack ***@***.***>; Author ***@***.***> Subject: Re: [LeonarddeR/rdAccess] Add support for Windows App (Issue #39) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. [https://avatars.githubusercontent.com/u/3049216?s=20&v=4]LeonarddeR left a comment (LeonarddeR/rdAccess#39)<#39 (comment)> Could you share some additional info? * On what OS are you, I assume Windows 11? Are you using an Arm64 system by any chance? * I hope you are somewhat comfortable with the registry editor (regedit). Could you share what subkeys you have under the following registry paths: * HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns * Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\Addins, if it exists — Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AW3QJK2VZ2OIUGFGGCM47AT3TG5DDAVCNFSM6AAAAACGYXKCN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBUGQYDENJZGU>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[LeonarddeR]

This is interesting, it seems that HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RdPipe is missing.

In the remote desktop accessibility section of NVDA Settings, could you enable Persist client support when exiting NVDA and give NVDA an extra restart, then have another look to see if the registry key exists? May be there's something wrong with registration.
The persist option makes the add-on behave similar to JAWS in this way that the registry key isn't wiped when NVDA exits. This is only possible on an installed copy of NVDA.

[scottm-levelaccess]

Should I do this on both the local and remote ends? From: Leonard de Ruijter ***@***.***> Sent: Wednesday, September 17, 2025 4:37 PM To: LeonarddeR/rdAccess ***@***.***> Cc: Scott McCormack ***@***.***>; Author ***@***.***> Subject: Re: [LeonarddeR/rdAccess] Add support for Windows App (Issue #39) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. [https://avatars.githubusercontent.com/u/3049216?s=20&v=4]LeonarddeR left a comment (LeonarddeR/rdAccess#39)<#39 (comment)> This is interesting, it seems that HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RdPipe In the remote desktop accessibility section of NVDA Settings, could you enable Persist client support when exiting NVDA and give NVDA an extra restart, then have another look to see if the registry key exists? May be there's something wrong with registration. The persist option makes the add-on behave similar to JAWS in this way that the registry key isn't wiped when NVDA exits. This is only possible on an installed copy of NVDA. — Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AW3QJK5DXXYLOZ33IYLN2KD3THA75AVCNFSM6AAAAACGYXKCN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBUGQ4TANRYGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[scottm-levelaccess]

There is a visual glitch with the settings dialog:The Open RDPipe Log… button is sitting between the Persist client support and Enable default Remote Desktop support checkboxes and partially covers up the Enable support checkbox until it gets focus. Here is a screenshot if needed. ***@***.*** From: Leonard de Ruijter ***@***.***> Sent: Wednesday, September 17, 2025 4:37 PM To: LeonarddeR/rdAccess ***@***.***> Cc: Scott McCormack ***@***.***>; Author ***@***.***> Subject: Re: [LeonarddeR/rdAccess] Add support for Windows App (Issue #39) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. [https://avatars.githubusercontent.com/u/3049216?s=20&v=4]LeonarddeR left a comment (LeonarddeR/rdAccess#39)<#39 (comment)> This is interesting, it seems that HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RdPipe In the remote desktop accessibility section of NVDA Settings, could you enable Persist client support when exiting NVDA and give NVDA an extra restart, then have another look to see if the registry key exists? May be there's something wrong with registration. The persist option makes the add-on behave similar to JAWS in this way that the registry key isn't wiped when NVDA exits. This is only possible on an installed copy of NVDA. — Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AW3QJK5DXXYLOZ33IYLN2KD3THA75AVCNFSM6AAAAACGYXKCN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBUGQ4TANRYGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>