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.
Hi Rajith. Thank you for replying...
*sigh*
USB Midi controllers have been compatible with windows ever since I can remember.
I have used all kinds of them in: Windows XP, Windows Vista, Windows 7, AND Windows 8.
They are devices that allow you to control certain parameters inside a DAW or Standalone Syntheziser
by sending and receiving MIDI messages.
Examples of USB MIDI controllers are:
Midi Keyboards. Midi Drumpads. DJ controllers. etc.
You do not even need to install the factory driver if you do not want to. A midi controller will always
send and receive midi messages with windows via USB drivers and windows midi mapper driver.
The problem is driver related with this version of windows 8.1 , I have read many posts by many Producers from many different genres that have also experienced this same issue.
I would appreciate if you could stop giving me the generic answer and really Help me.
I am very close to not purchasing another windows product ever again and influencing my peers to do the same.
There are components in Windows that seem to be standards, midi comparability are one of these accepted things. I am having the same problems with Win 7 which was a reluctant change. Suddenly
after an update my midi gear lost all output capability and MS midi playback took over. The way to get in a niche market is not to kill an established standard to implement your own.
Really upset here and let down I have an awful lot of gear that depend on this function. Now I need to
go back to XP of switch over to the Mac Os solution which by the way also supports Firewire.
Was Windows for life,
Now looking for a mac.
Presto
solucion definitiva para el problema usb midi, tirar a la basura el windows 8.1 y poner otro sistema operativo.
hi cpm80 what turtle beach product are you using, i used to have their voyetra piano product but they stopped supporting it a long time ago and i wonder if you got something like that working with windows 8.1 ?
