For folks having issues due to loopMIDI, loopBE, etc not working in the current Windows MIDI Services release, we have a native in-box replacement in preview here:
We’re still working on the actual fix so that loopMIDI and similar will work, but that won’t be available until April/May at the earliest.
Pete
Microsoft
The thing is that loopMIDI is all over many external utilities and midi remotes, sometimes even hard-coded. And even when they’re not (eg. my scripts for the Arturia Keylab Mk2/Novation SL MK3) the user has to edit the proper js file to make things work with the new ports.
Nevertheless, the new loopback ports for the win midi services are most welcome 
Yes. Like I said, we’re still working on the actual fix, but that will take some time to get out. For hard-coded utilities (like rtpMIDI) that use the teVirtualMidi/loopMIDI driver, that will be especially important.
These also support arm64, which the third-party drivers do not.
In time, it’s my hope that tools and apps move to the new ports so we can cut down the complexity of setups (you can also copy our configuration files between PCs to give them the same port setup).
Many have found that giving them the same name as the loopMIDI ports, which this new loopback transport allows, makes they fully compatible. What exactly do you have to edit in the js files to switch over? Pretty much everything that uses the WinMM API on Windows today just uses port names as the identifiers.
Pete
Microsoft
Pretty basic stuff. See this:
I have obviously zero issues in updating this part of code for my shared remotes. Still, for users not into updating, I would have to turn them editing this part of the config script. Not a big deal, still not everyone is comfortable even with basic editing. Many musicians just want a setup done once and go.
I understand, still, there are setups that need time to reconfigure, and then there has to be a good reason for doing so. For example, I see no reason to turn my personal configurations which heavily rely on Bome MIDI Translator Pro, and a personal app which generates ports based on Bome’s SDK to change my ports at all.
I wasn’t being clear. You wouldn’t need to change those names. Shut down or uninstall loopMIDI so it’s not taking the names, and then create them in the MIDI Settings app:
What MIDI 1.0 apps see:
Pete
Microsoft
Also, so far in my testing, Bome works fine because it creates ports in a different way from teVirtualMidi (loopMIDI). Florian uses a bus driver in his.
Pete
Microsoft
Of course it does This is why I’ve noted that I see no reason to deal with these ones.
You were perfectly clear. So, users either would have to change the port names in my script (in case they adopt the new win ports and for whatever reason choose other naming for their ports, perhaps default names) or follow the procedure of removing (stop or uninstall) loopMIDI and then proceed in the MIDI Settings app to create ports with the same names. In either case a user editing something is needed. That being said, all this is just a temporary thing. Eventually, users will adapt
Looking forward to the signed driver so I can install. Since I am a heavy mouse user I am getting ready some apps like Chordie and old Bome mouse keyboard as I am never satisfied with current on-screen keyboards. 
This isn’t implemented as a driver. Just like the other loopbacks, app-to-app MIDI, and Network MIDI 2.0, it is a service plugin.
So you can install it if you want to, without turning off driver signing enforcement or similar.
But, entirely up to you.
Pete
Microsoft
It just says that I have to turn on dev mode for windows, that’s all.
thanks
Dev mode is just this:
We use it as a signal that you are ok installing unsigned plugins, because developers would normally need to do that.
But again, if you can wait, all good. This is more for people who are completely blocked right now.
I’ll have a preview of the full fix for loopMIDI and other dynamic devices released the same way, so customers can get it well before it goes into Windows.
Pete
Microsoft
Hello, for me LoopMIDI no longer works with my Sherlock touchscreen plugin.
I preferred to revert to version 24H2, hoping the problem will be resolved quickly.
It will take a few months to get the fix into retail Windows releases.
Pete
Microsoft
I use an SSL Nucleus that is controlled via ipMIDI. The Windows update KB5077181 causes a crash/blue screen when ipMIDI is started! If you uninstall the update, everything works fine again. I have now paused automatic Windows updates.
At the same time, I get a warning that paused updates are a security risk. That’s not satisfactory.
I’m not sure if the workaround described above also works with ipMIDI, and I don’t really understand the instructions above.
