This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 17%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
In the ongoing nightmare that is WIndows 11 my Midi instruments are no longer being picked up. How do I fix it? In the long term I'm going to buy a MAC because I'm sick to death of trying to troubleshoot the bug ridden crock that is Windows 11.
I've been trying to fix this particular issue for hours now and I think Copilot may have made issues worse. Yyou should understand we just want a stable system that works ...not what your imposing on us
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 79%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
I fixed the loopmidi. My theory about what is wrong was : Windows WMI / MIDI enumeration issues. Lets see if I was right...
START↓ The tool the Windows tech gave points to a couple interesting issues. after checking the paperwork and putting it through VirusTotal. Info:
The chain goes: Windows MIDI Services; WinMM MIDI; USB MIDI devices; Network MIDI discovery.
The program has 2 special parts that they highlight and which points to the issues also.
In the program - (MidiEndpointDeviceInformation) exists to - represent a MIDI device endpoint.
MidiEndpointDeviceInformation:↓
DeviceID; EndpointName; Transport; Metadata; Capabilities.
*This is what apps read to display MIDI ports.↑
Definitions:
USB endpoint: the logical termination point for communication between the device and the host computer.
MIDI device endpoint: is a specific, addressable source (input) or destination (output) of MIDI data within a device or software, representing a single 16-channel stream.
Displayed MIDI Port-(virtual MIDI drivers or MIDI monitor): creates, manages, and visualizes virtual pathways for MIDI data to flow between applications on the same computer.
--------------------------------------------- USB / Bluetooth / Network MIDI device; Windows USB / device stack; Windows MIDI Service (midisrv); MIDI endpoints createdApps (DAWs, Python, tools, etc).
MidiEndpointDeviceWatcher: It watches the system for MIDI endpoints appearing or disappearing. Windows MIDI Services ties the watcher directly to the service lifecycle.
USB device plugged in; USB stack detects device; MIDI service creates endpoint; DeviceWatcher fires event; App sees new MIDI port
My issue is right in this pipeline. Which is amazing because all my work was not wasted, I did hunt down the right path to find the issue!!
---------------- Conclusion:
USB device detected ->PNP device created; BUT MidiEndpointDeviceInformation not created. Which results in: USB device exists but MIDI endpoint does not exist. ->(cant see the MIDI device's name in software)
So then we ask? " Why did older "MIDI breaks"? Well, older MIDI devices often rely on the old WinMM enumeration path. With new paths made because the implementation of MIDI 2.0 to Windows being the possible cause.
The new system translates: WinMM; WinRT; MIDI 2.0; USB MIDI. Our old devices fail, If the translation fails, the device never becomes an endpoint. In the end, after all of that, the failure likely lays inside; Windows MIDI Services or WMI Enumeration layer. This comes up (wmidap.exe) which is why I landed on WMI Enumeration failing. So I guess I was close in my personal finding, but it is good to know way smarter people than me made a program to fix it this issue that should have never been broken
. In short- Primary issue appears to be Windows MIDI endpoint enumeration / binding for older MIDI 1.0 devices, likely involving the newer Windows MIDI Services layer, WMI/device metadata enumeration, or legacy compatibility handoff.
Saying Windows WMI was the cause is not 100%, but super close, I just am new to this type of deep troubleshooting is not my normal wheelhouse. But I am learning, and its been fun!
I hope this help! ♥
I was able to get Loop MIDI to work? Because I'm having the MIDI 1.0 issue as well, but I did find a way to fix Loop MIDI but. The process is advanced to help you rebuild LoopMIDI. The program they provided in this thread is amazing and should work! My theory about what is wrong was : Windows WMI / MIDI enumeration issues. Let's see if I was right...
START↓
The tool the Windows tech gave points to a couple interesting issues. after checking the paperwork and putting it through VirusTotal. Info:
The chain goes: Windows MIDI Services; WinMM MIDI; USB MIDI devices; Network MIDI discovery.
The program has 2 special parts that they highlight and which points to the issues also.
In the program - (MidiEndpointDeviceInformation) exists to - represent a MIDI device endpoint.
MidiEndpointDeviceInformation:↓
DeviceID; EndpointName; Transport; Metadata; Capabilities.
*This is what apps read to display MIDI ports.↑
Definitions:
USB endpoint: the logical termination point for communication between the device and the host computer.
MIDI device endpoint: is a specific, addressable source (input) or destination (output) of MIDI data within a device or software, representing a single 16-channel stream.
Displayed MIDI Port-(virtual MIDI drivers or MIDI monitor): creates, manages, and visualizes virtual pathways for MIDI data to flow between applications on the same computer.
USB / Bluetooth / Network MIDI device; Windows USB / device stack; Windows MIDI Service (midisrv); MIDI endpoints createdApps (DAWs, Python, tools, etc).
MidiEndpointDeviceWatcher: It watches the system for MIDI endpoints appearing or disappearing. Windows MIDI Services ties the watcher directly to the service lifecycle.
USB device plugged in; USB stack detects device; MIDI service creates endpoint; DeviceWatcher fires event; App sees new MIDI port
My issue is right in this pipeline. Which is amazing because all my work was not wasted, I did hunt down the right path to find the issue!!
Conclusion:
USB device detected -> PNP device created; BUT MidiEndpointDeviceInformation not created. Which results in: USB device existing but MIDI endpoint does not exist. ->(cant see the MIDI device's name in software)
So then we ask? " Why did older MIDI break?" Well, older MIDI devices often rely on the old WinMM enumeration path. With new paths made because the implementation of MIDI 2.0 to Windows being the possible cause.
The new system translates: WinMM; WinRT; MIDI 2.0; USB MIDI. Our old devices fail, If the translation fails, the device never becomes an endpoint. In the end, after all of that, the failure likely lays inside; Windows MIDI Services or WMI Enumeration layer. This comes up (wmidap.exe) which is why I landed on WMI Enumeration failing. So I guess I was close in my personal finding, but it is good to know way smarter people than me made a program to fix it this issue that should have never been broken
. In short- Primary issue appears to be Windows MIDI endpoint enumeration / binding for older MIDI 1.0 devices, likely involving the newer Windows MIDI Services layer, WMI/device metadata enumeration, or legacy compatibility handoff.
Saying Windows WMI was the cause is not 100%, but super close, I just am new to this type of deep troubleshooting is not my normal wheelhouse. But I am learning, and its been fun!
I hope this help!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 31%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZ%3C/text%3E%3C/svg%3E)
After much research I found that simply adding the missing string midi wdmaud.drv and midi1 wdmaud.drv solved my missing midi ports for my Roland quadcapture, ableton 12
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 92%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPG%3C/text%3E%3C/svg%3E)
I have the exact same issue, whether using SW based MIDI devices such as LoopMIDI or Physical devices connected via USB. Frustrating at the minimum.
My workaround is to restart the Windows MIDI service, works every time and avoids having to reboot. So whenever I connect or reconnect MIDI device, I restart the service.
But yes, It would be great if Microsoft would get their act together and not ruin MIDI on Windows 11...
-P.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 5%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Microsoft just released a big feature update to the release preview track that adds native MIDI services support as KB5074105. as it is a 'release preview' you will need to switch windows update to the release preview track.
there is also a full website concerning the new feature.
https://microsoft.github.io/MIDI/
the tools and SDK pack have yet to be released. in the mean time, they have an enablement checking tool to see if MIDI is enabled yet or not on your system.
Not sure if this will help any older apps like dosbox or older games that might use MIDI feautres (like Bioshock 2's support of Creative labs X-Fi midi soundfonts, but the update would definitely help those who have something like a musical keyboard hooked up to their computer that uses MIDI.
from the MS midi website:
Windows MIDI Services is the new and greatly improved MIDI stack for Windows, supporting both MIDI 1.0 and MIDI 2.0.
Windows MIDI Services brings MIDI 2.0, multi-client (multiple apps using the same device) MIDI 1.0, app-to-app MIDI, faster USB transports, built-in loopback MIDI, and much more. The Runtime and tools enable applications to use this new API, and for you to be able to configure, customize, and troubleshoot your MIDI setup.
At the very least this should be of some use to the OP of this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 23%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERT%3C/text%3E%3C/svg%3E)
I'm experiencing the same frustraton. LoopMidi won't appears anymore...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 39%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
I totally agree.
Everyday you expect the worst when connecting synthesizers, writing score music .
The only thing working properly under Windwos 11 is spamming you with AI trash.
If your MIDI ports are not appearing in Windows 11, here are some steps you can take to troubleshoot the issue:
If you continue to experience issues, you may want to consult the documentation for your specific MIDI devices or reach out to the manufacturer's support for further assistance.
References:
