I have recently lost all ability to communicate with virtual instruments via MIDI in Win 11. I have been in touch with multiple sources, which all agree this is due to a recent Windows update and is not uncommon. Although there are work-arounds available, they don’t work for everyone afflicted (like me), but there is a lot of work behind the scenes, so I am hopeful. Interesting that Micro$oft does not seem to be involved in this effort, but I might be mistaken. Here’s hoping this doesn’t happen to you.
Hi @dockahn ,
That’s not a good experience.
Has it to do with older hardware that have incompatible drivers to that Windows 11 update? Sound like it to me.
Any issues with software?
Which kind of CPU are you using? ARM?
I hope you will find working solutions.
Thanks for your willingness to make suggestions. I have a Creation Station built by Sweetwater specifically built to optimize Windows for music applications. It is not old, and it was working without any problems during my session last Sunday afternoon. Sunday night was a different story. No issues with software. I can play the notes on the virtual keyboards with my mouse. But no MIDI controllers are listed to be able to choose from. It’s as though there are no MIDI controllers that are connected.
I have some suggestions which have been forwarded to me but haven’t had the opportunity to implement them.
My main purpose of posting this malady is that the tech support people I’ve talked to have stated that they are seeing a lot of this recently, and I want people to know that if it happens, it’s not just them. I spent hours switching out computers, audio interfaces, and cables wondering if I had an equipment failure before I was able to contact support (because it happened on Easter).
OK.
Let us know how things turn out.
Good luck.
Be sure Windows MIDI Service is running.
HI @dockahn
It sounds like you’ve had the Midi 2.0 stack installed which can, and does cause some isssues for some people.
You can check for the Midi 2.0 stack by running the tool from https://microsoft.github.io/MIDI/ and it will tell you if it is installed, if it is then it’s the likely cause of your current issues.
A quick Google (other search engines are available) shows some interesting results… for ‘Win11 Midi 2.0 Stack issues’ https://devblogs.microsoft.com/windows-music-dev/troubleshooting-recent-midi-issues-in-windows-11/
HTH!
You can also check out the new Windows MIDI Discord server here:
Lots of information on how to set up your hardware, work around problems, ask questions etc.
Pete Brown from Microsoft is present on this Discord server and is incredibly helpful - he has personally helped me out with a couple of issues with my MIDI hardware. Pete is a Principal Software Engineer in the Windows Developer Platform team at Microsoft and he is also the current chair of the Executive Board of the MIDI Association.
It’s worth pointing out that the implementation of the new MIDI service and stack has exposed problems with drivers which have remained ‘invisibly’ broken over the years. Korg now recommend uninstalling their drivers, and InMusic (who supply drivers for Akai, M-Audio and other brands) are currently working on fixing their drivers. There are workarounds for owners of hardware from these brands until those fixes are in place.
3 Likes
Thanks for the response @Yearofthegoat
It’s long overdue that they fixed the ‘10 items or less’ issues with that driver, fingers crossed it won’t be too long now.
Nothing to wait for if you have the new Windows MIDI Service - just uninstall the Korg drivers, apply the ‘midifixreg’ from Github (here: Releases · microsoft/MIDI · GitHub, scroll down to ’ Korg Driver Install/Uninstall Repair Tool’), install the Microsoft in-box driver(s) for your Korg hardware and that’s it fixed.
Did exactly that for my nanoKontrol2.
1 Like
Thanks for so many helpful suggestions. Matjones: I suddenly couldn’t access my Nautilus software for backup, so I went to the Korg website with the intention of re-loading my driver, where I found that I should remove the driver and was given detailed instructions as to how to do so. All of my MIDI functions were working at that time, but as soon as I followed those instructions (which only had to do with Korg products), I lost the ability to communicate via MIDI. I agree the Top Ten was a big headache.
As to the other suggestions: I regret that I have not had time to try any of them. I maintain 27 acres and six buildings, and spring is a very busy season. There is a lot of physical activity, and once the sun goes down, I’m either too sore or too tired to head to the studio. Good news is that most of the required work is done after today, and I hope to be able to follow everyone’s guidance starting tomorrow.
Thanks again for everyone’s willingness to help, and for your great suggestions. As the saying goes: fingers crossed.
HI again @dockahn
I uninstalled that Korg Driver immediately after reading @Yearofthegoat post lol, i’m glad to see the back of it, not had a chance to check my Minilogue XD yet though, the librarian tool that comes with it is great over USB Midi, mega slow over DIN though, it’ll be interesting to try when i have time.
Please do update us when you can as it might be useful for other forum users at some point too.
After you uninstall the Korg drivers, you must fix the Windows registry with the midifixreg tool (or reinstall Windows!). Reboot after that and use the Windows driver(s).
The symptom of not fixing the registry is MIDI devices (even non-Korg ones) will show up in Device Manager, but not in any applications. Takes a couple of minutes only.