i'm a little unclear on where to ask this. the system in question is a gigabyte ga-ep45-ud3p (p45/ich10) so i guess it does still qualify as retro status...

there is a lot of undiscerable slop online concerning win10 & midi that i've ignored over the years. i never thought i would ever have to deal with this as i run anything requiring winxp or later in wine/alsa, but now i'm forced to.

all i want is a single virtual midi loopback cable. i've installed both loopmidi and loopbe1 and, while neither report any errors, neither show up as a midi in/out target. the applications i'm using are fsmp and hairless midi serial bridge. the only midi target i ever see is microsoft gs wavetable synth. what is broken? is this some stupid permissions thing?

a few notes on my win10 22h2 system:
- 64bit, uefi, windows driver signing disabled
- windows defender stripped out (https://github.com/ionuttbara/windows-defender-remover)
- no windows midi service (whatever that is) in services.msc