Windows MIDI Interim Solution (LoopMIDI Failure)

There is currently an issue affecting loopMIDI on Windows systems due to a recent Windows update that may already be installed on your computer.

Microsoft has introduced a new MIDI system in Windows 11 called the MIDI 2.0 Services stack, which changes how the operating system manages MIDI devices internally. This update replaces parts of the older MIDI architecture that many virtual MIDI drivers — including loopMIDI — were originally designed to work with.

Because of this change, compatibility issues may occur. The new Windows MIDI Service may fail to properly register virtual MIDI ports, randomly drop ports, block loopback endpoints, or stop functioning after system sleep, restarts, or updates.

When this happens, any Windows DAW that relies on MIDI communication may experience problems detecting the ports correctly. This can result in:

• Missing MIDI ports
• Inactive MIDI connections
• No incoming or outgoing MIDI signal
• Control surface scripts or MIDI Remote configurations not appearing in the DAW

This can affect Cubase, Nuendo, Ableton Live, Studio One, Reaper, FL Studio, Pro Tools, and other DAWs that rely on Windows MIDI devices.

Going forward, loopMIDI and similar virtual MIDI drivers will eventually be replaced by the new Windows MIDI Services stack. If your system is running an older version of Windows and you choose not to update, you can continue using loopMIDI as your loopback MIDI endpoint.

However, if the virtual ports you previously created in loopMIDI are no longer detectable, it likely means your system has already updated to the newer Windows MIDI 1.0 / MIDI 2.0 Services stack.

With that in mind, the following steps will help you properly integrate and configure the new Windows MIDI Services system.

These instructions are intended to replace the loopMIDI loopback endpoint by using the new Windows MIDI 2.0 Services stack instead.

If you are using an older Windows system, or if you choose not to update to the newer Windows MIDI driver architecture, the original loopMIDI setup instructions will still apply and continue to work as your loopback MIDI endpoint.

Confirming if you need Windows MIDI Service or LoopMIDI

You can run a quick test to see if your system needs the new MIDI Sevice or LoopMIDI.
(If your system did accept LoopMIDI Previously and now not available or if you know your system updated in March no need to run this test - you need the new tool)
Go to this address

https://github.com/microsoft/MIDI/releases

Under the section titled “App SDK and Tools Release Candidate 3 + Basic MIDI 1.0 Loopbacks,” scroll down until you see “Assets.” Click on Assets to expand the list of available downloads.

Download either the x64 or arm64 version of the midicheckservice tool.

Unzip and run the tool. If you see a "Successfully verified" message you can install the new tool.

New Windows MIDI 2.0/1.0 Service Stack

Installed Midi Runtime 1.0.17-rc.4.6

Update Instructions

Before installing the new version, it is recommended to uninstall the previous version of the SDK Runtime and Tools. (If previously installed)

Go to Settings > Apps > Installed Apps (use Windows Settings, not the Control Panel). There is no need to remove any service plugins.

 Download the installer that matches your system architecture:

https://github.com/microsoft/MIDI/releases/tag/rc-4

• Arm64 – for Qualcomm and similar processors
• x64 – for AMD and Intel processors

Developer Mode is only required to allow installation of the unsigned beta app. After installation, you can disable Developer Mode again if you prefer.

For a fresh installation, also download the MIDI 1.0 Basic Loopback Plugin.

These files should be stored in a location that allows convenient access.

Once downloaded, simply double-click the installer to begin. You do not need to manually run it as Administrator—Windows 11 will automatically prompt for admin permissions during installation.

Please note that this installer is not digitally signed, so you may encounter security warnings during download and installation. Additionally, some third-party antivirus or antimalware programs may block, delete, or interfere with the installer.

 If this happens, refer to your security software’s documentation to add a temporary or permanent exclusion.

Save these 2 Files somewhere in your Directory. Or desktop for easy access

Installing the Tool

After downloading the files, run the Loopback installer first, followed by the SDK installer.

During installation, you may see a popup message that says “Windows protected your PC.” This appears because the application is unsigned.

To proceed:

1. Click More info
   
2. Select Run anyway
   
3. Continue the installation to complete the setup.
4. If you have older version of the Loopback plugin it will ask to uninstall first before installing the new Plugin
   
   
   
   
   

   Using the Setup Tool

   1. Click the Windows Start button
   2. Search for “MIDI”
   3. Open the MIDI application
      
      
      You may see this window asking to finish the MIDI Setup. Click Finish MIDI Setup.
      
      
      You will then see the settings loaded on the side panel.
      
      
      
      • Click the MIDI 1.0 Loopback Endpoints
        
        
        
        
      • Select “Create New Basic Loopback Endpoint”
        
        

        In the “Loopback Name” field, enter “StreamDeck2DawTrack”* (or any name you prefer for the port), then click OK.

        Repeat the same steps to create a second port for the opposite direction—for example, “DawTrack2StreamDeck.”*

        
        
        

        Create any additional ports using the same steps, if required.

        Once everything is set up, you can uninstall loopMIDI and disable Developer Mode if you no longer need it.

        If you encounter an “Unable to create loopback endpoint” error while creating a port, restart the MIDI Service and then try creating the endpoint again.
        
        

      Below are the ports used in our various packs:
      
      

      Ableton Live needed ports

      StreamDeck2DawTrack

      DawTrack2StreamDeck

      Mackie2Daw

      Daw2Mackie

       

      Cubase/Nuendo  needs
      
      StreamDeck2DawTrack
      DawTrack2StreamDeck

      MidiKeys_IN

      MidiKeys_OUT

      Mackie2Daw

      Daw2Mackie

       

      Fender Studio /Studio One

      MidiKeys_IN

      MidiKeys_OUT

      Mackie2Daw

      Daw2Mackie

       

      Logic Pro

      Mackie2Daw

      Daw2Mackie

       

      Reaper

      StreamDeck2Daw

      Daw2StreamDeck

      Mackie2Daw

      Daw2Mackie

       

       

       

      ProTools

      SD2ProTools

      ProTools2SD

       

       

      Fruity Loops

      Mackie2Daw

      Daw2Mackie

       

      Bitwig

      StreamDeck2DawTrack

      DawTrack2StreamDeck

      Mackie2Daw

      Daw2Mackie

       

       

       

      Davinci Resolve Color Panel

      ColorPanel_IN

      Color_Panel_OUT

      Mackie2Daw

      Daw2Mackie