To reinstall driver you have to: 1. Open Device Manager (Press WINDOWS + X click 'Device Manager') 2. Right click on your Computer name 3. When you plug the device into your USB, Windows will look for the associated driver, if it cannot find this driver then you will be prompted to insert the driver disc that came with your device. Common USB Device errors are ‘ usb port not working ‘, ‘device descriptor request failed error’ or ‘bugcodeusbdriver’ issues. Download Drivers, download Input Devices, download Boeder, wide range of software, drivers and games to download for free. The IOCTLHIDREADREPORT request transfers an input report from a HIDClass device into the HID class driver's buffer. IOCTLHIDSENDIDLENOTIFICATIONREQUEST The IOCTLHIDSENDIDLENOTIFICATIONREQUEST control code is the IOCTL of the idle notification request IRP that HIDClass sends to HID mini drivers, such as HIDUSB, to inform the bus.
-->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
ADB (Android Debug Bridge) and Fastboot (a protocol between phone and computer is a nifty command-line tool used to interact with your Android device from a computer. In this guide, we’ll show you how you can download and setup ADB on Windows 10 computer, using ADB and Fastboot, Installing Google USB driver along with resources and a step-by-step guide.
What are ADB and Fastboot?
ADB and Fastboot are the tools used to send terminal commands to your Android phone via a computer while connected through a USB cable. Although, both serve different functions but can be installed at the same time. Below is a quick breakdown of what these tools are and what do they do.
- Android Debug Bridge (ADB): This tool allows you to send a wide array of terminal commands — including but not limited to basic Linux shell commands, plus some specialty developer commands — to your phone at just about any time (as long as you have debugging enabled on your phone). You can send commands while the phone is turned on and booted, or even when it’s in recovery mode. While ADB is often used in conjunction with rooting or modifying your phone, you can use ADB to send terminal commands to unrooted devices as well. ~ Lifehacker
For example, you can copy files from your computer to Android storage by using “ADB push ironman3.Mkv /sd card/Movies/” command.
- Fastboot:a protocol between phone and computer. When you need to modify your phone’s firmware, Fastboot is the tool you need. This allows you to send commands to the bootloader, which means you can flash/modify things like custom recoveries. You can’t flash whole ROMs with it, but it’s helpful for many things that ADB can’t do. Fastboot isn’t enabled for all phones, so you may have to check your specific device. ~ Lifehacker
You can flash a custom recovery using “fastboot flash recovery twrp.img
” (twrp.img should be located in the same folder).
Both of these tools come with the Android SDK. However, that’s an extremely large download that, frankly, most users who are interested in ADB and fastboot don’t need. Fortunately, Google recently made it easy to get these two without all the junk.
Install ADB and Fastboot tool on Windows 10
Google made a relatively small package called “Platform-tools” that includes ADB and Fastboot along with some other utilities.
Step 1. Download Google SDK Tools for Windows 10
Google named Platform Tools package that includes Fastboot, ADB and other utilities. To download the Platform-tools package visit this page, These are the separate package for Windows, Linux, and Mac.
Choose an appropriate version of Platform tool, select terms and click on the big blue button to download.
Step 2. Run
Navigate to the Platform Tools folder, Right click and choose “open command prompt” from here. If you see Powershell option instead on the command prompt, use this guide.
Input Mapper
To use ADB commands you must enable “USB Debugging” feature on your phone. Otherwise, it won’t work.
ADB commands Application
Install an Apk
You can install an apk file (stored on your computer) to your phone using this command
more at Android Studio
Pulling/pushing a file
Use “adb push filename /path” to send the file to the mobile device.
For starters, I used the “fastboot devices
” command will display all the connected devices which are in fastboot mode. For example to enter in fastboot mode in a Xiaomi device you have to turn off the phone, start it pressing Power + Vol Down simultaneously.
Step 3. Optional, Modify Adb Path
- Open “Advanced system settings.”
- Click “View Advanced system settings.”
- Click the box that says “Environment Variables.”
- Under “System Variables” click on the variable named “Path.”
- Click “Edit…” and enter ADB folder location.
Install ADB and Fastboot Drivers
Google USB drivers are required to perform ADB debugging with Android devices. Generally, when you connect the Android device to Windows 10, it will automatically download drives via Windows update. But in case it didn’t
- Click to download the Google USB Driver (8MB ZIP file)
- After download, extract the ZIP file.
- Open “Device manager”.
- Find Portable Devices.
- Right-click on your phone name and Update driver.
- Select Browse my computer for Driver Software.
- Now Navigate to the driver folder using the browse button. Select the extracted folder and click on next.
If everything goes right Google USB driver should be installed and your computer will recognize your phone just fine.
Install Android Bootloader Interface through Windows update
Starting with Windows version 20H2, Microsoft has quietly added it to Optional Updates. This means that you will have to go into the settings and install this software, which I am giving below in the steps and the steps are quite easy, you hardly need to face any problem in doing this from the office, for this you need an internet connection.
QUIckly open Windows settings and then Windows Updates (find under Update and security). Under the Check for update button you can see optional updates button right beneath it.
Now you have to click on the arrow icon. All optional updates will be shown here, select any update and download and install it. For this, you will need an internet connection. If you have a metered connection to your internet connection, then you can install such updates by coming here.
That’s it.
Manually Installing ADB and Fastboot Interface
Do this when ADB and fastboot commands are not working or your computer didn’t recognize devices when checking through ADB devices and fastboot devices command. This is a normal case with the recent version of Windows 10 and with some Oneplus devices.
prerequisite
Download Targa Input Devices Driver Windows 7
- Disable driver signature enforcement: open a PowerShell window and enter
bcdedit /set testsigning on
(and off when done). - Install Oneplus Driver, select Install this driver security prompt when asked.
- Open device manager and look for Android Phone and Android Bootloader Interface if they show up somehow.
- From “Action” select Add legacy hardware.
- Click Next.
- Choose Install the hardware that I manually select from a list (Advanced).
- Select Android Phone.
- Unless you’re connecting a device of other manufacturer such as Xiaomi device, Select Google, Inc. and choose Android Bootloader Interface. (Repeat the steps for Android ADB Interface).
- The wizard will install the software, after that the ADB and Fastboot tools should work fine with your phone. remember not all of the phones are supported Fastboot, you should check your specific device.
Download Targa Input Devices Driver Win 7
That’s all for now if you think we missed something you can always drop a comment below.
For users who find this process time tacking, despite it shouldn’t take longer than 10 minutes. But instead, if you prefer installing ADB+fastboot in seconds, use a 3rd party installer like this one.
Article Contents
- Install ADB and Fastboot tool on Windows 10
- Step 1. Download Google SDK Tools for Windows 10
- ADB commands Application