none
WinUSB compatible device doesn't get drivers from Windows update RRS feed

  • Question

  • I have an embedded device with USB interface and I'm trying to get it working with Windows 7 without any additional drivers as described here: https://blogs.msdn.microsoft.com/usbcoreblog/2012/09/26/how-to-install-winusb-sys-without-a-custom-inf/

    I added all necessary MS descriptors to the firmware when windows asks for them during USB enumeration, so at the end it is detected as WinUSB compatible device - USB\MS_COMP_WINUSB is shown in the device manager:


    Now I expect Windows Update to get and install the WinUSB driver for it automatically. However this does not happen - I see that Windows contacts the update site, but does not find the driver.

    Do you have any idea why this happens and what should I try else?
    Sunday, July 30, 2017 7:03 PM

All replies

  • The driver for WinUSB compatible device is, obviously, winusb.  If Windows Update does not find updates for it - most likely, the winusb driver is already up to date. Have you expected something else?

    Does Dev. Manager show a yellow bang on this device? If yes, what is the error code? (you cannot insert a picture yet, sorry for this.)  

    -- pa

    Sunday, July 30, 2017 11:13 PM
  • Windows shouldn't need to go to WU to match on a compatible ID. There should be an in box match in %windir%\inf

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, July 31, 2017 1:39 AM
  • yes, device manager shows yellow triangles, with status "driver was not installed (Code 28)". That means that the winusb driver is not available locally. According to the article "If your computer is configured to get driver update automatically, the WinUSB driver will get installed without any user intervention by using the new INF package."
    This does not happen. and I try to find out why and how to debug the problem...

    Monday, July 31, 2017 7:57 AM
  • While waiting for more useful answer, please have look at the logs  ( %windir%\inf\setupapi.dev.log  and Event viewer)

    -- pa

    Monday, July 31, 2017 9:51 AM
  • "No driver found on Windows Update"

    ...

         dvi:      Searching for compatible ID(s):
         dvi:           usb\ms_comp_winusb
         dvi:           usb\class_ff&subclass_00&prot_00
         dvi:           usb\class_ff&subclass_00
         dvi:           usb\class_ff
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\inf'
         inf:      Searched 0 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\inf'

    ...

    ndv: Searching Windows Update for drivers... 12:26:04.955 ndv: Waiting for previous WU search to complete. 12:26:04.956 ndv: Acquired WU search serialization mutex. 12:26:19.484 ndv: About to release WU search serialization mutex. 12:26:30.826 ndv: No driver found on Windows Update. 12:26:30.826

    Is there a way to see the WU request to check if Windows requests the driver based on VID and PID only or if it also uses the "compatible ID"? I tried Wireshark, but since the request is SSL encrypted there is not much to see...

    Monday, July 31, 2017 10:35 AM
  • According to the log, it searched only by compatible IDs. Is your Win7 updated? SP1 at least?

    -- pa

    Monday, July 31, 2017 6:08 PM
  • fresh installed Win7 SP1 64bit with all latests updates from WU.

    • Edited by Gamadril Monday, July 31, 2017 6:44 PM
    Monday, July 31, 2017 6:43 PM
  • Well it looks like a problem with WU. The system has tried to get the driver from WU, with a good ID (usb\ms_comp_winusb).

    -- pa

    Monday, July 31, 2017 9:53 PM
  • Any chance Microsoft would fix it? I chatted with MS support today, they say it is too complex and too specific for them...
    Tuesday, August 1, 2017 1:51 PM
  • Even if they won't, you can install the driver yourself, from the WDK redistributables. You can also add winusb driver into Win7 image for deployment on multiple machines.

    -- pa

    Wednesday, August 2, 2017 11:27 AM
  • This will be a end-user device. The idea behind WinUSB support is to make it easier for the customer to use it without any additional drivers that must be installed manually. If I have to provide a driver anyway, I don't need WinUSB at all in that case...

    • Edited by Gamadril Wednesday, August 2, 2017 2:20 PM
    Wednesday, August 2, 2017 2:20 PM
  • New insight: WU gets the driver on English Windows 7 version and not on German version.
    Friday, August 4, 2017 9:03 AM
  • Final result of the tests:

    Here is the result: 2 VMs parallel installation, same steps, same WU settings. All available updates installed on both VMs.
    Connected Device to English VM:

         dvi:      Searching for compatible ID(s):
         dvi:           usb\ms_comp_winusb
         dvi:           usb\class_ff&subclass_00&prot_00
         dvi:           usb\class_ff&subclass_00
         dvi:           usb\class_ff
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\inf'
         inf:      Searched 0 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\inf'
         dvi: {Build Driver List - exit(0x00000000)} 22:53:31.780
         ndv: Selecting best match from Driver Store (including Device Path)...
         dvi: {DIF_SELECTBESTCOMPATDRV} 22:53:31.781
         dvi:      No class installer for 'TEST-DEVICE'
         dvi:      No CoInstallers found
         dvi:      Default installer: Enter 22:53:31.785
         dvi:           {Select Best Driver}
    !    dvi:                Selecting driver failed(0xe0000228)
         dvi:           {Select Best Driver - exit(0xe0000228)}
    !    dvi:      Default installer: failed!
    !    dvi:      Error 0xe0000228: There are no compatible drivers for this device.
         dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 22:53:31.787
         ndv: Searching Windows Update for drivers... 22:53:31.801
         ndv: Waiting for previous WU search to complete. 22:53:31.802
         ndv: Acquired WU search serialization mutex. 22:53:42.922
         ndv: About to release WU search serialization mutex. 22:54:03.101
         ndv: Found driver on Windows Update, downloading - 0.0 MB... 22:54:03.101

    => everything OK, driver found and installed

    German VM:

         dvi:      Searching for compatible ID(s):
         dvi:           usb\ms_comp_winusb
         dvi:           usb\class_ff&subclass_00&prot_00
         dvi:           usb\class_ff&subclass_00
         dvi:           usb\class_ff
         cpy:      Policy is set to make all digital signatures equal.
         dvi:      Enumerating INFs from path list 'C:\Windows\inf'
         inf:      Searched 0 potential matches in published INF directory
         inf:      Searched 35 INFs in directory: 'C:\Windows\inf'
         dvi: {Build Driver List - exit(0x00000000)} 23:00:35.087
         ndv: Selecting best match from Driver Store (including Device Path)...
         dvi: {DIF_SELECTBESTCOMPATDRV} 23:00:35.087
         dvi:      No class installer for 'TEST-DEVICE'
         dvi:      No CoInstallers found
         dvi:      Default installer: Enter 23:00:35.087
         dvi:           {Select Best Driver}
    !    dvi:                Selecting driver failed(0xe0000228)
         dvi:           {Select Best Driver - exit(0xe0000228)}
    !    dvi:      Default installer: failed!
         dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 23:00:35.087
         ndv: Searching Windows Update for drivers... 23:00:35.103
         ndv: Waiting for previous WU search to complete. 23:00:35.103
         ndv: Acquired WU search serialization mutex. 23:00:43.824
         ndv: About to release WU search serialization mutex. 23:01:03.670
         ndv: No driver found on Windows Update. 23:01:03.670

    Driver not found.

    Looks for me like a Windows issue.

    Friday, August 4, 2017 9:17 PM
  • So now you're ready to resume the talk with the MS support?

    -- pa

    Saturday, August 5, 2017 7:08 PM
  • If I only knew WHERE MS support is... And after searching the internet it seems I'm not alone... After chatting with another guy I got a phone number of the PRO SUPPORT - yea, sound like the best way to talk about technical bugs and sending logs.

    My problem is not very serious, however I'm wondering how many people decided to give up reporting Windows bugs just because there is simply no way to do it...

    I think I will give up as well and use my time for important things.


    • Edited by Gamadril Monday, August 7, 2017 1:35 PM
    Monday, August 7, 2017 12:34 PM