So today I go to start working on a session and I get a hang at initializing midi inputs. Is this in some way related to Microsoft changing the MIDI in Windows 11 recently?
Not sure how to get past this and get working again.
crash report shows wdmaud2 as the problem. According to Google, that is the new MIDI 2. This is going to be a super big problem if they really totally broke Windows MIDI.
Only solution I found was to uninstall the Windows update: KB5077241.
Nuendo now works again. This is not ready to roll out yet. What is Microsoft thinking?!
What MIDI devices do you have attached? Any virtual MIDI devices?
Tons of people are using the new stack without problems. Most issues are with specific devices and drivers.
Pete
Microsoft
Thanks Pete.
What MIDI to USB devices are actually supported? I have a couple M-Audio Midisport boxes. That’s my only Midi to USB interfaces. If those no longer work, then… WHY? And what should we be getting to replace those?
We’re trying to find out why they no longer work. It’s not a question of support. We’re looking to see what has broken there.
I can say that we have always seen those high on failure rate tracking even before the new MIDI stack. There’s something about the device or driver that isn’t quite right.
But right now, MIDISport devices using the vendor drivers are failing under the new MIDI stack. If you have ones that are class-compliant (I believe the newer ones are) you could uninstall the m-audio drivers and use our in-box driver.
Otherwise, you can join us on the discord server at Windows MIDI / Audio and use the workaround in #start-here to revert back.
Pete
Microsoft
Most third-party drivers still work. But some are quite buggy, and always have been.
I checked, and the midisports going back 20 years are all class-compliant. They say they work on macOS without a driver, so they will work on Windows without a driver. The driver was only to support multi-client, which we now have built-in.
Unplug the midisport and completely uninstall the downloaded midisport driver from Settings > Apps > Installed apps
Reboot. If the driver was completely uninstalled, the midisport will be moved over to our in-box class driver.
To verify the driver, you can right-click the Windows logo on the task bar, choose “Device Manager” and then go down to “Sound, video and game controllers”. Right click the midisport and choose “Properties”. You should see “(Generic USB Audio)” as the Manufacturer
If you do not see that, then either the device is not class compliant (it will have a yellow bang next to the device), or the driver was not completely uninstalled.
Disconnect the device, and then go up to the View menu and choose “Show hidden devices”
Then go back down and find the grayed-out midisport entry (there may be multiple). For each of them, right-click and choose “Uninstall Device”
When/if prompted, agree to completely uninstall/remove the driver from the system.
Reboot.
Pete
Microsoft
Followed your instruction and completely uninstalled the Midisport drivers. Rebooted and let it find class compliant drivers from MS. The driver does show as MS from 2026. Now to test
Please let me know how it goes. I’m starting to wonder if within the same model of midiman, some of these were class-compliant and others were not. Maybe a firmware difference.
If it works, and you have a moment, please check to see if it now shows “(Generic USB Audio)” for the driver manufacturer.
Pete
Microsoft
The driver manufacturer does say (Generic USB Audio)
So you’re all set now?
Pete
Microsoft
