Any USB device requires drivers to operate. In some cases (keyboards, mice) these are included with Windows, but in most cases they are provided by the device manufacturer (SCS, in the case of the USB-connected Pactor modems).
This note applies to the SCS USB-connected modems: the PTC-IIusb, DR-7800 Dragon, and the PTC-IIIusb, and “PTC-IIusb” here will refer to any of these modems. Serial-connected modems (PTC-II, PTC-IIe or IIex, PTC-IIpro) may be connected with a USB/serial adaptor, those also require drivers and much of this note will apply– except that the driver-files must come from the manufacturer of the USB/serial adaptor, and not with Airmail nor from SCS.
For the SCS PTC-IIusb and other USB modems, the drivers are provided on a CD-Rom that was provided with the modem, or can be downloaded from the SCS website, and are also installed with Airmail. Once installed properly, the drivers will create a virtual “COM port” to access the modem.
The 3 mobile broadband usb modem is in fact a huawei external usb modem of exactly the same type as the vodafone mobile connect 3g hsdpa usb modem. Also, you can go back to the list of drivers and choose a different driver for huawei e220 3g hsdpa usb modem. I found and installed cdma usb modem driver. I am running windows xp sp3 and now my computer sees the LG VX5600 as a modem. This still does not help me with taking pictures off my phone. I don't see any settings in the phone to change to usb mass storage device. I have read countless forums and websites, but still do not see a fix to my problem. SAMSUNGUSBDriverforMobilePhones.exe The USB Driver for Windows is available for download on this page. You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB. The ICUSB232FTN FTDI USB to Null Modem Serial Adapter Cable (1-Port) converts an available USB 1.1 or 2.0 port into an RS232 Null Modem serial DB9 port, solving DCE/DTE conflicts directly, without requiring additional cross-wired serial cables or adapters.
There are some potential wrinkles: Drivers on a CD that came with a modem that was purchased years ago will not be compatible with newer versions of Windows. Similarly, an older version of Airmail may not have installed the newer drivers needed for Win-7, and in particular Win-7 64-bit version. Also, if the modem was plugged in before the drivers were made available then Windows may have “given up” trying to install it, even after the drivers are available.
This note will outline how to check for USB driver issues and how to fix them. You need to be logged into the computer as an “administrator”, usually the primary (first) login if there is more than one. For Win-7 you can check (and change) your user-status in Control Panel, “User Accounts” (select “small-icon” view in the upper-right part of the Control Panel window).
Drivers Usb Serial Modem Router
If the drivers are installed correctly then Airmail’s “Setup Wizard” (Tools menu) will automatically find the PTC-IIusb modem, and show the correct COM-port on the “HF-Modem” page.
If it doesn’t, then cancel that window and proceed with some checks:
Device Manager:
Drivers Usb Serial Modem Setup
First, open Windows “Device Manager”. Start by opening Windows Control Panel, select small-icon view (upper-right) if needed, then find “Device Manager” and click on that. This opens the Device Manager window, which shows all connected hardware devices.
Start by looking for yellow “?” or “!” icons (symbols), those are “unknown devices” and indicate that something is not working– perhaps the modem, maybe something else. A modem with no drivers may be listed as “USB serial port” with a yellow icon, that is the same thing as “unknown device”. Leave the Device-Manager window open and disconnect the modem’s USB cable from the computer. Does the yellow icon disappear? If so then the “unknown device” is your modem, continue below.
If there are no yellow icons, then find “Ports” and expand that by clicking the little arrow. The “SCS PTC-IIusb” should be listed there, along with the assigned COM-number. Note that COM-port number, then compare to Airmail’s settings (Tools menu, Options window, connection tab) and correct that setting if needed. The baud rate for a PTC-IIusb modem is always 115200.
If you do find an “unknown device” (yellow icon) and you have confirmed that it is the modem (by disconnecting and reconnecting the USB cable), then we need to sort out drivers as follows.
Installing Drivers:
The Airmail install program also installs the SCS drivers, but older Airmail versions will not have the correct drivers for newer versions of Windows. Specifically, Airmail ver 3.4.062 has drivers for all Windows versions including Win-7/x64 (64-bit), while Airmail ver 3.4.034 is only good through Win-7/x86 (not 64-bit).
So if you have an older version of Airmail, then download the latest Airmail version (3.4.062) and install that, making sure that the “Install PTC-IIusb drivers” box is checked on the last page. Do this with the modem unplugged from the computer. Then power on the modem and plug in the USB cable, Windows should automatically find the drivers and install them. Restart Airmail and run Airmail’s setup wizard.
If you have deleted driver software (below), then you can always re-run the Airmail installer program. If you don’t change any settings, then the installer will not change your Airmail setup. When you get to the last page, check the box that says “Install PTC-IIusb drivers” and click “Finish”. Do this with the modem unplugged, then reconnect the modem and power it on.
If Windows can’t find drivers, or Airmail still can’t find the modem, then be sure the modem is connected and powered on, go back to Windows Device Manager and find the unknown device, right-click on that icon (i.e. click with the right mouse-button, not the left), and select “Update Driver Software”. Select “Search Automatically”, and wait while it searches for drivers. If Windows reports success then proceed as above with Airmail’s setup wizard.
Downloading drivers:
If still no luck then download the drivers from the SCS website. Go to www.scs-ptc.com and click on “Download” at the top, then scroll down that page and click on the link for USB drivers:
“USB driver for SCS PTC-IIusb …”. On the next page click on the driver file which will be “SCS USB Driver 2.08.02 WHQL Certified.zip” or similar, and save that file to a “downloads” folder.
Now open your “downloads” folder (whatever it is called), and open the file that you just downloaded. It will be a compressed “zip” folder, containing another folder called “SCS USB Driver 2.08.02 WHQL Certified” or similar. Copy that folder to a “Drivers” folder on the local hard drive (C-Drive) where it can be easily found– create a new “Drivers” folder if it is not already there. So under “Local Disk” you have a “Drivers” folder, and under that the “SCS USB Driver…” folder.
Installing drivers manually:
Once drivers are downloaded and saved in a “Drivers” folder, go back to Device Manager and find the “unknown device” again, and again right-click and select “Update Driver Software”. This time select “Browse my computer”. Click the “Browse” button and select the “SCS USB Driver…” folder that you downloaded and and copied to the “Drivers” folder. Click “Next” and wait while Windows installs the drivers.
Windows may come back and report success, in which case you should be done– go back to Airmail’s setup wizard, above, and see if Airmail finds the modem. If Windows says that the drivers could not be installed then unplug the USB cable, wait a few seconds, and reconnect. Check Device Manager– the modem should be listed as “SCS PTC-IIusb” under “Ports”. Continue as above.
Deleting old drivers:
If still no luck, and you have either downloaded the drivers from the SCS website, or you have the current Airmail install program, then the next step is to delete any current PTC-IIusb drivers and start over. Go back to Windows Device Manager, find the PTC-IIusb or “unknown device” icon, right-click on that and select “Uninstall”, and check the box that says “Delete driver software” (if visible). Click OK, Windows will uninstall the device and delete the current drivers.
It should re-appear as an unknown device, if not then select “Scan for hardware changes” (Action menu) or disconnect and reconnect the USB cable. It should now be an “unknown device” (yellow icon). If you don’t see it then check under “Ports” for a “SCS PTC-IIusb modem”, it might be re-installed but with older drivers– repeat the “Uninstall” (and delete driver-software) as many times as needed until it appears as an “unknown device” or (“USB Serial port” with a yellow icon). Then proceed with “Installing drivers”, above.
If there is still no luck then something is likely broken. Try a different USB connector on the computer, try your modem on a different computer, or try a different modem on your computer– the USB interface may be faulty.
(revised 2012-05-05)
-->Important
This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems
This topic lists the Microsoft-provided drivers for the supported USB device classes.
- Microsoft-provided drivers for USB-IF approved device classes.
- For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
- For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).
If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.
If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.
USB Device classes
USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.
Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.
For general information about USB-IF approved device classes see the USB Common Class Specification
The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.
Device setup classes
Windows categorizes devices by device setup classes, which indicate the functionality of the device.
Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.
Two important device setup classes for USB devices are as follows:
USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.
USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.
The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.
Microsoft-provided USB device class drivers
| USB-IF class code | Device setup class | Microsoft-provided driver and INF | Windows support | Description |
|---|---|---|---|---|
| Audio (01h) | Media {4d36e96c-e325-11ce-bfc1-08002be10318} | Usbaudio.sys Wdma_usb.inf | Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides support for the USB audio device class by means of the Usbaudio.sys driver. For more information, see 'USBAudio Class System Driver' in Kernel-Mode WDM Audio Components. For more information about Windows audio support, see the Audio Device Technologies for Windows website. |
| Communications and CDC Control (02h) | ||||
| Ports {4D36E978-E325-11CE-BFC1-08002BE10318} | Usbser.sys Usbser.inf | Windows 10 for desktop editions Windows 10 Mobile | In Windows 10, a new INF, Usbser.inf, has been added that loads Usbser.sys automatically as the function driver. For more information, see USB serial driver (Usbser.sys) | |
| Modem {4D36E96D-E325-11CE-BFC1-08002BE10318} Note Supports Subclass 02h (ACM) | Usbser.sys Custom INF that references mdmcpq.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | In Windows 8.1 and earlier versions, Usbser.sys is not automatically loaded. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) and includes [Install] and [Needs] sections. Starting with Windows Vista, you can enable CDC and Wireless Mobile CDC (WMCDC) support by setting a registry value, as described in Support for the Wireless Mobile Communication Device Class. When CDC support is enabled, the USB Common Class Generic Parent Driver enumerates interface collections that correspond to CDC and WMCDC Control Models, and assigns physical device objects (PDO) to these collections. | |
| Net {4d36e972-e325-11ce-bfc1-08002be10318} Note Supports Subclass 0Eh (MBIM) | wmbclass.sys Netwmbclass.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 | Starting in Windows 8, Microsoft provides the wmbclass.sys driver, for mobile broadband devices. See, MB Interface Model. | |
| HID (Human Interface Device) (03h) | HIDClass {745a17a0-74d3-11d0-b6fe-00a0c90f57da} | Hidclass.sys Hidusb.sys Input.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the HID class driver (Hidclass.sys) and the miniclass driver (Hidusb.sys) to operate devices that comply with the USB HID Standard. For more information, see HID Architecture and Minidrivers and the HID class driver. For further information about Windows support for input hardware, see the Input and HID - Architecture and Driver Support website. |
| Physical (05h) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
| Image (06h) | Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} | Usbscan.sys Sti.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbscan.sys driver that manages USB digital cameras and scanners for Windows XP and later operating systems. This driver implements the USB component of the Windows Imaging Architecture (WIA). For more information about WIA, see Windows Image Acquisition Drivers and the Windows Imaging Component website. For a description of the role that Usbscan.sys plays in the WIA, see WIA Core Components. |
| Printer (07h) | USB Note Usbprint.sys enumerates printer devices under the device set up class: Printer {4d36e979-e325-11ce-bfc1-08002be10318}. | Usbprint.sys Usbprint.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbprint.sys class driver that manages USB printers. For information about implementation of the printer class in Windows, see the Printing - Architecture and Driver Support website. |
| Mass Storage (08h) | ||||
| USB | Usbstor.sys | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbstor.sys port driver to manage USB mass storage devices with Microsoft's native storage class drivers. For an example device stack that is managed by this driver, see Device Object Example for a USB Mass Storage Device. For information about Windows storage support, see the Storage Technologies website. | |
| SCSIAdapter {4d36e97b-e325-11ce-bfc1-08002be10318} | SubClass (06) and Protocol (62) Uaspstor.sys Uaspstor.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 | Uaspstor.sys is the class driver for SuperSpeed USB devices that support bulk stream endpoints. For more information see: | |
| Hub (09h) | USB {36fc9e60-c465-11cf-8056-444553540000} | |||
| Usbhub.sys Usb.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbhub.sys driver for managing USB hubs. For more information about the relationship between the hub class driver and the USB stack, see USB host-side drivers in Windows. | ||
| Usbhub3.sys Usbhub3.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 | Microsoft provides the Usbhub3.sys driver for managing SuperSpeed (USB 3.0) USB hubs. The driver is loaded when a SuperSpeed hub is attached to an xHCI controller. See USB host-side drivers in Windows. | ||
| CDC-Data (0Ah) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
| Smart Card (0Bh) | SmartCardReader {50dd5230-ba8a-11d1-bf5d-0000f805f530} | |||
| Usbccid.sys (Obsolete) | Windows 10 for desktop editions Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbccid.sys mini-class driver to manage USB smart card readers. For more information about smart card drivers in Windows, see Smart Card Design Guide. Note that for Windows Server 2003, Windows XP, and Windows 2000, special instructions are required for loading this driver because it might have been released later than the operating system. Note Usbccid.sys driver has been replaced by UMDF driver, WUDFUsbccidDriver.dll. | ||
| WUDFUsbccidDriver.dll WUDFUsbccidDriver.inf | Windows 8.1 Windows 8 | WUDFUsbccidDriver.dll is a user-mode driver for USB CCID Smart Card Reader devices. | ||
| Content Security (0Dh) | - | - | - | Recommended driver: USB Generic Parent Driver (Usbccgp.sys). Some content security functionality is implemented in Usbccgp.sys. See Content Security Features in Usbccgp.sys. |
| Video (0Eh) | Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} | Usbvideo.sys Usbvideo.inf | Windows 10 for desktop editions Windows Vista | Microsoft provides USB video class support by means of the Usbvideo.sys driver. For more information, see 'USB Video Class Driver' under AVStream Minidrivers. Note that for Windows XP, special instructions are required for loading this driver because it might have been released later than the operating system. |
| Personal Healthcare (0Fh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
| Audio/Video Devices (10h) | - | - | - | - |
| Diagnostic Device (DCh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
| Wireless Controller (E0h) Note Supports Subclass 01h and Protocol 01h | Bluetooth {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} | Bthusb.sys Bth.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Vista | Microsoft provides the Bthusb.sys miniport driver to manage USB Bluetooth radios. For more information, see Bluetooth Design Guide. |
| Miscellaneous (EFh) | Net {4d36e972-e325-11ce-bfc1-08002be10318} Note Supports SubClass 04h and Protocol 01h | Rndismp.sys Rndismp.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Vista | Prior to Windows Vista, support for CDC is limited to the RNDIS-specific implementation of the Abstract Control Model (ACM) with a vendor-unique protocol (bInterfaceProtocol) value of 0xFF. The RNDIS facility centers the management of all 802-style network cards in a single class driver, Rndismp.sys. For a detailed discussion of remote NDIS, see Overview of Remote NDIS. The mapping of remote NDIS to USB is implemented in the Usb8023.sys driver. For further information about networking support in Windows, see the Networking and Wireless Technologies website. |
| Application Specific (FEh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
| Vendor Specific (FFh) | - | - | Windows 10 for desktop editions Windows 10 Mobile | Recommended driver: WinUSB (Winusb.sys) |
Related topics