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.
I don't understand why M.S just won't admitt there's a problem. Prepared excuses unbelievable to remove midi control and replace it with M.S sound mapper. stop or I,m getting real close to going Mac.
Hi, donmeczblast. I am curios how you solved this problem. My Midi Controller (Novation Launchkey 49 and Numark Omni Control) does not work on usb 3.0 ports. They do on win 8.1 on usb 2.0, but not 3.0 (I have to mention that I only have 3.0 usb ports on my laptop). I am wondering if this is the problem at you and if it is, how did you solve it, or how would you think I can solve mine ... A little help would be very appreciated. Thank you so much
P.S. Ive seen that these guys dont know very much so I`m putting my hopes in you :) Thanks Again. Cheers
Hi @MarianMenfiu. I found Eliyas solution worked flawlessly for me. I know a few people either could not find their correct VID PID or they did but the "work-around" was not successful. I posted a step by step in page 8 of this thread. I will paste it here now and hope that it really helps you as I know how crippling it is to be without controllers for certain projects and tasks.
All the best and warm regards.
Go to device manager
Click on Universal Serial Bus Controlers
Plug in your Midi Controller to any USB 3.0 port
Once you see your device appear on the list Right click on it and go to properties
Click on the Events tab
from the Information box in the bottom you will notice your VID/PID/REV "Instance ID"
Mine say: Device USB\VID_0644&PID_800E/0100. **!!yours will be different!!**
So my Flag is gonna be: 0644800E0100
Now on your Desktop's Taskbar: Right click on your Start button and select Run
Type in: Regedit
Click OK
Navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/usbflags/
Now find the folder with your VID/PID/REV Instance ID (Mine is 0644800E0100)
On the right hand of the editor, Right click and select: New
Now select: Binary Value
Name it: osvc
Right click on it and select: Modify
Set the value: 00 00
Close the regedit window
Unplug and Plug back in your device... and Voila!!!
If it didn't work make sure you selected the correct folder with your correct VID/PID/REV
Good luck man
