Windows10 USB Problem 0xC0000182 - AUDIO + VCOM Composite Device

Raggio 6 Reputation points
2021-09-13T08:39:02.757+00:00

Hi all,

after developing the firmware for a composite USB application (AUDIO + CDC_VCOM) for an STM32F446 device, I'm facing strange behaviour in the driver side for Windows (I've tested both 10 and 8 with the same results) - Linux and MacOs works out of the box.

It seems that windows only sees the first device in the descriptor (AUDIO), install the standard drivers, and then fails to identify the CDC_VCOM device as the PID of the parent is detected as a generic "USB\VID_203A&PID_FFFE\PW3.0" without any &MI_00/&MI_01/&MI_02 identifier of composite device.
Above the events from system information when the device is connected:

Device USB\VID_0483&PID_5741\30353338045138352800200021 had a problem starting.

Driver Name: wdma_usb.inf
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
Service: usbaudio
Lower Filters: 
Upper Filters: 
Problem: 0xA
Problem Status: 0xC0000182


Device USB\VID_0483&PID_5741\30353338045138352800200021 was configured.

Driver Name: wdma_usb.inf
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
Driver Date: 03/18/2019
Driver Version: 10.0.18362.1
Driver Provider: Microsoft
Driver Section: USBAudio
Driver Rank: 0xFF2002
Matching Device Id: USB\Class_01
Outranked Drivers: 
Device Updated: false
Parent Device: USB\VID_203A&PID_FFFE\PW3.0

Unfortunately I am clueless on how Windows handles the driver for a device... What I can see is that the event list of a correctly detected composite device (STLINK-V2 MSC+VCOM) look like this:

//______________________ STLINK VCOM + MSC [MSC]


Device USBSTOR\Disk&Ven_MBED&Prod_microcontroller&Rev_1.0\8&25cc1fd0&0&0673FF544949847067092959&0 was started.

Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Service: disk
Lower Filters: 
Upper Filters: 


Device USBSTOR\Disk&Ven_MBED&Prod_microcontroller&Rev_1.0\8&25cc1fd0&0&0673FF544949847067092959&0 was configured.

Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.18362.1
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0006
Matching Device Id: GenDisk
Outranked Drivers: disk.inf:GenDisk:00FF2002
Device Updated: false
Parent Device: USB\VID_0483&PID_374B&MI_01\7&855d780&0&0001

//______________________ STLINK VCOM + MSC [VCOM]


Device USB\VID_0483&PID_374B&MI_02\7&855d780&0&0002 requires further installation.

Driver Management concluded the process to install driver stlink_vcp.inf_amd64_29e9917f088afd48 for Device Instance ID USB\VID_0483&PID_374B&MI_02\7&855D780&0&0002 with the following status: 0x0.

Driver Management has concluded the process to add Service usbser for Device Instance ID USB\VID_0483&PID_374B&MI_02\7&855D780&0&0002 with the following status: 0.

I hope somebody can help,
thank you,
Davide

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,242 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Raggio 6 Reputation points
    2021-09-13T16:16:05.27+00:00

    Many thanks for the reply @Limitless Technology .

    Unfortunately I've already an up to date 1903 version of Windows 10, I don't know how to check if the update KB4022716 is correctly installed, but it should be.

    For further information, when I start my device in AUDIO only mode, it gets correctly identified by Windows and the event log shows: 

    Device USB\VID_0483&PID_5731\30353338045138352800200021 was started.  
   
Driver Name: wdma_usb.inf  
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}  
Service: usbaudio  
Lower Filters:   
Upper Filters:   
   
Device USB\VID_0483&PID_5731\30353338045138352800200021 was configured.  
   
Driver Name: wdma_usb.inf  
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}  
Driver Date: 03/18/2019  
Driver Version: 10.0.18362.1  
Driver Provider: Microsoft  
Driver Section: USBAudio  
Driver Rank: 0xFF2002  
Matching Device Id: USB\Class_01  
Outranked Drivers:   
Device Updated: false  
Parent Device: USB\VID_203A&PID_FFFE\PW3.0

    The issues shows only when I add the CDC interface, creating the composite usb device AUDIO + CDC. It's strange, Linux and MacOs works out of the box.

    I've tried also a solution I've found from another developer (for a HID + CDC device). He suggested to mod the VCOM driver from STM (https://www.st.com/en/development-tools/stsw-stm32102.html) to add the &MI_xx child device of the composite and also install a dsinst_***.exe afterwards, but again no luck and same not working result.
    Here is the link of it's repository: https://gitlab.com/piotrva/stm32-composite-hid-cdc

    Anyway, starting from Windows 8 the VCOM driver from STM is no longer needed as Windows 10 is able to use a generic driver for that VCOM interface.

    That's harder than I expected it to be... do you have any other idea?

    1 person found this answer helpful.
  2. Limitless Technology 39,391 Reputation points
    2021-09-13T14:09:35.623+00:00

    Hello Raggio,

    This issue occurs because the USB audio 2.0 driver (usbaudio2.sys) isn't classified as a generic driver in Windows 10 Version 1703. Therefore, the system assumes that a compatible, nongeneric driver is installed for the device even though the driver is generic.

    This issue also causes Windows 10 Version 1703 to postpone the search for other compatible drivers through Windows Update that typically occurs immediately after you install a new device.

    There are four different methods to resolve this issue, use the below link to execute the steps.

    https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-10-not-install-specific-drivers-usb-audio-devices

    Hope this answers all your queries, if not please do repost back.
    If an Answer is helpful, please click "Accept Answer" and upvote it : )

    0 comments