Download Step-four Port Devices Driver

Download Step-four Port Devices Driver Windows 10
Download Step-four Port Devices Driver Free
Download Step-four Port Devices Driver Download

In this document

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices. For D2XX Direct drivers, please click here. Driver Downloads. Find available Marvell drivers by Platform or Part Number. Driver Downloads. Marvell Drivers.

Installing a USB Driver

Installing a USB Driver

First, find the appropriate driver for your device from the OEM driverstable below.

Once you've downloaded your USB driver, follow the instructions below to install or upgrade thedriver, based on your version of Windows and whether you're installing for the first timeor upgrading an existing driver.

Tip: When you finish the USB driver installation,see Using Hardware Devices forother important information about using an Android-powered device fordevelopment.

Caution:You may make changes to android_winusb.inf file found insideusb_driver (for example, to add support for other devices),however, this will lead to security warnings when you install or upgrade thedriver. Making any other changes to the driver files may break the installationprocess.

Windows 7

To install the Android USB driver on Windows 7 for the first time:

Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.)
Click Next to install the driver.

Or, to upgrade an existing Android USB driver on Windows 7 with the newdriver:

Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-checkSearch removable media; and check Include this location in thesearch.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.)
Click Next to upgrade the driver.

Windows XP

To install the Android USB driver on Windows XP for the first time:

Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-checkSearch removable media; and check Includethis location in the search.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.)
Click Next to install the driver.

Or, to upgrade an existing Android USB driver on Windows XP with the newdriver:

Connect your Android-powered device to your computer's USB port.
Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Includethis location in the search.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.)
Click Next to upgrade the driver.

Windows Vista

To install the Android USB driver on Windows Vista for the first time:

Download Step-four Port Devices Driver Windows 10

Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
Select Locate and install driver software.
Select Don't search online.
Select I don't have the disk. Show me other options.
Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.) As long as you specified theexact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to install the driver.

Or, to upgrade an existing Android USB driver on Windows Vista with the newdriver:

Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane.
Locate and expand ADB Interface in the right pane.
Right-click on HTC Dream Composite ADB Interface, and select Update Driver Software.
When Vista starts updating the driver, a prompt will ask how you want to search for the driver software. Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USBDriver is located in <sdk>extrasgoogleusb_driver.) As long as you specified theexact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista might prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to upgrade the driver.

OEM Drivers

Note: If your device is one of the Android Developer Phones(purchased from the Google Play publisher site), a Nexus One, or a Nexus S, then you needthe Google USB Driver, instead of an OEM driver. The GalaxyNexus driver, however, is distributed by Samsung(listed as model SCH-I515).

OEM	Driver URL
Acer	http://www.acer.com/worldwide/support/mobile.html
alcatel one touch	http://www.alcatel-mobilephones.com/global/Android-Downloads
Asus	http://support.asus.com/download/
Dell	http://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml
Foxconn	http://drivers.cmcs.com.tw/
Fujitsu	http://www.fmworld.net/product/phone/sp/android/develop/
Fujitsu Toshiba	http://www.fmworld.net/product/phone/sp/android/develop/
Garmin-Asus	https://www.garminasus.com/en_US/support/pcsync/
Hisense	http://app.hismarttv.com/dss/resourcecontent.do?method=viewResourceDetail&resourceId=16&type=5
HTC	http://www.htc.com Click on thesupport tab to select your products/device. Different regions will have different links.
Huawei	http://www.huaweidevice.com/worldwide/downloadCenter.do?method=index
Intel	http://www.intel.com/software/android
KT Tech	http://www.kttech.co.kr/cscenter/download05.asp for EV-S100 (Take)
Kyocera	http://www.kyocera-wireless.com/support/phone_drivers.htm
Lenovo	http://developer.lenovomm.com/developer/download.jsp
LGE	http://www.lg.com/us/mobile-phones/mobile-support/mobile-lg-mobile-phone-support.jsp
Motorola	http://developer.motorola.com/docstools/USB_Drivers/
Pantech	http://www.isky.co.kr/cs/software/software.sky?fromUrl=index
Pegatron	http://www.pegatroncorp.com/download/New_Duke_PC_Driver_0705.zip (ZIP download)
Samsung	http://www.samsung.com/us/support/downloads
Sharp	http://k-tai.sharp.co.jp/support/
SK Telesys	http://www.sk-w.com/service/wDownload/wDownload.jsp
Sony Mobile Communications	http://developer.sonymobile.com/downloads/drivers/
Teleepoch	http://www.teleepoch.com/android.html
Yulong Coolpad	http://www.yulong.com/product/product/product/downloadList.html#downListUL
ZTE	http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442

-->

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.

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.

Download Step-four Port Devices Driver Free

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:

Blogpress588