# \[Obsolete\] Native Windows MIDI Services with MetaServer (Windows 11) — RC4 Setup Guide

**URL:** <https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456>\
**Category:** General Discussion\
**Created:** [June 2, 2026, 11:52am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456 "2026-06-02T11:52:14Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**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:** [June 2, 2026, 11:52am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/1 "2026-06-02T11:52:14Z")

</div>

**Guide retired · 9 November 2026**

The original setup used the RC4 preview of Windows MIDI Services. Microsoft has withdrawn support for those components. Please skip the old installation steps, including any quoted in the replies below. Please don’t install RC4, enable Developer Mode, install preview transports, or change the MIDI service account to make MetaServer 6.0.5 detect native ports.

**If your native ports disappeared after removing RC4** , MetaServer for Windows 6.0.5 (build 6016) checks for the old SDK runtime before it checks the Windows MIDI service. That can leave native ports unavailable in MetaServer even when the service itself is running. Installing newer MIDI tools alone does not update the API used by this build.

If your existing MIDI setup works, you can keep using it. If you’re moving from RC4 to Microsoft’s newer preview components, follow Microsoft’s removal instructions for your configuration. [Microsoft’s Windows MIDI Services release instructions](https://github.com/microsoft/MIDI/releases/tag/inbox-preview-13)

**Production update · 10 November 2026** — [MetaServer for Windows 6.0.6 (build 6022)](https://metagrid.app/resources/MetaServer_Win.exe) is available through auto-update and direct download. On Windows 11 25H2 and later it includes Microsoft’s Preview 11 API and works after RC4 is removed. You can remove any remaining RC4 components under **Settings → Apps → Installed apps**. The separate Microsoft MIDI Tools and Transports are optional for MetaServer.

The Windows installer is unsigned. See the [release announcement](https://forum.metagrid.app/t/1681/1) for its SHA-256 and the [Windows MIDI Services discussion](https://forum.metagrid.app/t/1680) for Pete’s guidance. Thanks to Pete for flagging the change and to @triplebrett for documenting the original setup.

---

<div class="post-metadata">

**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:** [June 2, 2026, 11:53am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/2 "2026-06-02T11:53:41Z")

</div>

Pinned on June 2, 2026, 11:53am UTC



---

<div class="post-metadata">

**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:** [June 2, 2026, 11:53am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/3 "2026-06-02T11:53:50Z")

</div>

Unpinned on June 2, 2026, 11:53am UTC



---

<div class="post-metadata">

**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:** [June 2, 2026, 11:54am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/4 "2026-06-02T11:54:13Z")

</div>

Made this a banner on June 2, 2026, 11:54am UTC. It will appear at the top of every page until it is dismissed by the user.



---

<div class="post-metadata">

**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:** [June 2, 2026, 11:54am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/5 "2026-06-02T11:54:38Z")

</div>

Removed this banner on June 2, 2026, 11:54am UTC. It will no longer appear at the top of every page.



---

<div class="post-metadata">

**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:** [June 2, 2026, 11:54am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/6 "2026-06-02T11:54:54Z")

</div>

Pinned globally on June 2, 2026, 11:54am UTC



---

<div class="post-metadata">

**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:** [June 3, 2026, 11:58am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/7 "2026-06-03T11:58:10Z")

</div>

One more thing to add that helps. Run ‘services.msc’ and right click on Windows Midi services and click properties. Change Startup to Automatic (Delayed Start)

 ![Screenshot 2026-06-03 075223](https://canada1.discourse-cdn.com/flex009/uploads/metagrid/original/2X/b/b9d61a1e04011192e6dc90f2f7382b2966fabbb7.png)

---

<div class="post-metadata">

**Author:** ![raymond0](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@raymond0](https://forum.metagrid.app/u/raymond0)\
**Post date:** [June 4, 2026, 12:44am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/8 "2026-06-04T00:44:54Z")

</div>

The go-to site for all things relating to the new Windows Midi Services is [https://aka.ms/mididiscord](https://aka.ms/mididiscord)

Pete Brown, the Microsoft project manager for Native Windows Midi Services, set this up and posts regularly. There’s setups, workarounds, news of developments, resources, reporting of issues etc.

For example:  
" **Fix for loopMIDI/rtpMIDI/IP-MIDI etc and workaround for Hangs with inMusic/AKAI/Rane/NuMark/m-audio etc. drivers**

The update is now rolling out in Windows 11 via 30-day CFR starting on April 30, finishing by May 30. CFRs are explained here: **⁠[key-release-updates](https://discord.com/channels/980245825202552942/1477135264290967573/1495140512921948331)**

**⁠Symptoms:** loopMIDI/rtpMIDI/loopBE/SSL/AVID/ipMIDI/NI DAW etc ports do not show up in apps. **Symptoms:** Cubase and other apps hang at “initializing MIDI” and you have an inMusic device connected.

Be sure to keep up to date with your Windows Updates to receive this fix. I’ve removed the link to the workaround from here because the better choice is to get the in-box version."

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/psychlist1972/32/1248_2.png) [@Psychlist1972](https://forum.metagrid.app/u/Psychlist1972)\
**Post date:** [June 6, 2026, 8:21pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/9 "2026-06-06T20:21:39Z")

</div>

Hey all. Excited to see this!

I found this because one of the MetaGrid/MetaServer customers ran into a MIDI detection issue and posted on our Discord server.

Just a note: the official download for the current Windows MIDI Service SDK and Tools is [About Windows MIDI Services - Windows MIDI Services](https://aka.ms/midi) , not the winget link. Someone listed an older SDK version in winget, and last I checked, had not updated it to the rc4 version.

As explained on the Discord server, over the next few months, we will be putting the SDK (not the MIDI Settings app or Console) into Windows so no download will be required for that. (Current plan is for this to also include the MIDI 1 loopback support for SDK and Service.) There are breaking API changes there based on feedback, and although it’s not an officially supported scenario, the downloadable and in-box SDKs should coexist while you move to the in-box version.

Any questions? [Windows MIDI / Audio](https://aka.ms/mididiscord)

Pete  
Microsoft

---

<div class="post-metadata">

**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:** [June 7, 2026, 12:48am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/10 "2026-06-07T00:48:28Z")

</div>

Thank you Mister, Finaly my Windows Midi App is here and now can make my midi loopback with the new system… Thank you Mr Psychlist1972 (again…😉 )

---

<div class="post-metadata">

**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:** [June 7, 2026, 12:21pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/11 "2026-06-07T12:21:17Z")

</div>

Thank you, Pete — really appreciate you stepping in directly, and the correction is noted. I’ve updated our guide to point to [About Windows MIDI Services - Windows MIDI Services](https://aka.ms/midi) as the canonical source rather than the winget package.

And congratulations to you and the team on Windows MIDI Services — it’s a genuinely impressive piece of work. Bringing proper MIDI 2.0, multi-client support, and a modern SDK to Windows while keeping decades of MIDI 1.0 apps and devices working is no small feat, and the UMP-centric design with transparent translation is exactly the kind of foundation the platform has needed for a long time.

We also fully appreciate how hard this is to roll out — shipping something this fundamental across the entire Windows install base, in phases, while iterating on breaking API changes from community feedback, is a serious undertaking. The out-of-band SDK approach makes a lot of sense given that.

Looking forward to the in-box SDK and loopback support landing down the line — that’ll make life much simpler for our users. Thanks again your reply on this forum.

---

<div class="post-metadata">

**Author:** ![biped](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@biped](https://forum.metagrid.app/u/biped)\
**Post date:** [June 12, 2026, 1:45pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/12 "2026-06-12T13:45:54Z")

</div>

Early adopter to Pete’s fixes here. I had everything working with Reaper/Metaserver/Metagrid under Windows 11 updated MIDI.

I have been using native Windows MIDI ports using metaserver 5.1.8. Just updated to metaserver 6 and it isn’t working. It looks like it should be but it’s not. I guess metaserver 6 thought i was running with loopmidi ports, but I wasn’t. It asked if I wanted to change to the new midi ports so i said ok. I saw that it created it’s own midi ports. Ok, but they didn’t work. I noticed that under integration (Reaper) it said incomplete. It wasn’t, it’s been fine. But i imported the keymap anyway. Nothing.

Ok, so I reverted to the ‘old’ ports. Everything is working again.

Metaserver still thinks I’m on the old loopmidi, but I’m not. It thinks the ports I assigned are loopMidi ports, but they are not.

The option to switch to native midi ports is still there, but again, it doesn’t work for some reason. When i turn it on, I see the ports it creates, but they don’t get used.

Under integrations, it shows Reaper “Setup Incomplete”. But it isn’t, because it’s working.

These are the Windows Midi ports in the new windows midi settings (pic below) that I created for 5.1.8.

 ![metaserver](https://canada1.discourse-cdn.com/flex009/uploads/metagrid/original/2X/9/9ef28cfec34708cf4fcca608a41f60d1a16e3f2f.png)

So for now, I’m on Metaserver 6 using my own ‘custom’ native Windows MIDI ports.

The UI in metaserver doesn’t provide any indication why the new midi ports weren’t working. I couldn’t see anyway to troubleshoot it. For now, I’ll stick with what I have.

I write this in the hopes that devs can stremline the migration process for someone already using native windows Midi.

---

<div class="post-metadata">

**Author:** ![biped](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@biped](https://forum.metagrid.app/u/biped)\
**Post date:** [June 16, 2026, 1:11pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/13 "2026-06-16T13:11:30Z")

</div>

Some more thoughts regarding Win 11:

- Metaserver does not start with Windows, even though I have the box checked.
- Checking for a new version provides no feedback.
- The tray icon shows WiFi and USB as online, but the app shows USB as idle.
- Still thinks I’m using LoopMidi ports and prompts me to use Windows MIDI services, even though I am (from early hotfixes provided by Pete from Microsoft).
- Reaper integration shows as ‘setup incomplete’, but it was previously setup on the older versions of Metaserver, and I have all the custom macros/keymaps imported and it works.

---

<div class="post-metadata">

**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:** [June 16, 2026, 7:22pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/14 "2026-06-16T19:22:30Z")

</div>

@biped Are you on MetaServer 6.0.2?

---

<div class="post-metadata">

**Author:** ![biped](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@biped](https://forum.metagrid.app/u/biped)\
**Post date:** [June 16, 2026, 8:25pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/15 "2026-06-16T20:25:00Z")

</div>

Yes, confirmed: 6.02 (you can see it my screenshot above)

---

<div class="post-metadata">

**Author:** ![Psychlist1972](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/psychlist1972/32/1248_2.png) [@Psychlist1972](https://forum.metagrid.app/u/Psychlist1972)\
**Post date:** [November 8, 2026, 9:29pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/16 "2026-11-08T21:29:27Z")

</div>

A reminder that the Windows MIDI Services rc4 bits referenced in this post are no longer supported nor are they available.

Current Windows bits are at [Releases · microsoft/MIDI · GitHub](https://aka.ms/midireleases) . Older rc4 and earlier releases of tools, API, or transports, should be uninstalled via Windows Settings \> Apps \> Installed Apps.

Pete  
Microsoft

---

<div class="post-metadata">

**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:** [November 9, 2026, 4:00pm UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/17 "2026-11-09T16:00:50Z")

</div>

Thanks, Pete. For anyone who found this guide after removing RC4, [Download MetaServer for Windows 6.0.6 Beta 2 (build 6021)](https://metagrid.app/downloads/beta/metaserver/windows/6.0.6/Beta2/MetaServer-6.0.6-Beta2-Windows.exe). On Windows 11 25H2 and later, this build uses the newer API and can discover native MIDI ports without the old runtime. You can keep your current MetaGrid Pro app.

The installer is unsigned. You’ll find the checksum in [the pinned beta post](https://forum.metagrid.app/t/150/1). Please share your results in [the RC4 support thread](https://forum.metagrid.app/t/1680) so we can follow up in one place.

---

<div class="post-metadata">

**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:** [November 10, 2026, 11:19am UTC](https://forum.metagrid.app/t/obsolete-native-windows-midi-services-with-metaserver-windows-11-rc4-setup-guide/1456/18 "2026-11-10T11:19:46Z")

</div>

For anyone following this guide, the production update is available now. Use the built-in updater or [download MetaServer for Windows 6.0.6 (build 6022)](https://metagrid.app/resources/MetaServer_Win.exe), then reopen your DAW. On Windows 11 25H2 and later, the Preview 11 API is included. You can leave RC4 uninstalled. The first post now links to the production installer. [Release notes](https://metagrid.app/resources/releases/metaserver/windows/6.0.6/6022/MetaServer-6.0.6-6022-whats-new.html)
