12 Replies Latest reply on May 11, 2017 4:22 PM by rguevara

    USB 3.0 extensible Host Controller Stack in Windows 7 and compatible ID descriptor issue


      Hi there,

      I have got an issue with a custom USB 2.0 device (with our own firmware) regarding enumeration and driver installation in windows 7 using USB 3.0 extensible Host Controller driver.

      The devices uses the BOS descriptor (OS 1.0) to provide a compatible ID (RNDIS) for selecting the appropriate inf file / driver (rndiscmp.inf / rndiscmp6.sys). This works fine in Windows 7 using (native Microsoft) USB 2.0 driver and also in Windows 8 using USB 3.0 or 2.0 with MS driver (on many different installations). But it does not work in Windows 7 using intel USB 3.0 extensible Host Controller (using a VIA Chipset/driver stack it works!). Analyzing USB traffic I can observe that the Descriptor is requested from the device. Hereupon the compatible ID is sent to the PC but it can not be found in registry and hence it is not used to select the driver automatically (evaluating setupapi.dev). The driver must be chosen manually then.

      Actually the USB requests are the same as in the USB 2.0 case but something goes wrong in intel USB 3.0 driver stack.


      Does anybody have any idea? Or any additional debugging possibility?


      Thank you very much!