There seems to be an issue after Windows 11 25H2 that is causing Loop MIDI ports not to show as original names (such as Metasystem - Cubase IN), rather it shows as “teVirtual MIDI - Vurtual MIDI Driver”, 16 of them.
Anyone with this problem? Metagrid Pro does not connect now because inside Cubase it can’t find the original MIDI port.
I’m having the same issue here.
Uninstall the “KB5074105” windows update and all came back to “normal” !
Don’t forget to “Pause” your WIN update till end of march (fix must come in march).
Thanks for that remedy. Unfortunately, KB5074105 doesn’t show up for me as an option for uninstalling.
same. I’m stuck with it and a non functioning metagrid. I installed the dev build of midi 1.0 loopback from their discord but no joy getting metaserver to use it.
The ports need be named as speced - so guys what exactly happened with this Windows update?
It was a big midi update with support for 2.0. They broke loopMIDI in the process but replaced it with their own loopback 1.0 and 2.0 ports. I’ve tried everything to recreate metaserver using their new ports without luck.
ok - we will be testing this tomorrow as first priority.
Oh yes you have to… that brokes all my iPad connection…. until I remove this Update and all came back…… so for now I’ve “Pause” my windows 11 update untill they fix it (Microsoft say in march) !
Here : Windows MIDI Services rollout - known issues and workarounds - Windows MIDI and Music dev
And on “Discord”
Or perhaps with the new metaserver that you show (MAC only) create your own “connections”….
I am waiting until Microsoft releases an update
Same issues here…
Bummer
Any workarounds?!! THIS IS REALLY BAD. I can’t roll back. It’s been a week, did you look into it??!!! thanks
EDIT: this worked for me
This fixes it in many cases.
Press Win + R
Type:
services.msc
Find Windows MIDI Service (or MIDI Services)
Click Stop
Then Start it again
Or run this in Admin Command Prompt:
net stop midisrv
net start midisrv
This resets the MIDI stack so Windows can see the loopMIDI ports again.
We’ve spent the last days investigating the recent Windows Update MIDI issues in depth, especially the problems affecting virtual MIDI ports like LoopMIDI.
After extensive testing we can confirm that the behavior is caused by changes in the new Windows MIDI Services stack which Microsoft is currently rolling out with Windows 11 updates. The new MIDI subsystem introduces a different device discovery mechanism and changes how virtual MIDI endpoints are handled.
As a result, some virtual MIDI drivers (including LoopMIDI / teVirtualMIDI-based ports) may currently show issues such as:
• ports not appearing in applications
• ports appearing with different names
• ports disappearing after reboot
• ports not being detected until the MIDI service restarts
This is not a MetaGrid issue, but rather a compatibility problem caused by the transition to the new Windows MIDI architecture.
The good news is that Microsoft’s new MIDI stack also introduces native routing and virtual endpoint capabilities, which will eventually replace the need for third-party loopback drivers.
Because of this shift, we are already planning the migration of our Windows integration toward the new native Windows MIDI system to ensure long-term stability and compatibility with upcoming Windows updates.
We will share more details as this work progresses.
In the meantime, if you encounter issues with virtual MIDI ports, restarting the Windows MIDI Service or reducing the number of virtual ports can sometimes temporarily restore functionality.
Thanks to everyone who reported the issue and helped us track this down.
The workaround @tripleBrett mention works fine but is a termporary solution - all we need to do now is to focus on implementing the new Windows MIDI Services stack in MetaServer.