Using RDP the remote session does not see all ports but using Chrome Remote Access the remote session sees all ports

Question

I have a program on the remote (Windows 11 Pro (10.0.22631 Build 22631) that scans for MIDI ports.

Besides the general Microsoft GS Wavetable Synth MIDI, there is another MIDI driver that supplies an IN and an OUT MIDI port. The device manager sees this even using RDP.

The program uses WinMM midi[In/Out]GetNumDevs() and midi[In/Out]GetDevCaps() to scan for MIDI ports. When run using RDP, Only the Microsoft GS Out port is seen. When using Chrome Remote,
the Microsoft GS Out port is seen as well as the other driver's IN and OUT MIDI ports. (The ports are seen when directly logged on to the remote computer as well, so it's clearly a RDP related issue.)I also have a 3rd party program that looks for MIDI IN ports. When run via RDP, it also does not find
the MIDI port, but when run directly on the remote computer, or using Chrome Remote, it does see the MIDI port.

Since the programs are running on the remote computer where the port in question is located, I don't see why starting the program via an RDP connection should have any bearing on the issue.

Answer 1

Hello,

When you are using mstsc, you can expand "show options" -> "local resources" , and try to configure your device redirection and confirm if it will help.

---

If the Answer is helpful, please click "Accept Answer" and upvote it.