# Metaserver does not find Loop MIDI ports **URL:** \ **Category:** General Discussion\ **Created:** [February 27, 2026, 8:23pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289 "2026-02-27T20:23:57Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Vicken](https://avatars.discourse-cdn.com/v4/letter/v/50afbb/32.png) [@Vicken](https://forum.metagrid.app/u/Vicken)\ **Post date:** [February 27, 2026, 8:23pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/1 "2026-02-27T20:23:57Z")
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. ---
**Author:** ![Vicken](https://avatars.discourse-cdn.com/v4/letter/v/50afbb/32.png) [@Vicken](https://forum.metagrid.app/u/Vicken)\ **Post date:** [February 28, 2026, 5:43am UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/2 "2026-02-28T05:43:21Z")
![IMG_3531](https://canada1.discourse-cdn.com/flex009/uploads/metagrid/original/2X/2/2fbbe6a0ed1ab4e5c9b1fa28fecc22d83978b53f.jpeg) ---
**Author:** ![millertone](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@millertone](https://forum.metagrid.app/u/millertone)\ **Post date:** [March 1, 2026, 5:51pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/3 "2026-03-01T17:51:02Z")
I’m having the same issue here. ---
**Author:** ![HomeStudio87](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/homestudio87/32/89_2.png) [@HomeStudio87](https://forum.metagrid.app/u/HomeStudio87)\ **Post date:** [March 1, 2026, 7:31pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/4 "2026-03-01T19:31:55Z")
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). ---
**Author:** ![millertone](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@millertone](https://forum.metagrid.app/u/millertone)\ **Post date:** [March 2, 2026, 4:26pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/5 "2026-03-02T16:26:51Z")
Thanks for that remedy. Unfortunately, KB5074105 doesn’t show up for me as an option for uninstalling. ---
**Author:** ![biped](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@biped](https://forum.metagrid.app/u/biped)\ **Post date:** [March 2, 2026, 5:45pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/6 "2026-03-02T17:45:44Z")
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. ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 2, 2026, 7:43pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/7 "2026-03-02T19:43:19Z")
The ports need be named as speced - so guys what exactly happened with this Windows update? ---
**Author:** ![biped](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@biped](https://forum.metagrid.app/u/biped)\ **Post date:** [March 2, 2026, 7:54pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/8 "2026-03-02T19:54:52Z")
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. ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 2, 2026, 7:56pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/9 "2026-03-02T19:56:57Z")
ok - we will be testing this tomorrow as first priority. ---
**Author:** ![HomeStudio87](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/homestudio87/32/89_2.png) [@HomeStudio87](https://forum.metagrid.app/u/HomeStudio87)\ **Post date:** [March 2, 2026, 9:44pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/10 "2026-03-02T21:44:10Z")
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](https://devblogs.microsoft.com/windows-music-dev/windows-midi-services-rollout-known-issues-and-workarounds/) And on “Discord” Or perhaps with the new metaserver that you show (MAC only) create your own “connections”…. ---
**Author:** ![Vicken](https://avatars.discourse-cdn.com/v4/letter/v/50afbb/32.png) [@Vicken](https://forum.metagrid.app/u/Vicken)\ **Post date:** [March 3, 2026, 1:53am UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/11 "2026-03-03T01:53:57Z")
I am waiting until Microsoft releases an update ---
**Author:** ![PdC](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@PdC](https://forum.metagrid.app/u/PdC)\ **Post date:** [March 6, 2026, 8:37pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/12 "2026-03-06T20:37:01Z")
Same issues here… Bummer ---
**Author:** ![tripleBrett](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/triplebrett/32/90_2.png) [@tripleBrett](https://forum.metagrid.app/u/tripleBrett)\ **Post date:** [March 9, 2026, 2:25pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/13 "2026-03-09T14:25:01Z")
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 # Fix 1 (fastest): Restart the Windows MIDI service This fixes it in many cases. 1. Press **Win + R** 2. Type: 3. Find **Windows MIDI Service** (or **MIDI Services** ) 4. Click **Stop** 5. Then **Start** it again Or run this in **Admin Command Prompt** : ```auto net stop midisrv net start midisrv ``` This resets the MIDI stack so Windows can see the loopMIDI ports again. ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 9, 2026, 4:42pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/14 "2026-03-09T16:42:37Z")
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. ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 9, 2026, 4:58pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/15 "2026-03-09T16:58:30Z")
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. ---
**Author:** ![raymond0](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@raymond0](https://forum.metagrid.app/u/raymond0)\ **Post date:** [March 15, 2026, 10:33pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/16 "2026-03-15T22:33:53Z")
This Windows update has been talked about for years with the Windows rep Pete Brown active on many forums, his Microsoft blog and at conferences. Here is a Pete Brown post (today) that might be useful [Win 11 KB5077241 Update making all Midi Devices Disappear | Page 4 | VI-CONTROL](https://vi-control.net/community/threads/win-11-kb5077241-update-making-all-midi-devices-disappear.170478/page-4#post-5843748) I’m confident that if Metagrid approached him he would respond as he has mentioned industry engagement several times in the posts I’ve read. Although probably not relevant to Metagrid fyi there’s also a Windows native ASIO update scheduled for later this year. Cheers. ---
**Author:** ![millertone](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@millertone](https://forum.metagrid.app/u/millertone)\ **Post date:** [March 18, 2026, 1:47pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/17 "2026-03-18T13:47:17Z")
Seems that since updating to 1.6.17 MetaGrid Pro won’t connect to my computer, even though it shows up while scanning. Ironically, MetaServer is connecting to LoopMIDI or some other MIDI service. Is this all because MetaServer 6.0 isn’t available for Windows yet? ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 18, 2026, 2:55pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/18 "2026-03-18T14:55:44Z")
MetaServer 6.0 is not available for Windows yet. What happens when you try to connect? WiFi / USB? ---
**Author:** ![millertone](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@millertone](https://forum.metagrid.app/u/millertone)\ **Post date:** [March 18, 2026, 3:32pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/19 "2026-03-18T15:32:31Z")
I’m unable to connect via WiFi, and I get frequently disconnected via USB. ---
**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\ **Post date:** [March 18, 2026, 3:50pm UTC](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289/20 "2026-03-18T15:50:32Z")
Can you please send us the logs from MetaGrid - make sure they are set to Trace. We will handle this ASAP. [Next page](https://forum.metagrid.app/t/metaserver-does-not-find-loop-midi-ports/1289.md?page=2)