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.
I am using 8.1 will all updates and am having the same issues with two midi keyboards. After repeatedly plugging in and unplugging, they will work for a few seconds and fail.
The device IDs indicate the VID and PID; however, there is no REV
In addition the system is not granting permission to edit the registry key, although I am the administrator.
Very frustrating. I have to somehow resolve this issue.
Hi Bassdan,
Thank you for writing your concern on Microsoft Community.
We understand how you feel about the situation. I would like to have more understanding with the issue so that we could work it out faster. I would appreciate if you could include some more information.
I suggest you to check whether the Device driver gets installed successfully or not when you plug it in.
I would also suggest you to uninstall and reinstall the device driver and check if it helps. Here are the steps:
A: Press Windows Key + R on your desktop screen to go to run command box.
B: Type devmgmt.msc and hit Enter.
C: Look for the Keyboard device name, right-click and then click Uninstall/Remove Device.
D: When you are prompted to confirm that you want to remove the device, click OK.
E: Unplug the device and plug it back after a couple of seconds.
F: Restart the computer.
After the computer restarts, the drivers will be automatically installed.
If this does not fix the issue you may consider reinstalling the device driver by contacting to the manufacturer.
Hope it helps. Share the results and feel free to reply for further reference.
We’ll be glad to help you.
Navneet,
I have done all that, as have others on this thread.
The previous solution posted was to write registry keys for Windows 8.1 to not send the MSOS descriptor query which confuses the midi device per this article:
I also attempted to use Message Analyzer per the following article; however the current version is different than the one described, and failed the trace.
I performed the steps in this article:
For my M-Audio Keystation Pro 88 MIDI controller:
VID = 0A4D
PID = 00B5
REV = 0101
For my M-Audio O2 MIDI keyboard controller:
VID = 0763
PID = 0115
REV = 0125
I constructed the following keyset and set ovsc=0
HKLM\System\CurrentControlSet\Control\usbflags\0A4D00B50101
REG_BINARY osvc = 00 00
HKLM\System\CurrentControlSet\Control\usbflags\076301150125
REG_BINARY osvc = 00 00
Neither "fixed" worked. I also tried both controllers on a different computer running Windows 8.1. Same problem. The issue did not exist in XP.
