I've tried also a solution I've found from another developer (for a HID + CDC device). It's strange, Linux and MacOs works out of the box. The issues shows only when I add the CDC interface, creating the composite usb device AUDIO + CDC. Parent Device: USB\VID_203A&PID_FFFE\PW3.0 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.Ībove the events from system information when the device is connected: Device USB\VID_0483&PID_5741\30353338045138352800200021 had a problem starting.Ĭlass Guid: 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.
