# Will new Windows MIDI loopback ports allow MidiOutput::createNewDevice() on Windows? **URL:** \ **Category:** Windows\ **Created:** [March 11, 2026, 1:46pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420 "2026-03-11T13:46:19Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![adamstark](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/adamstark/32/122_2.png) [@adamstark](https://forum.juce.com/u/adamstark)\ **Post date:** [March 11, 2026, 1:46pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/1 "2026-03-11T13:46:19Z")
It looks like Microsoft are putting some time into virtual MIDI ports on Windows. E.g. here: > **[Release App SDK and Tools Release Candidate 3 + Basic MIDI 1.0 Loopbacks ·...](https://github.com/microsoft/MIDI/releases/tag/rc-3)** > > UPDATE: 2026-03-01: Replaced the SDK & Tools package with a newer one with an updated MIDI Settings App installer to help those who were running into the XamlParseException on Settings app Startup.... Will this allow the implementation of… `MidiOutput::createNewDevice()` on Windows to match macOS functionality? If so is this something the JUCE team would consider adding? Thanks, Adam ---
**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\ **Post date:** [March 11, 2026, 2:32pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/2 "2026-03-11T14:32:46Z")
This is already present in JUCE’s develop branch, although you will need to have the Windows MIDI SDK installed, and you’ll also need to include the Windows MIDI Services nuget package in your build. You can currently get the package from the project’s [Releases page](https://github.com/microsoft/MIDI/releases). You’ll also need to set the `JUCE_NEEDS_WINDOWS_MIDI_SERVICES` module configuration flag to 1. ---
**Author:** ![adamstark](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/adamstark/32/122_2.png) [@adamstark](https://forum.juce.com/u/adamstark)\ **Post date:** [March 11, 2026, 2:44pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/3 "2026-03-11T14:44:31Z")
Ok great, thank you 🙂 ---
**Author:** ![bnoel](https://avatars.discourse-cdn.com/v4/letter/b/a183cd/32.png) [@bnoel](https://forum.juce.com/u/bnoel)\ **Post date:** [June 29, 2026, 2:19pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/4 "2026-06-29T14:19:03Z")
Is there news on the support of these feature for windows ? the doc for 8.0.14 still states this to be not supported for windows. 🙂 Thanks. ---
**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\ **Post date:** [June 30, 2026, 1:37pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/5 "2026-06-30T13:37:46Z")
> [@bnoel](#): > > Is there news on the support of these feature for windows ? the doc for 8.0.14 still states this to be not supported for windows. 🙂 Most of the advice above holds for 8.0.14. The work has been merged from develop into the master branch, but still requires some extra configuration/setup. You might find the steps described [here](https://github.com/juce-framework/JUCE/issues/1648#issuecomment-4291982166) helpful. In short, you need the Windows MIDI Services SDK Runtime installed, and you also need the nuget packages for Windows MIDI Services and Cppwinrt installed. If you’re using the Projucer, you need to enable the JUCE\_NEEDS\_WINDOWS\_MIDI\_SERVICES module flag on juce\_audio\_devices, or if you’re using CMake, pass `NEEDS_WINDOWS_MIDI_SERVICES TRUE` to your `juce_add_gui_app` call. Microsoft is currently working on moving the Windows MIDI Services SDK and API in-box. This means that, in the future, the nuget part of the setup should become unnecessary. At that point, I imagine we’ll just check the current Windows SDK at build-time and enable the MIDI Services if possible. ---
**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\ **Post date:** [June 30, 2026, 1:47pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/6 "2026-06-30T13:47:19Z")
I guess MS are not going to add this to Windows 10, even though it’s service lifetime has just been extended to Oct 27? ---
**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\ **Post date:** [June 30, 2026, 1:56pm UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/7 "2026-06-30T13:56:53Z")
Yeah I can’t imagine they’ll do that. ---
**Author:** ![bnoel](https://avatars.discourse-cdn.com/v4/letter/b/a183cd/32.png) [@bnoel](https://forum.juce.com/u/bnoel)\ **Post date:** [July 1, 2026, 7:22am UTC](https://forum.juce.com/t/will-new-windows-midi-loopback-ports-allow-midioutput-createnewdevice-on-windows/68420/8 "2026-07-01T07:22:45Z")
Thanks !