Cubase 13/14 - Windows 11 - and MIDI Errors

Cubase
1

My class-compliant USB MIDI keyboard suddenly stopped sending MIDI data to Cubase 14. It is recognized by Windows, appears in Device Manager, and shows up as active in Cubase under Studio Setup > MIDI Port Setup — but no MIDI data is received when playing. The same problem occurs in other MIDI-enabled software such as Divisimate, Chordie, and standalone VST hosts.

This is not a hardware failure. The keyboard works flawlessly on another Windows machine and successfully sends MIDI to browser-based MIDI testing tools. The issue began before I upgraded to Windows 11 25H2. I only updated in an effort to solve the problem, but the situation remained unchanged.

I’ve already performed a full clean Windows installation and reinstalled all drivers, including chipset, USB controller, and audio drivers. I’ve tried multiple USB ports (2.0 and 3.0), cables, disabled USB selective suspend, and turned off power-saving options for USB devices. I also cleared any potential registry conflicts under Driver32 related to wdmaud.drv and MIDI port slots. No duplicate or ghost devices appear in Device Manager.

MIDI-OX and other local monitoring tools do not register incoming MIDI data, and MIDI-OX sometimes reports a memory error when the keyboard port is selected. Despite that, the exact same keyboard sends MIDI data perfectly to an online WebMIDI tester on this same machine.

I also own Audio Imperia’s FVDE Midi controller, which similarly loses MIDI input after a reboot — suggesting a deeper system-level MIDI issue. Event Viewer logs repeatedly show Kernel-PnP Event ID 442 for the keyboard device, indicating that its settings were not migrated due to a partial or ambiguous device match, even after a clean OS install.

This device is class-compliant and does not use a dedicated driver. The problem appears to be at the level of Windows MIDI routing or driver enumeration. I need help understanding why Cubase and other MIDI applications cannot receive MIDI data, despite the device appearing functional at the system level and working on another computer.

Any insight into potential blocks or misrouting within Windows or Cubase would be greatly appreciated.

4 Likes
2

You mentioned clearing registry conflicts in Drivers32 (note the plural). That means you should have exactly one MIDI(n) entry in there, midi (not midi0, but just midi) with wdmaud.drv listed as the REG_SZ value.

Is that what you have?

In device manager, you should see your MIDI controller under “Sound, video and game controllers”, and if you right-click it and choose properties, the manufacturer in the General tab should be (Generic USB Audio) . That means our in-box USB MIDI 1.0 class driver.

If it’s working with a WebMIDI tester on that same PC, then I expect that the above is all perfectly functional, as WebMIDI ultimately calls down to the same APIs these other apps use.

You didn’t mention having any other MIDI software (or WebMIDI pages) running. I would also check that, because maybe something else has the port open? For Windows today, only one app can have any port open at a time. Others will see the port, but will fail to open it and therefore fail to send/receive data. The memory error is a common message some apps provide when that happens.

Pete

3

Are you using a Universal Audio Apollo interface?

6

Not sure if this is directly related, but it might help others using Windows 11 with Apollo interfaces.

Our studio PCs are running Windows 11 versions 25H2 and 24H2 with Apollo interfaces. We encountered a very similar issue, and after several rounds of debugging, we discovered that Universal Audio’s recent UAD Console v1.2.7 update seems to be the cause. Its UAMixerEngine process occupies a lot of ports when it starts with the system. Rolling back to UAD Console v1.2.4 resolved the problem completely.

5 Likes
7

Same problem here….
And rolling back to UAD Console v1.2.4 resolved the problem also for me.
Thanks!

2 Likes
8

Can you uninstall that KB? It’s under Windows Update > Update History and head to the bottom under “Uninstall Updates”. The MIDI bits accidentally went out in that KB, not in the original 25h2 install.

KB5065789 is the one to look for.

Sorry for the problems here. I was aware of the MIDI bits, but until yesterday, not anything that messed up registry entries or corrupted wdmaud.drv.

Pete
Microsoft

9

Sorry, was going by the email I got, but looks like those messages were deleted.

So did everyone here with the issue also have a UA device? @TY-1 did you find your issue was with the UA device? You were pretty adamant in the deleted post that it was a Windows update, so I want to check to see if it was the same fix Geng mentioned.

Just in case that pops up again, we don’t have any way to push MIDI bits to Windows 10. The only issue I’m aware of is with Windows 11 and the KB mentioned here.

Pete

10

yes indeed. Apollo USB on windows 11

11

Have you tried installing an earlier version of the UAD driver and Console? From what we’ve seen around the LA circle, the MIDI issue seems to be caused by the UAD v1.2.7 update, which came out right around the same time as Windows 11 25H2.

Maybe try uninstalling the UAD driver and Console, then install UAD 11.7.1 and UAD Console v1.2.4. See if that solves the problem. (If you just Google “UAD Software Archives,” the page with the earlier versions should pop right up.)

12

since your reply still searching how to download an older version of UAD googling and digging. willing to try EVERYTHING at this point, I just found 1.7.0 on https://www.touslesdrivers.com/ maybe this will do the trick

13

Do you still have the setup file by any chance?

14

The reason I mentioned Google is that UA no longer uses a standalone setup file. The UAD Console is now installed through deep links via the UA Connect app.

You can copy and paste the link below into your browser to see if it works:

uaconnect://main/apollo?action=download&id=uad-console&version=1.2.4.602

15

It is the Apollo TWIN USB, the soulution was this:

I first uninstalled EVERYTHING under the UAD nadme.

Then I went into the registry editor (win + R - type regedit) deleted all the midi 1 till 9 in my case. I was mising a so called midi 0 or just midi, so gpt adviced to create myself

  • click new - String value - ENTER
  • once you create double click and under midi data I put wdmaud.drv.
  • delete the rest midi files and reboot

registry
registry833×824 154 KB

I have and older scarlet focusrite 2i2 3rd Gen I re-installed the drivers, connected it and another reboot. Now works like a charm. I guess I have the apollo just to look at I think UAD should really get their Sh… together with this broken updates. If you guys have a workaround PLEASE let me know I dont think I should put this topic as resolved we need some brainstorming here.

16

Hi,
I’m having a very similar issue these past few days, but with my X-Keys controllers connected to MacroWorks.
From that software, I send — by pressing the controller buttons — macros and MIDI notes, using the Bome MIDI Driver.

The MIDI data is then sent to Cubase, where I’ve created two separate MIDI Remotes for each controller.
Everything shows up fine in the MIDI setup, so in theory it should all be working.
I also have two Stream Decks and a Novation master keyboard, and both of those still send MIDI without any problem.
But it looks like the MIDI ports from my two X-Keys are blocked, like no data is coming through anymore.

Everything was working perfectly until Wednesday, October 15, 2025, and since the next day, nothing works anymore.
It’s driving me crazy because I haven’t changed anything in my setup.
I also have a UAD Apollo X4, and I’ve noticed the same thing — they keep pushing automatic updates with their new system, which might be related.

17

Great, I followed your advice, downgraded the version and it works again. I would never have imagined that the problem could come from this damn UAD console. Thank you very much!!!

2 Likes
18

how do you guys manage to downgrade for me the UA connect jumps immediately to update and I cant install old UA console. could any of you share the protocol

19

Glad it helped!
I did some digging as well. UA recently introduced their new interface, the Volt 876, which is their first MIDI-supported audio interface. It likely still has some rough edges or dead loops in the code that end up hijacking the MIDI ports.

On our end, Windows 11 25H2 has been running perfectly so far. I’d also recommend trying out Windows MIDI Services — I actually used it while debugging the issue. (Shoutout to Pete and the team behind it)

1 Like
20

Check out their version archive website or just try the deep link.

21

Here’s the thread on the Universal Audio problem as well as the version information for the fix

Pete
Microsoft

22

For those of you with the UA problem, can you all confirm that the “midi” entry was removed in your registry under

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

image
image677×277 16.8 KB

This is the entry I’ve seen missing from the start of this thread as well as a thread on our forums. I don’t see that reported in the UAD thread, and don’t know if their update also fixes that.

Pete
Microsoft