Thank you for the debugging, this was making me crazy trying to figure out why my MIDI controllers stopped communicating. Thought for sure it was the recent Win 11 update, never would have thought it was related to my UAD Console! I rolled back to UAD Console v1.2.4 and all is good!
2 Likes
It appears that UAD has a fix, I have not installed it yet but the feedback on the UAD Forum is positive. I’m going to stick with v1.2.4 for now, I’ve lost too many hours this week on this issue.
Version 1.2.7 Supplemental — October 24, 2025
Fixed
-
(Apollo UAD Console) Resolved an issue that prevented Tap Tempo from functioning
-
(Apollo UAD Console) Resolved an issue that prevented Tap Tempo and Plug-in Scenes recall via MIDI
-
(Windows) Resolved an issue that caused MIDI issues with third-party applications
1 Like
The “midi” entry wasn’t removed (at least on my system); the registry remained unchanged after I installed the update.
1 Like
I use 2 ‘Silverface’ Apollos via Thunderbolt on Windows 11 25H2 and had updated to the first UA Console v1.2.7 and had been experiencing issues with my midi controllers being unresponsive too. On checking my registry, I am not missing the first ‘midi’ entry as you are. I’m on Cubase PRO 14.0.40. I’ve just updated the UA Console (still called v1.2.7 but has been ‘repaired’ in UA Connect app) which seems to have resolved midi devices not triggering or being blocked for me.
1 Like
I just used the link that was given in the forum and copied into Google:
uaconnect://main/apollo?action=download&id=uad-console&version=1.2.4.602
Windows MIDI Services ?
Thank GOD I found this post. I have been beating my head against the wall trying to figure out why my AKAI LPK25 class-compliant controller and Softube Console 1 Fader Mk III had stopped working (!!!). What a nightmare the past few days have been!
Here I was thinking it was my recent update to Windows 11 that just happened to coincide with this UAD Console update (why is that ALWAYS how it goes?). I’ve been cleaning out MIDI entries in the registry and old ghost USB device entries in Device Manager, all to no avail, trying to get these things to work (thanks, ChatGPT, but you kinda missed on this one…).
UAD SERIOUSLY needs to get their crap together with their Windows software - we’ve had nothing but problems over the years. I don’t even use their interfaces, but DO have their octo PCIe card installed, which I barely use any more. I think it’s time to rip all of that out and never look back.
New Windows MIDI stack and SDK. Includes multi-client MIDI, timestamps, scheduled messages, app-to-app MIDI, loopback endpoints, both MIDI 1.0 and MIDI 2.0, new tools, scripting support, device customization (naming, images, description), better hot plug/unplug support, and more.
Oh, and it also includes a tool to clean up reg entries in case someone accidentally uses a tool like the Korg Driver utility and messes up their MIDI setup. (Third-party USB MIDI drivers generally aren’t needed anymore for class-compliant devices).
Coming to Windows 11 retail in Q1 2026. Currently in Windows Insider Canary releases. Not yet compatible with retail Windows 11.
Existing apps using WinMM MIDI 1.0 or WinRT MIDI 1.0 (like Cubase can) will be able to access some of the new features (like multi-client) without changing any code, because we’ve replumbed those APIs to talk to the new MIDI Service. The service also translates between MIDI 1.0 and MIDI 2.0 automatically. That backwards compatibility is actually why it’s shipping in Q1 instead of now, because we found some issues with DJ controllers that we’ve fixed.
Pete
Microsoft
1 Like
Is it all working now?
Pete
Microsoft
Ah, I see — that’s what allowed you to identify the issues!
Installing it won’t mess up my current setup, right?
And is there any real benefit for now, since Cubase doesn’t yet support the new implementations like MIDI 2.0?
Have you fully read what @Psychlist1972 wrote:
It is currently only in the Insider channel releases
2 Likes
Ok 
1 Like
Yes, though the latest Softube update the VERY NEXT DAY (lol) goofed up my install for the Console 1 Fader Mk III…I have a support ticket in for them. But, the AKAI MIDI controller works just fine since rolling back the UAD Console.
1 Like
I rolled Nuendo back to 14.0.32 and that seems to have helped with the Console 1 functionality and their latest update (October 28). I’m keeping things like this for a while until it all gets ironed out.