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'm also having trouble. Trying to connect a Samson Carbon 49 keyboard. It's saying the driver doesn't work?? I plug it into my iPad and it works fine. Frustrating. Any help would be greatly appreciated.
I also have this problem. I tried to change the registry and then unplug and plug the device but nothing. Please help me i still cant solve this problem.
I have a work around that works for me - issue was Medeli / Session Pro 404D drums would not trigger any of my midi drums kits after new PC running win 8.1 and new DAW Sonar X2 Producer installed in my studio- not sure if this was USB 2.0 or USB 3.0 - as the PC is an eBay refurb - suspect USB 2.0? Anyway........ tried using the MIDI Connection from Session Pro drums - nothing, tried the USB connection (tried new drivers, learnt that USB cable length matters) still nothing. My new Komplete Kontrol midi controller triggered the drums, my Akai MPD 24 triggered the drums - my Yamaha Keyboard PSR 295 even triggered the drums - but my Session Pro would not trigger anything......
So - searching on eBay for a powered 'midi hub' of some sort I came across a £3.95 cable that takes a midi signal (it has midi in and midi out cables) and converts them to a USB plug on the other end - USING IT'S OWN DRIVERS - that now means that my Session Pro 404D's (made by Medeli, I think) now trigger all of my midi kits (except the ones in Native Instruments Komplete - working on this).
This fixed the problem for me, I suspect because it has it's own drivers? Make sure to buy the new version that states it works with Win 8 onwards.
I am in no way affiliated with the manufacturer of this product - just wanted to pass on my little fix for this issue which has already eaten every spare moment of my time for a week! : )
Best
Jim
