This driver is used as a serial port over a USB port. Since we are all confined ( Covid-19), I can't go to his place to help him. I got access to his PC uing AnyDesk This driver is installed on my own PC, but I can't find a way to install in on my brother Windows 10 PC. Any help appreciated Good luck to all Martin. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device. The package provides the installation files for FTDI USB Serial Port Driver version 2.12.16.0. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Right-click on your PC Start button and open Device Manager Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver For driver software click My computer From My computer select 'Let me pick from a list of drivers available'.

-->

Versions supported

• Windows 10
• Windows 8.1

Applies to

• Device manufacturers of CDC Control devices

Cdc Serial Driver Download Windows 10

Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.

• Improved PnP and power management by the driver (such as, handling surprise removal).
• Added power management features such as USB Selective Suspend.

In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.

Usbser.sys installation

Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

Note

If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.

Windows 10

In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.

USBClass_02

USBClass_02&SubClass_02

• If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
• If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
• If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.

Note

Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.

Windows 8.1 and earlier versions

In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.

The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.

For more information, see this KB article.

Configure selective suspend for Usbser.sys

Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:

To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:

• '0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.

• '0x00000000': Enters selective suspend only when there are no open handles to the device.

That entry can be added in one of two ways:

• Write an INF that references the install INF and add the registry entry in the HW.AddReg section.

• Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.

  For more information, see Microsoft OS Descriptors.

Develop Windows applications for a USB CDC device

If you install Usbser.sys for the USB CDC device, here are the application programming model options:

• Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.

• In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:

  Win32 programming model:

  • .NET framework programming model:

Related topics

The CH340 chip is used by a number of Arduino compatible boards to provide USB connectivity, you may need to install a driver, don’t panic, it’s easier than falling off a log, and much less painful.

Windows

(Manufacturer’s Chinese Info Link)

1. Download the Windows CH340 Driver
2. Unzip the file
3. Run the installer which you unzipped
4. In the Arduino IDE when the CH340 is connected you will see a COM Port in the Tools > Serial Port menu, the COM number for your device may vary depending on your system.
   

Older Windows Driver Version and Instructions

1. Download the Windows CH340 Driver
   
2. Unzip the folder.
   
3. If you are running a 64Bit Windows: – run the SETUP_64.EXE installer.
   
4. If you are running a 32Bit Windows: – run the SETUP_32.EXE installer.
   
5. If you don’t know, try the 64 bit and if it doesn’t work, the 32 bit.
   
6. In the Arduino IDE when the CH340 is connected you will see a COM Port in the Tools > Serial Port menu, the COM number for your device may vary depending on your system.
   

Macintosh

(Manufacturer’s Chinese Info Link)

The following github has up to day pkg files for 1.3, 1.4 and 1.5 at time of writing, thanks to Joshua Wallis for bringing this to my attention…

Direct Download Links (from the github repo above):

See the github link above for installation instructions if you need them.

Previous macinstosh downloads if the above doesn’t work for you…

(V1.3) Download the CH340 Macintosh Signed Driver for Mavericks (10.9), Yosemite (10.10) and El Capitan (10.11) and Sierra (10.12)

Inside the zip file you will find a PDF and a “pkg” file, short version, double click the pkg file, the PDF has some extra information.

OSX Sierra (10.12) Note

A kindly user, Maarten Segers reports

FYI, the driver documented here WILL crash on OSX Sierra.

I can personally not test on MacOS and can not vouch for the above drivers at github, but there you go.

See uninstalling information at the bottom of the page if the driver causes problems for you.

Here is an older version of the Mac driver, NOT FOR 10.12 Sierra

(V1.0) Download the CH340 Macintosh Signed Driver for Mavericks (10.9), Yosemite (10.10) and El Capitan (10.11)

Linux

(Manufacturer’s Chinese Info Link)

Drivers are almost certainly built into your Linux kernel already and it will probably just work as soon as you plug it in. If not you can download the Linux CH340 Driver (but I’d recommend just upgrading your Linux install so that you get the “built in” one).

Usb2.0-serial Driver Download Win 10

Uninstalling From Macinstosh

A couple of Mac users have said “the driver crashes my mac Sierra how do I uninstall”.

Firstly regards the crash make sure you installed the 1.3 version of the driver, not the old one. You could download it directly from the Manufacturers Website in case they have issued an update since I wrote this page.

Secondly a quick google search reveals that this is how you uninstall:

1. Open a terminal and type: cd /Library/Extensions/
2. Verify that the .kext file is present: ls | grep usbserial.kext
3. Output should be: usbserial.kext
4. Then type: sudo rm -R usbserial.kext
5. Verify that the .kext file has been removed: ls | grep usbserial.kext
6. Output should be empty.
7. After you should remove the files stored in receipts folder: cd /private/var/db/receipts/
8. Find the enties: ls | grep usbserial*
9. Output should be: codebender.cc.ch34xinstaller.usbserial.pkg.bom codebender.cc.ch34xinstaller.usbserial.pkg.plist
10. Remove each one of the files of the above list: sudo rm -r filename`