The Yamaha USB-MIDI Driver (V3.1.4 or earlier) will be blocked during installation on Windows 11 with the April 2026 security update installed.
Please download and install the Yamaha USB-MIDI Driver V3.1.5 to address the issue and to be able to use the CMC properly again.
Hello, I updated the driver but I can’t run more than one CMC device now. Hoping something can be done, I use the AI and CH together for radio show editing and it makes the process so much better!
They appear in Device Manager as follows, the order depends on which was connected first. Sometimes it’s hard to have the second get recognized at all without unplugging both again.
Steinberg CMC-CH- 1
Steinberg CMC-CH- 1
2- Steinberg CMC-AI- 1
2- Steinberg CMC-AI- 1
When connecting them via usb hub, only one will be usable, the other won’t show in Device Manager or the Cubase drop down midi input/output selection, even though it’s powered and will work if the other is removed from the hub.
Only the first connected device shows up as expected in the midi remote device setup in Cubase. The other device can be seen in the drop down midi input/output selection, but it doesn’t seem to work with anything eg. generic remote. Trying to add it by name via the + drop down menu does nothing.
I’ve reinstalled the driver, restarted the computer, and used different cables and usb ports, with the same results.
These are the event messages for both instances of each devices:
Device settings for SWD\MMDEVAPI\MIDIU_KSA_3652632443384315077_0_0 were not migrated from previous OS installation due to partial or ambiguous device match.
Last Device Instance ID: SWD\MMDEVAPI\MIDII_14D763C1.P_0000
Class GUID: {62f9c741-b25a-46ce-b54c-9bccce08b6f2}
Location Path:
Migration Rank: 0xF000FFFF0000F120
Present: false
Status: 0xC0000719
Device SWD\MMDEVAPI\MIDIU_KSA_3652632443384315077_1_0 was configured.
Driver Name: c_swdevice.inf
Driver Package ID: c_swdevice.inf_amd64_845d51425d14f98b
Class GUID: {62f9c741-b25a-46ce-b54c-9bccce08b6f2}
Driver Date: 06/21/2006
Driver Version: 10.0.26100.1
Driver Provider: Microsoft
Driver Section: SoftwareDevice
Driver Rank: 0xFF3000
Matching Device ID: SWD\GenericRaw
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_0499&PID_1065\YMHFF32548D3136473243104049
Device SWD\MMDEVAPI\MIDIU_KSA_3652632443384315077_1_0 was started.
Driver Name: c_swdevice.inf
Class GUID: {62f9c741-b25a-46ce-b54c-9bccce08b6f2}
Service:
Lower Filters:
Upper Filters:
Thanks for taking a look, please let me know any suggestions.
This is fixed for the November update of Windows.
The driver for those devices enumerates the endpoints as though they are all part of the same actual physical device. That’s different from how most any other driver behaves, so we had to special-case this.
If you need this fixed now, and don’t need the features of the new MIDI stack, instructions on switch the API mode to the Legacy mode are here:
Pete
Microsoft
Great, thank you very much.
Will the fix just be the enabled mode switch option, or will these devices be expected to operate using the new MIDI system?
Thanks again!
For folks who want much more detail than requested, here’s how port names will be generated come the November release.
Pete
Microsoft
Thx for the info how to change the API mode. This worked as described by adding the registry entry and setting it to ‘1’ (i.e. legacy mode), plus system restart.
I had six different CMC types attached and it seemed only one of them worked in C15pro on OS Win11pro (with recent updates installed, but not yet 26H2). Control for all six units is back after changing into legacy mode. Won’t try hybrid mode.
Is the registry switch persistent? In other words: Will this have to be changed manually to ‘0’ after the Nov update in order to actually have the new mode working or is the update intended to set that automatically?
The naming updates have moved to 2027, so won’t be in in November.
We don’t switch your API mode for you. It stays at what you have chosen.
Pete
Microsoft
