usb communication device work on win7 not win10 or win11,com port not created.

Question

usb communication device work on win7 not win10 or win11,com port not created.

Ray Stambaugh 0

Windows 7 connects to a USB device without error.

Device manager shows a working usb to serial com port.

Apps can communicate with the device through the com port.

Windows 10/11 does not connect to the USB device.

Device manager show a com port with errors.

CMD Mode displays no com ports.

USB device viewer reports 0 pipes open.

I have spent a week scouring the internet for a solution. None found.

Action taken:

Uninstall the driver.

Restarted the computer.

Installed the driver.

Connected the device, The error persists.

Searched for a tool that display what pnp was doing and why it failed.

None found.

Found and installed inf2cat.exe.

inf2cat.exe mchpcdc.inf 10_X64

No change.

Files:

=======================================================================

mchpcdc.inf - microchip cdc driver files.

; Windows USB CDC ACM Setup File

[Version]

Signature="$Windows NT$"

Class=Ports

ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}

Provider=%MFGNAME%

LayoutFile=layout.inf

CatalogFile=%MFGFILENAME%.cat

DriverVer=11/15/2007,5.1.2600.0

[Manufacturer]

%MFGNAME%=DeviceList, NTamd64

[DestinationDirs]

DefaultDestDir=12

;------------------------------------------------------------------------------

; Windows 2000/XP/Vista-32bit Sections

;------------------------------------------------------------------------------

[DriverInstall.nt]

include=mdmcpq.inf

CopyFiles=DriverCopyFiles.nt

AddReg=DriverInstall.nt.AddReg

[DriverCopyFiles.nt]

usbser.sys,,,0x20

[DriverInstall.nt.AddReg]

HKR,,DevLoader,,*ntkern

HKR,,NTMPDriver,,%DRIVERFILENAME%.sys

HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.nt.Services]

AddService=usbser, 0x00000002, DriverService.nt

[DriverService.nt]

DisplayName=%SERVICE%

ServiceType=1

StartType=3

ErrorControl=1

ServiceBinary=%12%%DRIVERFILENAME%.sys

;------------------------------------------------------------------------------

; Vista-64bit Sections

;------------------------------------------------------------------------------

[DriverInstall.NTamd64]

include=mdmcpq.inf

CopyFiles=DriverCopyFiles.NTamd64

AddReg=DriverInstall.NTamd64.AddReg

[DriverCopyFiles.NTamd64]

%DRIVERFILENAME%.sys,,,0x20

[DriverInstall.NTamd64.AddReg]

HKR,,DevLoader,,*ntkern

HKR,,NTMPDriver,,%DRIVERFILENAME%.sys

HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NTamd64.Services]

AddService=usbser, 0x00000002, DriverService.NTamd64

[DriverService.NTamd64]

DisplayName=%SERVICE%

ServiceType=1

StartType=3

ErrorControl=1

ServiceBinary=%12%%DRIVERFILENAME%.sys

;------------------------------------------------------------------------------

; Vendor and Product ID Definitions

;------------------------------------------------------------------------------

; When developing your USB device, the VID and PID used in the PC side

; application program and the firmware on the microcontroller must match.

; Modify the below line to use your VID and PID. Use the format as shown below.

; Note: One INF file can be used for multiple devices with different VID and PIDs.

; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.

;------------------------------------------------------------------------------

[SourceDisksFiles]

[SourceDisksNames]

[DeviceList]

%DESCRIPTION%=DriverInstall, USB\VID_04D8&PID_000A

[DeviceList.NTamd64]

%DESCRIPTION%=DriverInstall, USB\VID_04D8&PID_000A

;------------------------------------------------------------------------------

; String Definitions

;------------------------------------------------------------------------------

;Modify these strings to customize your device

;------------------------------------------------------------------------------

[Strings]

MFGFILENAME="mchpcdc"

DRIVERFILENAME ="usbser"

MFGNAME="Microchip Technology, Inc."

INSTDISK="Microchip Technology, Inc. Installation Disc"

DESCRIPTION="Communications Port"

SERVICE="USB RS-232 Emulation Driver"

=======================================================================

DeviceManager.txt - General tab.

Device status

This device cannot start. (Code 10)

{Operation Failed}

The requested operation was unsuccessful.

=======================================================================

USB device viewer.txt - USB data.

[Port2] : Communications Port

Is Port User Connectable: yes

Is Port Debug Capable: no

Companion Port Number: 6

Companion Hub Symbolic Link Name: USB#ROOT_HUB30#4&260e01b0&3&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}

Protocols Supported:

USB 1.1: yes

USB 2.0: yes

USB 3.0: no

   ---===>Device Information<===---

String Descriptor for index 2 not available while device is in low power state.

ConnectionStatus:

Current Config Value: 0x00 -> Device Bus Speed: Full (is not SuperSpeed or higher capable)

Device Address: 0x03

Open Pipes: 0

*!*ERROR: No open pipes!

      ===>Device Descriptor<===

bLength: 0x12

bDescriptorType: 0x01

bcdUSB: 0x0200

bDeviceClass: 0x02 -> This is a Communication Device

bDeviceSubClass: 0x00

bDeviceProtocol: 0x00

bMaxPacketSize0: 0x08 = (8) Bytes

idVendor: 0x04D8 = Microchip Technology Inc.

idProduct: 0x000A

bcdDevice: 0x0001

iManufacturer: 0x01

String Descriptor for index 1 not available while device is in low power state.

iProduct: 0x02

String Descriptor for index 2 not available while device is in low power state.

iSerialNumber: 0x00

bNumConfigurations: 0x01

   ---===>Full Configuration Descriptor<===---

      ===>Configuration Descriptor<===

bLength: 0x09

bDescriptorType: 0x02

wTotalLength: 0x0043 -> Validated

bNumInterfaces: 0x02

bConfigurationValue: 0x01

iConfiguration: 0x00

bmAttributes: 0xC0 -> Self Powered

MaxPower: 0x32 = 100 mA

      ===>Interface Descriptor<===

bLength: 0x09

bDescriptorType: 0x04

bInterfaceNumber: 0x00

bAlternateSetting: 0x00

bNumEndpoints: 0x01

bInterfaceClass: 0x02 -> This is Communications (CDC Control) USB Device Interface Class

bInterfaceSubClass: 0x02

bInterfaceProtocol: 0x01

iInterface: 0x00

-> This is a Communications (CDC Control) USB Device Interface Class

      ===>Descriptor Hex Dump<===

bLength: 0x05

bDescriptorType: 0x24

05 24 00 10 01

-> This is a Communications (CDC Control) USB Device Interface Class

      ===>Descriptor Hex Dump<===

bLength: 0x04

bDescriptorType: 0x24

04 24 02 02

-> This is a Communications (CDC Control) USB Device Interface Class

      ===>Descriptor Hex Dump<===

bLength: 0x05

bDescriptorType: 0x24

05 24 06 00 01

-> This is a Communications (CDC Control) USB Device Interface Class

      ===>Descriptor Hex Dump<===

bLength: 0x05

bDescriptorType: 0x24

05 24 01 00 01

      ===>Endpoint Descriptor<===

bLength: 0x07

bDescriptorType: 0x05

bEndpointAddress: 0x82 -> Direction: IN - EndpointID: 2

bmAttributes: 0x03 -> Interrupt Transfer Type

wMaxPacketSize: 0x0008 = 0x08 bytes

bInterval: 0x02

      ===>Interface Descriptor<===

bLength: 0x09

bDescriptorType: 0x04

bInterfaceNumber: 0x01

bAlternateSetting: 0x00

bNumEndpoints: 0x02

bInterfaceClass: 0x0A -> This is a CDC Data USB Device Interface Class

bInterfaceSubClass: 0x00

bInterfaceProtocol: 0x00

iInterface: 0x00

      ===>Endpoint Descriptor<===

bLength: 0x07

bDescriptorType: 0x05

bEndpointAddress: 0x03 -> Direction: OUT - EndpointID: 3

bmAttributes: 0x02 -> Bulk Transfer Type

wMaxPacketSize: 0x0040 = 0x40 bytes

bInterval: 0x00

      ===>Endpoint Descriptor<===

bLength: 0x07

bDescriptorType: 0x05

bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3

bmAttributes: 0x02 -> Bulk Transfer Type

wMaxPacketSize: 0x0040 = 0x40 bytes

bInterval: 0x00

=======================================================================

EckiS 916 Reputation points

2024-11-18T15:09:06.92+00:00

according to https://devicehunt.com/view/type/usb/vendor/04D8
USB\VID_04D8&PID_000A seems to be "Microchip Technology, Inc." - "CDC RS-232 Emulation Demo"
are you sure this is the correct driver for your device?
the "Emulation Demo" in the name sounds suspiciously as if this is not intended for real hardware.

"This device cannot start. (Code 10)"
Did you contact Microchip for updated Windows 10 / 11 drivers?
Ray Stambaugh 0 Reputation points

2024-11-20T15:31:07.8033333+00:00

This device uses windows supplied drivers only.

A device specific driver is not required.

1 answer

Your answer

EckiS 916 Reputation points

2024-11-18T15:09:06.92+00:00

according to https://devicehunt.com/view/type/usb/vendor/04D8
USB\VID_04D8&PID_000A seems to be "Microchip Technology, Inc." - "CDC RS-232 Emulation Demo"
are you sure this is the correct driver for your device?
the "Emulation Demo" in the name sounds suspiciously as if this is not intended for real hardware.

"This device cannot start. (Code 10)"
Did you contact Microchip for updated Windows 10 / 11 drivers?
Ray Stambaugh 0 Reputation points

2024-11-20T15:31:07.8033333+00:00

This device uses windows supplied drivers only.

A device specific driver is not required.

Answer 1

Hello,

1、Check Device Manager to see if the device is recognized but perhaps has a warning icon indicating a driver or resource issue.

Right-click the Start button and select ‘Device Manager’.

Look for your device. It might be in ‘Other devices’ or ‘Ports (COM & LPT)’ if it’s recognized as a serial device.

If there’s a warning icon, right-click the device and select ‘Update driver’. Choose to search automatically for updated driver software or browse your computer for driver software if you’ve downloaded the latest version from the manufacturer’s website.

2、Sometimes, the USB controller drivers can be the issue. Try updating the USB controller drivers from Device Manager.

In Device Manager, expand ‘Universal Serial Bus controllers’.

Right-click each USB controller and select ‘Update driver’.

3、If the device expects to create a virtual COM port, ensure that any associated virtual COM port drivers are installed. For example, devices using FTDI chips require specific VCP drivers.

Best Regards,

Hania Lian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Ray Stambaugh 0 Reputation points

2024-11-25T22:23:06.64+00:00

This device uses windows supplied drivers only.

A device specific driver is not required.

Device manager has the device listed under Ports (COM & LPT) as;

USB Serial Port (COM6)

The DOS mode command does not list COM6.

COM6 is not listed with any Serial Application.

Share via

usb communication device work on win7 not win10 or win11,com port not created.

1 answer

Your answer