This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello, I have a problem (see subject above).
I have been trying to fix it on my own but nothing seems to work.
I have never had this issue before and I have been Producing music since XP.
On Windows 8 my midi controllers worked just fine. As soon as I updated via windows store, My controllers have become unresponsive.
I have checked (And updated!) under device manager all of the Universal Serial Bus Drivers.
Everything seems to be working fine there, except when running any DAW (digital audio workstation) such as: FL Studio, Cubase, Pro Tools, Ableton, Ripper, Studio One, Reason.
The midi controllers show up as available but do not send or receive any midi messages.
Both my external Audio Interfaces work as far as Outputting sound in both Directwave and ASIO.
But midi does not.
PLEASE HELP, I do not EVER wanna be a MAC fanboy... but this Windows 8.1 update is pushing me away.
No Midi Controllers = No New music from me = Shopping around for a new system pretty soon :(
Any help on this would be greatly appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Description of the issue:
Fix for this issue is in August update released this morning. Please install update. With this fix, you don't have to apply the registry setting to workaround the problem.
www.microsoft.com/.../details.aspx for x86 systems.
www.microsoft.com/.../details.aspx for x64 systems.
-Eliyas
We were able to repro the issue with TEXTECH INTERNATIONAL LTD. (USB\VID_15CA&PID_0101 ) MIDI device. This device works when connected to 2.0 but not on 3.0 port. We debugged the issue and found the regression.
The 3.0 host controller driver in Windows 8.1 is forwarding a MSOS descriptor query to the device and that some how causes the device to get confused. The interesting part is that the even though the device is not fully functional, it doesn't fail any I/O. So from looking at the bus trace, every thing looks good. It is this one query that is sent during initialization causes the device to sulk, and then it never internally recovers.
Windows 8 doesn't send this query.
Another thing to note is that this issue manifest only for composite devices.
Fortunately there is a registry override to inform the core USB stack to not send this query. So I request you to apply the registry setting for now to workaround the issue. We will try to get this fix added to a future update and roll it out widely.
Get the VID/PID/REV ID of the device from the device manager. For example, for the device I'm using the VID/PID/REV values are 15CA/0101/F110. With that, create the following registry entry (this registry key might have been already created in some case) and set the "osvc" value to 00 00.
HKLM\System\CurrentControlSet\Control\usbflags\15CA0101F110\
REG_BINARY “osvc” = 00 00
Unplug and replug the device.
Let me know the results.
The troubleshooter Does not help.
The solution I found was to order a MIDI to USB adapter cable. I tried one of the generic ones, but had problems with generating rapid keyboard sounds and would also issue a full velocity E4 when the sustain pedal was pressed. Another person had the same problem. I send it back and ordered a iConnectivity mio MIDI cable, which didn't work on any of my three keyboards. The last attempt before I changed to another operating system, like Ubunto was to try the Roland um-one MIDI cable, which worked after downloading the 8 driver from their website. Since Windows 8.1 no longer supports a direct connection between the keyboard controller's usb port and the computer's, the MIDI port to USB port adapter is the only fix I could find.
Hi Bassdan,
Thank you for sharing the information and we apologize for not being able to address your concern in a timely manner. I learnt that you contacted to the retailer regarding defective device and I would like to whether you were able resolve the issue?
You may also go through my last response and try hardware and device troubleshooter and check if that helps.
Let us know if we could be of any help and we’ll be more than happy to assist.
Hi Joseph,
Thank you for contacting Microsoft Community.
I understand your concern and would like to know whether you have tried the steps mentioned in the earlier section of this thread?
If you are facing the same issue which seems to be hardware related, then you may try****running hardware and devices troubleshooter and check if it helps. Follow the steps:
a: Press the Windows + C to activate the charms menu or move the mouse pointer to bottom right corner of the screen and you will get the charms menu.
b: Click on search and select settings and type Troubleshooting and select troubleshooting.
c: Click on Hardware and Soundand select Hardware and Devicesand click on next to run the troubleshooter.
Get back to us with the information and the updated status.
We’ll be glad to help you.
