I updated from Windows 11 24H2 to 26H2 and MIDI Remote no longer works.
I still see my devices in the Lower Zone MIDI Remote tab (e.g., my Novation Launchpad Mini), but they don’t seem to be receiving MIDI input.
I noticed that my previous MIDI devices (the ones associated with each device such as my Novation Launchpad and Fireface UCX intercface) have been replaced with Windows MIDI (which I now also see in the Task Manager).
I was able to recover all my previous MIDI devices by enabling Use Device WinRT MIDI, but that did not fix my MIDI Remote issue.
The problem seems to be that MIDI info is no longer going to, or going through MIDI Remote.
I also noticed that clicking the buttons on the MIDI Remote Novation Launchpad (on-screen, not the physical buttons) no longer work either.
Does anyone know what could have broke this feature?
System Specs:
AMD Ryzen 7 8745HS 32GB RAM w/ Radeon 780M Graphics
RME UCX audio interface
Windows 11 Pro | version 26H2
Cubase 14.0.31
If I check “Use device WinRT MIDI” all those device names go back to what you’d expect. You said this is a before/after, but it doesn’t really help because you’re using two different APIs in the two screenshots.
This doesn’t seem to be anything related to 26h2 specifically.
Are those screenshots showing what you expect them to?
In the bottom one, “Use device WinRT MIDI” is off. Your old ports were set up using WinRT MIDI, right?
I’m not sure what I was using before, but I don’t remember seeing Windows MIDI in the Device column. I simply stumbled upon the “Use device WinRT MIDI” and noticed that when I enabled it that it changed the Devices back to what I thought they were prior to the update.
What I am 100% sure of is that I now see “Windows Midi Service” in the Background Processes section of the Task Manger which I have never seen before, and so based on that observation I thought that changing the MIDI Port Devices might be the solution to my problem. Unfortunately, it was not.
If I check “Use device WinRT MIDI” all those device names go back to what you’d expect. You said this is a before/after, but it doesn’t really help because you’re using two different APIs in the two screenshots.
Does API = application programming interface? If so, please explain its relevance.
This doesn’t seem to be anything related to 26h2 specifically.
My MIDI Remote was working perfectly yesterday on 24H2. I then spent 8 hours (10PM to 6AM) doing what I thought would be a routine ~30 minute update and, as usual, I now have myriad problems that I did not have before. So, respectfully, I’m certain this problem (and all the others) was caused by the update. I’ve never performed a Windows update without problems (going back to Windows 3.0).
Are those screenshots showing what you expect them to?
At this point I don’t know what to expect from MS; they have been the bane of my existence for decades.
I get you’re frustrated, and your opinions on Microsoft aside, this isn’t a Microsoft or Windows problem.
You were on 24h2 previously, which also had Windows MIDI Services in it since January. It’s not new to 26h2 or new to this month.
You unchecked use WinRT MIDI in Cubase. That made everything show up as “Windows MIDI” because that’s what Cubase shows. If you check it, it shows device names because, again, that’s how Cubase works.
WinRT MIDI: the MIDI API that was introduced with Windows 10
Windows MIDI: the WinMM MIDI API that was introduced with Windows 3.1
The relevance is exactly what I’m pointing out: it changes what Cubase shows in that screen. Why? Because the original WinMM API from Windows 3.1 has no device information for ports, but the WinRT API does.
You unchecked use WinRT MIDI in Cubase. That made everything show up as “Windows MIDI” because that’s what Cubase shows.
Actually, it was the other way around.
After loading a project in Cubase I went to use my Novation Launchpad and it didn’t work. So I opened up MIDI Remote in the Lower Zone and looked for problems there, but didn’t find anything.
So that’s when I went into Studio Setup and noticed that the Devices were all Windows MIDI, and so I went looking for a way to change them back to what I thought they were before when everything was working. And that’s when I discovered the “Use device WinRT MIDI” option.
To be clear, I do not know what the problem is, and that’s why I posted my issue.
In your post, you showed a screen shot that said it was from before the update, and it showed WinRT MIDI checked, and it had the names you expected. Your “after” picture shows the names you said were wrong, and it shows that option unchecked.
What I intended to show was that before the update (I thought) I was using the Devices that you see when I checked “Use device WinRT MIDI” (that was my ‘before’ state).
So, yes, you are correct " … in thinking that [I] took both screenshots after the update".
If so, then this was a bit of a diversion and nothing to do with the MIDI Remote scripts not working.
Maybe not.
My working hypothesis is that there’e a new MIDI ‘transmission’ problem between my Novation Launchpad and Cubase. You obviously know a lot more about Windows than I do, so do you have any suggestions to get my MIDI Remote working again?
I recall reading something about MS introducing new MIDI code a while back and it causing some problems, so maybe that’s where I should look.
I should mention that I have not updated Windows since last year.
You obviously know a lot more about Windows than I do, so do you have any suggestions to get my MIDI Remote working again?
I wrote half the of the new MIDI stack.
I should mention that I have not updated Windows since last year.
That’s also important to know. So you actively blocked updates throughout 2026? The MIDI Updates came through monthly starting in January. You would have had to use a third-party tool, group policy, or registry updates (which do the same as group policy) to block all of the updates.
The reason this is important is because the release in January changed some of the names of the ports. For example, instead of “3- Foo” it’s “3 - Foo” which is a bug and will have the fix rolled out, but for any scripts that check by name instead of SysEx ID, that may be the cause. That’s also why I had to be certain about your screenshots and if they were truly before and after.
The other reason it’s important to know if you completely blocked updates is because the old WinRT MIDI 1.0 port names were terrible. That’s why hardly anyone adopted that API. So we unified the WinMM and WinRT MIDI 1.0 names to better match what WinMM was using. Before, you’d end up with a lot of ports just named “MIDI”. Now, again, if the scripts match on port name, this could break them.
In the Studio Setup in Cubase there’s a little monitor button next to the inputs. It’s the one that looks like a DIN connector for MIDI 1.0.
Pick a device that is not working in MIDI remote, and open the monitor. Then do stuff on the device that would normally send MIDI messages. This is an easy first check that will help sort out if the issue is inside Cubase, or outside of it.
In the Studio Setup in Cubase there’s a little monitor button next to the inputs. It’s the one that looks like a DIN connector for MIDI 1.0.
Pick a device that is not working in MIDI remote, and open the monitor. Then do stuff on the device that would normally send MIDI messages. This is an easy first check that will help sort out if the issue is inside Cubase, or outside of it.
It seems we’re converging on the problem.
I just tried doing what you said and saw no activity from my Novation Launchpad. I know its Input/Output ports from the MIDI Remote Manager (shown below).
So, it seems that there’s a port ‘misalignment’. How do I get this routing corrected?
Pick a device that is not working in MIDI remote, and open the monitor. Then do stuff on the device that would normally send MIDI messages. This is an easy first check that will help sort out if the issue is inside Cubase, or outside of it.
I did that as well. I tested the output of my Studiologic keyboard (which is not associated with MIDI Remote) and saw no activity from it either.
I was going to ask you to install at least the tools next so we can figure out if the problem is outside of Cubase. Before you do that, though, in Cubase, check the option to use System timestamps in that Studio setup window and then see if you get any messages.
If you don’t, we’ll test this using the tools in the Preview 12 release linked above.
Actually I do see activity from my Studiologic keyboard.
My previous attempt was to monitor the output port (I should have used the input port). I guess in/out is relative to Cubase and not the controller itself.
I just noticed you have an m-audio device in there and the korg nanokey.
Are you using the KORG drivers? If so, you need to remove them as they are both no longer necessary and no longer functional. Not using their drivers also eliminates a long-standing problem customers had with the 10 slots in the registry.
(just saw your message about the studiologic. That’s good. Going to finish typing this anyway).