MIDI input device not recognized

[BrianInTexas]

I have a working VPO built on Windows 10 LTSC and Hauptwerk.
I am trying to install and configure GO.
The MIDI input device is a Behringer FCA610. It's driver is installed and works with Hauptwerk.
When GO starts, it sees no MIDI input device.
Any suggestions?

[midimusic]

If your midi input device is already in use by Hauptwerk then you will not be able to use it for GO. A midi input device can only be opened once.

csw900

[oleg68]

@BrianInTexas could you post the screenshot of File->Settings-Midi here?

[oleg68]

I did, and the result is identical.

But the screenshot would be different with some additional information.

[BrianInTexas]

I did look at it, and it still said there are no midi devices for both input and output.
It honestly looked identical to me.
I am preparing the Win 11 upgrade file now.

[midimusic]

I will be surprised if upgrading to windows 11 makes any difference. If here really is a problem I suspect it is in the FCA610 driver.
csw900

[oleg68]

I did look at it, and it still said there are no midi devices for both input and output. It honestly looked identical to me. I am preparing the Win 11 upgrade file now.

The MIDI tab from recent GO versions has more fields containing some important information. So give me the screenshot exactly from 3.15.3-1.

[BrianInTexas]

Well. Win 11 was an interesting journey. I needed to do it anyway as part of deciding what to do with other computers.
Turns out, the real problem was Remote Desktop. While you are connected by Remote Desktop, MIDI devices are disabled from doing anything, including being seen by other software (i.e. GrandOrgue) that you are running. While using the computer in person, it works fine. So, I reverted back to the LTSC 2021 version, and it works the same way. I am not going to revert all the way to LTSC 2019, though.

The requested capture:

With LTSC the process count is 80, which is about half that of Win 11.

@midimusic was right about the FCA610 driver and Win 11. It is uninstallable on Win 11.

[BrianInTexas]

So the final answers are:

1. Any Remote Desktop connection to a Windows 10 or Windows 11 24H2 computer with MIDI devices results in the MIDI devices becoming unusable until the computer is rebooted.

2. Microsoft is currently working to overhaul the MIDI handling with a new version, apparently backwards compatible (1/0, and with a new (2.0) mode that is intended to eventually replace 1.0 and provide much higher performance and less weirdness.

https://devblogs.microsoft.com/windows-music-dev/windows-midi-services-oct-2024-update/

3. Windows 11 Pro does not look (to me) very suitable for use in a VPO to me. I am watching the progress of Windows 11 IoT LTSC.

4. Many MIDI devices have poor Windows support, mostly because Windows is not currently very friendly to MIDI.