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.
Yeah. I just bought a Samson Carbon 49 Keyboard MIDI controller to use with FL Studio, and all it came with was a cheapo DAW, because apparently it was supposed to work with the Generic MIDI drivers that the devs decided would not be needed for METRO Tablets so it had to go in the Desktop environment, too. :/
Can we get a Plug-and-play Generic MIDI Driver back, guys? Some of us have software that *works* but about as well as using a mouse instead of a pen tablet in a graphics program.
My usb to midi cable no longer works. I use this with my keyboards and other midi-based hardware.
I've followed the MS blog to capture the usb events and determine if the osvc value can be set.
I set the osvc value to the correct usb device in the system registry but after a reboot and device reconnect it still shows no signs of life.
I've tested the cable on windows 7 and even an iPad and the device works perfectly fine.
I can't believe the update from Win 8 to 8.1 stuffed up midi drivers so bad.
Is there any alternative generic midi driver I can try???
since the upgrade to windows 8.1 I have no midi drivers. I have 5 different software programs that use midi in my DAW which were working fine until the upgrade. Now none of them work and there are no midi drivers to be found anywhere. Some programs will show a msg that no midi drivers are in stalled in windows. Right now I am out of business on my midi. How can I retrieve or find my midi drivers? Thanks.
Why do I not get an answer? I cannot record the band as scheduled? I need help. I called Microsoft and they want $100 or $150+ to try to answer my question and resolve my problem. Why can't people just be honest? If Microsoft has made a misstate on the 8.1 update, or decided to not support midi anymore, why not just say so? I am stuck until I can get this fixed. I couldn't believe they want me to pay for them to fix this problem. The 8.1 update fouled up my workstation. it was working fine for over a yr before the update. I need help and there seems to be no where to turn. all I see here is people with similar problems and MS seems to not even admit there is a problem. the drivers are still on the computer and the new update just won't point to them. I have been doing midi since early 90's. ..the problem is in win 8.1, so why won't they just say so and fix it? All my stuff worked fine on XP and win 8.0. I don't want to sound angry, just factual. and I would like some answers and some help....I have always been an avid Microsoft supporter and I just want to get this fixed.
