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.
Thank you Eliyas!
Not a response to the previous post. Just sharing link to a blog that we just posted describing the issue and a workaround.
We are trying to get a fix rolled out in a future update. I will update you guys when it happens.
Thanks,
Eliyas
Hi Turisti,
On a quick glance through Arturia's Knowledge Base (http://www.arturia.com/evolution/kb) there is mention that some devices need to be placed into "MIDI Controller" mode. However, I couldn't find if the MiniLab had that requirement. Also, you've already mentioned that this works as is on Win7 and I will assume you didn't configure the device?
At this point you should reference Arturia's knowledge base and/or contact their customer support. This seems to be specific to the device's setup and Arturia knows the specifics of how they communicate with their device.
Thanks,
Kate
Hi Kate
My keyboard is an Arturia Minilan as well.
I'm having the same issues. Been having a conversation with Arturia's Tech Support for almost two months now. The keyboard works flawlessly on my other Windows 7 computer.
The computer I want to be able to use it with is a Windows 8.1 64 bit version with only USB 3 ports.
Tried the reg mod thing, didn't work, but the computer is obviously communicating the keyboard; the lights on the keyboard started flickering when I changed the registry.
The keyboard shows up under Devices (not the Device manager though, weirdly) and Windows says it "Works" but the disconnect sound keeps playing, and the lights of the Minilab do a little dance. It's like it's stuck in a connection loop.
They just released an update for their "Analog Lab"(was 1.0.5, now 1.1) software which contains some sort of driver, I'm really not sure as to what exactly it may do, probably some communications protocol of some sort which doesn't seem to do the trick. For me at least.
My guess is that this is on "your end", seeing as the keyboard works great under Windows 7. There's no drivers anywhere to be downloaded, except for the Analog Lab, which is optional if you want to use the keyboard as a midi controller (class compliant).
Cheers
