2SE Port Devices Driver

Unextract the file into any folder. Then while your cable is connected to the computer — go Device Manager. Windows Vista/7/8/10: Control Panel » System » Device Manager; Windows XP: Control Panel » System » 'Hardware' tab » Device Manager; You'll see a device similar to 'USB Serial Port' under either 'Other devices' or 'Ports (COM & LPT)'.

• Go to Control panel, enter System to access your Device Manager Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port Click Driver in the Windows Properties section The driver must be numbered as '2.0.2.8' and dates accordingly.
• Because your platform can have both USB 2.0 and USB 3.0 controllers, it's useful to check which controller the USB device is connected to. Follow these steps: Connect a USB 3.0 flash drive (USB Mass Storage Device) to one of the Intel USB 3.0 ports. In Device Manager, click View, and click Devices by connection.

(DO NOT connect cable to your computer yet. Only do this when you're instructed below.)

Start by downloading the VAG-COM Driver Pack 1.

Here's how to install on different Windows versions...

Windows Vista, 7, 8, 8.1, 10:

Uncompress the file. Double-click on 'Install.exe' to install the drivers. When complete — plug in cable into any USB port on your computer and wait for automatic installation to complete.

If install is successful, move onto Step 2.

If installation fails, see below: Troubleshooting: If Drivers Failed To Install

Windows XP:

1. Uncompress the file. Double-click on 'Install.exe' to install the drivers.
2. Plug cable into any computer's USB port.
3. 'Found New Hardware Wizard' will start and it will ask you 'Can Windows connect to Windows Update to search for the software?'. Select 'Yes'.
4. Select 'Install the software automatically'.
5. After the installation is complete, click 'Finish'.
6. 'Found New Hardware Wizard' will start once again because there are two drivers for this cable.
7. Go through the same steps as explained above to install this second driver.

If install is successful, move onto Step 2.

If installation fails, see below: Troubleshooting: If Drivers Failed To Install

Troubleshooting: If Drivers Failed To Install:

Installation failed? Download here VAG-COM Driver Pack 2.

Unextract the file into any folder. Then while your cable is connected to the computer — go Device Manager.

• Windows Vista/7/8/10: Control Panel » System » Device Manager
• Windows XP: Control Panel » System » 'Hardware' tab » Device Manager

You'll see a device similar to 'USB Serial Port' under either 'Other devices' or 'Ports (COM & LPT)'.

Right-click and choose 'Update Driver Software'. Like this:

Then select the location where you unextracted Driver Pack 2. Let it install.

Go to Control Panel.

• Windows Vista/7/8/10: Control Panel » System » Device Manager
• Windows XP: Control Panel » System » 'Hardware' tab » Device Manager

Expand 'Other devices' or 'Ports (COM & LPT)'. Whichever contains 'USB Serial Port'.

Next to 'USB Serial Port' — you'll see a number.

If the COM port number is between 1-4, then everything is fine. Move onto Step 3.

If the COM port number is above 4, then we'll have to change it so it's between 1-4. Here's how...

Cable should be plugged into computer.

1. Start VCDS-Lite software.
2. Click 'Options' button.
3. You will see 'Select COM Port' box. Select the 'COM Port' number as explained in Step 2.
4. Click the ‘Test’ button.
5. If everything is good, it should display 'Interface Status: Found!'.
6. You can now connect other end of cable to car. Turn on ignition. And you're ready to start diagnosing!

If test is not successful — check the following:

1. Other software or devices using USB ports or that same COM Port could be conflicting. You should uninstall the suspected software or device for troubleshooting this problem.
2. It should be noted that VAG-COM 409.1 KKL cable does not work on vehicles running on CAN-BUS System.
3. Cable must be plugged into the vehicle with ignition ON.
4. Test the cable with each COM Port from 1 to 4 in Windows Device Manager.
5. Make sure that the driver is installed and configured as explained in Step 1.

• Only Audi, Volkswagen, Skoda and Seat vehicles are supported. Other brands will only work for generic OBD-II functions.
• If VAG-COM 409.1 KKL cable doesn't connect — or if you get the error message 'Can't Synch Baud Rate' — then go to Options and set Start Baud to 9600. If 9600 doesn't work, try 4800 and 1200. Turn the vehicle's ignition OFF and back ON after each failed attempt to connect.
• If you have installed VCDS software before or from another source, uninstall all versions of VCDS software right now, and delete directory 'C:Ross-Tech'. Then install latest version of VCDS-Lite software by clicking here.

For further information and instructions for troubleshooting, visit the following links:

How to Install & Register VCDS-Lite software That Came With Your VAG-COM 409.1 KKL Cable

Versions supported

• Windows 10
• Windows 8.1

Applies to

• Device manufacturers of CDC Control devices

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.

2se Port Devices Driver Download

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:

2SE Port Devices Driver

• 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

2se Port Devices Driver Update

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:

2se Port Devices Drivers

Related topics