USB MIDI Device Doesn’t Work on USB 3.0 Port - Microsoft Community

hello,

before ask question, i've had chance review: windows 8.1: usb midi device works on usb 2.0 port, doesn’t work on usb 3.0 port https://blogs.msdn.microsoft.com/usbcoreblog/2014/01/21/windows-8-1-usb-midi-device-works-on-usb-2-0-port-doesnt-work-on-usb-3-0-port/   i referencing blog in question. 

i'm running windows 10 education , have usb midi device i'd connect daw (fl studio or ableton) receive error message when connecting device: usb device not recognized. i've learned it's feature descriptor request that's creating error. followed of steps in above blog, i'm unable construct registry key location the idvendor, idproduct, , bcddevice values. the values 0's. unable complete steps , device cannot enumerate or recognized. have installed previous driver software compatibility settings no avail. steps necessary windows 10 recognize usb 2.0 midi device? driver need created scratch? happy contribute solution, need better understand problem. 

here usbview connection:

    =========================== usb port2 ===========================

connection status        : 0x02 (device failed enumeration)
port chain               : 2-2
properties               : 0x01
 isuserconnectable       : yes
 portisdebugcapable      : no
 porthasmulticompanions  : no
 portconnectoristypec    : no

      ======================== usb device ========================

        +++++++++++++++++ device information ++++++++++++++++++
device description       : unknown usb device (device descriptor request failed)
device path              : \\.\usb#vid_0000&pid_0002#5&3afd18bd&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
device id                : usb\vid_0000&pid_0002\5&3afd18bd&0&2
hardware ids             : usb\device_descriptor_failure
driver keyname           : {36fc9e60-c465-11cf-8056-444553540000}\0025 (guid_devclass_usb)
driver inf               : c:\windows\inf\usb.inf
legacy bustype           : pnpbus
class                    : usb
class guid               : {36fc9e60-c465-11cf-8056-444553540000} (guid_devclass_usb)
interface guid           : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (guid_devinterface_usb_device)
enumerator               : usb
location info            : port_#0002.hub_#0001
manufacturer info        : (standard usb host controller)
capabilities             : 0x44 (removable, rawdeviceok)
status                   : 0x01806400 (dn_has_problem, dn_disableable, dn_removable, dn_nt_enumerator, dn_nt_driver)
problem code             : 43 (cm_prob_failed_post_start)
address                  : 2
power state              : d3 (supported: d0, d2, d3, wake d0, wake d2)

        ---------------- connection information ---------------
connection index         : 0x02 (2)
connection status        : 0x02 (devicefailedenumeration)
current config value     : 0x00
device address           : 0x00 (0)
hub                   : 0x00 (no)
number of open pipes     : 0x00 (0)
device bus speed         : 0x00 (low-speed)

        --------------- connection information v2 -------------
connection index         : 0x02 (2)
length                   : 0x10 (16 bytes)
supportedusbprotocols    : 0x01
 usb110                  : 1 (yes)
 usb200                  : 0 (no)
 usb300                  : 0 (no)
 reservedmbz             : 0x00
flags                    : 0x00
 devisopatssorhigher     : 0 (is not operating @ superspeed or higher)
 devissscaporhigher      : 0 (is not superspeed capable or higher)
 devisopatssplusorhigher : 0 (is not operating @ superspeedplus or higher)
 devissspluscaporhigher  : 0 (is not superspeedplus capable or higher)
 reservedmbz             : 0x00

    ---------------------- device descriptor ----------------------
blength                  : 0x00 (0 bytes)

      -------------------- string descriptors -------------------
string descriptors not available  (because device has problem code cm_prob_failed_post_start)

here system info: 

os name microsoft windows 10 education
version 10.0.16299 build 16299
other os description not available
os manufacturer microsoft corporation
system name desktop-o8gh2vg
system manufacturer to filled o.e.m.
system model to filled o.e.m.
system type x64-based pc
system sku sku
processor amd fx(tm)-6300 six-core processor, 3500 mhz, 3 core(s), 6 logical processor(s)
bios version/date american megatrends inc. 2701, 3/24/2016
smbios version 2.7
embedded controller version 255.255
bios mode legacy
baseboard manufacturer asustek computer inc.
baseboard model not available
baseboard name base board
platform role desktop
secure boot state unsupported
pcr7 configuration binding not possible
windows directory c:\windows
system directory c:\windows\system32
boot device \device\harddiskvolume2
locale united states
hardware abstraction layer version = "10.0.16299.15"
user name desktop-o8gh2vg\alex
time zone mountain daylight time
installed physical memory (ram) 8.00 gb
total physical memory 7.90 gb
available physical memory 4.86 gb
total virtual memory 9.15 gb
available virtual memory 5.66 gb
page file space 1.25 gb
page file c:\pagefile.sys
virtualization-based security not enabled
device encryption support reasons failed automatic device encryption: tpm not usable, pcr7 binding not supported, hardware security test interface failed , device not instantgo, un-allowed dma capable bus/device(s) detected, tpm not usable
hyper-v - vm monitor mode extensions yes
hyper-v - second level address translation extensions yes
hyper-v - virtualization enabled in firmware yes
hyper-v - data execution protection yes

hi alexander,

to determine why having issue constructing registry keys, recommend post query in our microsoft developer network forum. complex troubleshooting required address concern, , msdn forum focuses on advanced technical discussions microsoft products. acquire help, accurate tips, , methods address issue.

if have other concerns, don't hesitate reach out us.

Windows / Windows 10 / Devices & drivers / PC