Loop Midi hidden in Windows 11 25H2 fix

Cubase
1

This is for those who are using loop Midi virtual ports.

I understand that Microsoft is gradually rolling out the new MIDI 2.0 driver as part of a Windows update. Since this is a major change to the MIDI infrastructure, it’s being deployed in batches. It’s possible that in some cases the new MIDI stack may cause loopMIDI to fail, while others may not yet have received the update.

The issue has reportedly been acknowledged by the MIDI 2.0 driver developers on Discord. From what I understand, a fix has already been implemented, but it still needs to go through Microsoft’s internal processes before being released via Windows Update.

In the meantime, a temporary workaround is to restart the MIDI service (not loopMIDI). If the new stack is installed, you can:

  1. Go to Windows Tools → Services

  2. Look for Windows MIDI Service (or MIDI Services)

  3. Open it, then click Stop, followed by Start

In some cases, restarting the affected application (DAW or Stream Deck — not loopMIDI) after restarting the MIDI service also resolves the issue.

I’ve confirmed that I do have the Windows MIDI Service installed. Looking back, I experienced a similar issue recently when I created a new port in loopMIDI and it didn’t appear in the plugin, which may have been related.

6 Likes
Why I have rolled back to Previous WIndows build - away from MIDI 2, a warning
Arturia Keylab MK2 Custom Midi Remote Script ( MKII )
2
1 Like
3

Known issues and workarounds, including loopMIDI/loopBE and related.

Pete
Microsoft

3 Likes
4

Good morning and sorry for the bad english. I’m an Ableton user with a Streamdeck and i use It with a template in Mackie Control.

I’m really sorry if i’m writing here, but the issue comes from LoopMidi: It disappears but it disappear from devices and there is no way that i can get It back.

I’ve tried everything mentioned, nothing works.

If i stop the midi service i get a black screen with the “Your device has encoubtered and error”.

I’ve rolled back Windows to the 25h2 “original” version, no way, loop midi Is not listed anymore in the devices hidden or not.

So i’ve activated the loopback ports in Windows.

I’ve contacted the Ableton Template vendors that point me here, with the same solutions that are not working for me, but i was asking them to test the new midi ports, since LoopMidi is no longer needed.

The template works i think as the Cubase template: loopback port A as Output/ loopback port B as input, and in Live i have the Mackie control Active with Loopback A as input and Loopback B as Output

Live Is going crazy and recieve midi notes instead of Mackie Control.

So i’ve tested the SB midi Springbeats.

The ports are working, but the issue is that when i close Live, MidiService starts a loop that prevents Live to close and i have to restart the machine.

If i try to stop midi service from the new MidiSerttings app, black screen and your device etc…

The issue is totally random. Three weeks ago i have reinstalled Windows 25h2, installed LoooMidi and everything was smooth and perfect.

Yesterday i have turn on the PC, and i have this nightmare again, with absolutely no reason.

The only thing that i’ve done is update Nvidia drivers, as i do usually.

I’m writing at Microsoft supporta too.

So, Is there someone that can look inside my machine to understand what Is going on?

In the new MidiSerttings app there are some monitoring features, i can send my registry, i can send my logs, errore…

Believe me, i’ve tried everything.

Thank you so much and sorry again for the bad english.

Roberto

5

You said it was smooth and perfect until Nvidia update. Did it happen straight after the update?

1 Like
6

Well i’m not 100% sure, but yes, It worked perfectly.

I have read your suggestions and i will try the Studio Drivers.

I always do a clean install, i have overlays off, i usually set the max Power to the GPU so the last thing that i can try are Studio Drivers.

Thank you so much for the support!

7

Just let know here if you solved it.

8

Hi Puli, unfortunately it doesn’t work.

Screenshot 2026-02-19 102342
Screenshot 2026-02-19 1023421399×1069 71.8 KB

9

Shame. Did you try to temporarily unload /disable Nvidia drivers to check?

10

Yep, no luck. I really don’t understand why it is not seen anymore in the system and i don’t know why it shows previously with same drivers settings.
Literally from night to day with no reason. The issue is that this Loopback Ports from Windows are not working with the StreamDeck Template. I’m in touch with the developer and they don’t know what to do too.

11

If you have the windows midi service installed, did you down load the preview versions of the tools?

If so you should see the loop midi ports in the new midi settings app.

One of the known issues with new midi system is that sometimes devices that dynamically create midi ports dont get detected. If this is happening to you, start loop midi before windows midi service. And definitely do this before opening up any programs that would need midi.

1 Like
12

Yep, i have all enabked and no LoooMidi. The issue is that LoppMidi is not seen by the system anymore. There is no LoopMidi Virtual midi port in device manager, so it’s like It can’t be seen by the system.

But i have installed SB midi, and while the system seea the ports, the MidiSettings app Is not shiwing any virtual driver.

13

Am waiting on the official release myself. But now Loopmidi can be replaced by a new internal port in the new MIDI2 API apparantly.

1 Like
14

loopMIDI issue and workarounds are documented here:

Mackie control is just MIDI notes and related messages. Whatever is listening to it needs to know to interpret that info as Mackie control, not note information.

This post has a lot in it, and it’s not clear to me what is happening now, what was happening before, etc. I’m finding it very difficult to understand, not because of language, but because it seems to be several weeks of notes.

Black screens and similar: This is the first I’m hearing of or seeing anything with bugchecks for MIDI, but I do not know what state your machine is in, because you said you had rolled back to 25h2.

I suspect more is going on here. If you get me the crash dump I can analyze it. Usually in c:\windows\memory.dmp or c:\windows\mididump*.dmp

If you rolled back, Windows MIDI Services is no longer in use, and if the machine is otherwise healthy, it would work as it used to. The loopback ports would no longer be available to you.

The official Discord server for Windows MIDI Services is Windows MIDI / Audio . I can try to help you there if you start a new post under “bugs-and-suggestions”.

Unfortunately, if you just start a thread on the regular support pages, you won’t get very helpful answers.

Pete
Microsoft

1 Like
15

Thank you so much for your replies.

@Pete the loopback Windows ports fortunately are working fine. I have to use LoooMidi because the StreamDeck template doesn’t works with Windows loopback ports.

I’ve tried to follow the steps that you mentioned, but with no luck.

I’ll open a thread in the proper section.

Thank you again for the support.

1 Like
16

My streamdeck cubase profile also stopped working about yesterday and hoping that this will be fixed soon… Restarting the midi service is not working :frowning:

17

Is that using loopMIDI? If so, there are known workarounds here:

Roberto is working through something different. We’re discussing on Discord.

Pete
Microsoft

18

Yes it’s sideshow cubase profile using loop midi and actually restarting the midiservice gets the traffic back and cubse midi monitoring shows activity when pressing stream deck buttons but the commands do not execute. Normal key commands works ok.

19

You can refer to this post if the Midi Remote lost its Assignments.
In case shoot me an email arbi@sideshowfx.net

1 Like
20

Good news:

Making music with MIDI just got a real boost in Windows 11 | Windows Experience Blog Making music with MIDI just got a real boost in Windows 11 | Windows Experience Blog