As you can easily find, the USB has become a standard and the most popular PC expansion interface of the twenty-first century. USB devices can be seen in all walks of life; even the game console, SD card, and mouse, keyboard & other hardware components of the computer can be connected through the USB. How to Install USB Driver for Android Device on Windows Computer. USB driver is the key point to connect your Android device to Windows computer. With the development of technology, USB cable is not only the tool to charge, but also to connect your Android device to computer. And if you want to recover important data, transfer files or fix. Usb Video Device Driver free download, and many more programs.
-->This article helps to fix an issue in which Windows 10 doesn't install specific drivers for USB audio devices on the first connection.
Original product version: Windows 10, version 1703
Original KB number: 4021854
Symptom
When you connect a USB audio device to a Windows 10 Version 1703-based computer the first time, the operating system detects the device but loads the standard USB audio 2.0 driver (usbaudio2.sys) instead of the specific device driver.
Cause
This issue occurs because the USB audio 2.0 driver (usbaudio2.sys) isn't classified as a generic driver in Windows 10 Version 1703. Therefore, the system assumes that a compatible, nongeneric driver is installed for the device even though the driver is generic.
This issue also causes Windows 10 Version 1703 to postpone the search for other compatible drivers through Windows Update that typically occurs immediately after you install a new device.
Resolution
To fix this issue, use one of the following methods.
Method 1
To resolve this issue, install update 4022716.
Method 2
If the device-specific driver is distributed through Windows Update, you can manually update the driver by using Device Manager. For more information about how to do this, see update drivers in Windows 10.
Method 3
If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. After the device-specific driver is installed, Windows 10 will select that driver instead of the standard USB audio 2.0 driver when you first connect the device.
Note
See the device manufacturer's user guide for specific instructions about how to install the driver.
Method 4
If the driver isn't distributed through Windows Update, you can manually reinstall the driver. To do this, follow these steps:
- Install the device-specific driver (see Method 2).
- Open Device Manager.
- Right-click (or tap and hold) the name of the device, and then select Uninstall.
- Restart the computer.
When it restarts, Windows will try to reinstall the device by using the device-specific driver.
-->
Summary
Resources for USB device builders
This section provides links for manufacturers of USB peripheral devices.
USB device enumeration process
How does USB stack enumerate a device?
A detailed description of the enumeration process used by the Microsoft USB driver stack - starting from when the stack detects the presence of a device and indicates to the PnP manager that a new device has arrived.
USB 2.1, 2.0, 1.1 device enumeration changes in Windows 8
In Windows 8, we’ve made modifications in the USB driver stack in how the stack enumerates USB 2.1, 2.0, and 1.1 devices. Those modifications support new USB features and improve device enumeration performance. Read the post is to bring awareness to those subtle changes and enable device/firmware builders to easily determine the root cause of enumeration failures.
Microsoft OS descriptors
USB devices store standard descriptors in firmware for the device and its interfaces and endpoints. In addition, the device can store class and vendor-specific descriptors. However, the types of information that those descriptors can contain is limited. IHVs typically must use Windows Update or media such as CDs to provide their users with a variety of device-specific information such as pictures, icons, and custom drivers.
An IHV can use Microsoft OS descriptors to store the information in firmware instead of providing it separately. Window retrieves that information by reading Microsoft OS descriptors, and uses it to install and configure the device without requiring any user interaction. See Microsoft OS Descriptors for USB Devices.
Microsoft OS 1.0 Descriptors Specification
This document introduces Microsoft OS descriptors. It includes a specification for the OS string descriptor, extended properties OS feature descriptor, and OS feature descriptors formats.
Microsoft OS 2.0 Descriptors Specification
This document defines and describes the implementation of version 2.0 of the Microsoft OS Descriptors. The goal of Microsoft OS 2.0 Descriptors is to address the limitations and reliability problems with version 1.0 of OS descriptors and enable new Windows-specific functionality for USB devices.
Loading Winusb.sys as the function driver by using Microsoft OS descriptors
The IHV can define certain Microsoft operating system (OS) feature descriptors that report the compatible ID as 'WINUSB'. Those descriptors allow Windows to load Winusb.sys as the device's function driver without a custom INF file. For examples about how to define the compatible ID, see the example section of the Extended Compat ID OS Feature Descriptor Specification. The specification is included in the download for Microsoft OS 1.0 Descriptors Specification.
Setting a container ID
Container IDs for USB Devices
Describes how Container IDs for Universal Serial Bus (USB) devices are generated.
USB ContainerIDs in Windows
Guidelines for device manufacturers to program their multifunction USB devices so that they can be correctly detected by Windows.
How to Generate a Container ID for a USB Device
The blog post describes how a device must report a container ID such that Windows enumerates and shows the device in Devices and Printers properly. For devices that support multiple functions (composite device) or components (compound device), the device must report the same ID for each portion. The device must report the ID in a Microsoft OS ContainerID descriptor.
Implementing power management
Link Power management in USB 3.0 Hardware
This document provides guidelines for hardware vendors and OEMs to implement power management for USB devices by using Link Power Management (LPM) in conjunction with Selective Suspend. It explains hardware transitions from U1 to U2 and provides information about common pitfalls in LPM implementation in USB controllers, hubs, and devices.
Drivers Usb Devices Usb Devices Dongle
Demystifying selective suspend
This blog post describes how the USB driver stack handles function and selective suspend in USB 3.0 devices.
Driver For Usb Drive
Debugging and diagnostic tools
USB Event Tracing for Windows
Event Tracing for Windows (ETW) is a general-purpose, high-speed tracing facility that is provided by the operating system. It includes information on how to install the tools, create trace files, and analyze the events in a USB trace file.
WPP Software Tracing
How to use the default operation of the Windows software trace preprocessor (WPP) to trace the operation of a software component (trace provider).
USB 3.0 Extensions (usb3kd.dll)
These commands display information from data structures maintained by three drivers in the USB 3.0 stack: the USB 3.0 hub driver, the USB host controller extension driver, and the USB 3.0 host controller driver.
USB 2.0 Extensions (usb2kd.dll)
These commands display information from data structures maintained by drivers in the USB 2.0 stack: the USB 2.0 hub driver and the USB 2.0 host controller driver.