- Microsoft Usb 2.0 Driver Download
- Lenovo Usb 2.0 Controller Driver
- Usb 2.0 Driver Windows 10
- Intel Usb 2.0 Controller Driver Windows 7
- Usb 2.0 Controller Driver Windows Xp
After you upgrade your computer to Windows 10, if your Intel USB Drivers are not working, you can fix the problem by updating the drivers. It is possible that your USB driver is not compatible with the newer version of Windows.
Find Intel USB Device Drivers by Model Name or Number
How to Update Device Drivers
There are two ways to update drivers.
I have a new (May 2017) desktop PC running latest Windows 10 vn1703 with 2 USB 3.0 ports on the front and 4 USB 2.0 ports on the back. Device Manager only lists USB 3.0, i.e. One 'USB 3.0 eXtensible host controller' and one 'USB Root Hub (3.0)'. Should there be any controller or root hub for USB 2.0. Enhanced Host Controller Interface for USB 2.0: Specification The document describes the enhanced host controller interface for universal serial bus revision 2.0, including the interface between system software and host controller hardware interface.
![Usb 2. 0 Controller Driver Usb 2. 0 Controller Driver](/uploads/1/2/6/1/126155886/709937465.png)
Option 1 (Recommended): Update drivers automatically - Novice computer users can update drivers using trusted software in just a few mouse clicks. Automatic driver updates are fast, efficient and elimate all the guesswork. Your old drivers can even be backed up and restored in case any problems occur.
OR
Microsoft Usb 2.0 Driver Download
Option 2: Update drivers manually - Find the correct driver for your USB and operating system, then install it by following the step by step instructions below. You’ll need some computer skills to use this method.
Option 1: Update drivers automatically
The Driver Update Utility for Intel devices is intelligent software which automatically recognizes your computer’s operating system and USB model and finds the most up-to-date drivers for it. There is no risk of installing the wrong driver. The Driver Update Utility downloads and installs your drivers quickly and easily.
You can scan for driver updates automatically with the FREE version of the Driver Update Utility for Intel, and complete all necessary driver updates using the premium version.
Tech Tip: The Driver Update Utility for Intel will back up your current drivers for you. If you encounter any problems while updating your drivers, you can use this feature to restore your previous drivers and configuration settings.
- Download the Driver Update Utility for Intel.
- Double-click on the program to run it. It will then scan your computer and identify any problem drivers. You will see a results page similar to the one below:
- Click the Update Driver button next to your driver. The correct version will be downloaded and installed automatically. Or, you can click the Update Drivers button at the bottom to automatically download and install the correct version of all the drivers that are missing or out-of-date on your system.
Option 2: Update drivers manually
To find the latest driver, including Windows 10 drivers, choose from our list of most popular Intel USB downloads or search our driver archive for the driver that fits your specific USB model and your PC’s operating system.
If you cannot find the right driver for your device, you can request the driver. We will find it for you. Or, try the automatic option instead.
Tech Tip: If you are having trouble finding the right driver update, use the Intel USB Driver Update Utility. It is software which finds, downloads and istalls the correct driver for you - automatically.
After downloading your driver update, you will need to install it. Driver updates come in a variety of file formats with different file extensions. For example, you may have downloaded an EXE, INF, ZIP, or SYS file. Each file type has a slighty different installation procedure to follow. Visit our Driver Support Page to watch helpful step-by-step videos on how to install drivers based on their file extension.
How to Install Drivers
After you have found the right driver, follow these simple instructions to install it.
- Power off your device.
- Disconnect the device from your computer.
- Reconnect the device and power it on.
- Double click the driver download to extract it.
- If a language option is given, select your language.
- Follow the directions on the installation program screen.
- Reboot your computer.
This topic provides an overview of the Universal Serial Bus (USB) driver stack architecture.
The following figure shows the architectural block diagram of the USB driver stack for Windows 8. The diagram shows separate USB driver stacks for USB 2.0 and USB 3.0. Windows loads the USB 3.0 driver stack when a device is attached to an xHCI controller. The USB 3.0 stack is new in Windows 8.
Windows loads the USB 2.0 driver stack for devices that are attached to eHCI, oHCI, or uHCI controllers. The USB 2.0 driver stack ships in Windows XP with Service Pack 1 (SP1) and later versions of the Windows operating system.
- USB 3.0 driver stack
USB 3.0 driver stack
The USB 3.0 stack is new in Windows 8. Microsoft created the new drivers by using Kernel Mode Driver Framework (KMDF) interfaces. The KMDF driver model reduces complexity and improves stability.
USB 3.0 host controller driver (Usbxhci.sys)
The xHCI driver is the USB 3.0 host controller driver. The responsibilities of the xHCI driver include initializing MMIO registers and host memory-based data structures for xHCI controller hardware, mapping transfer requests from upper layer drivers to Transfer Request Blocks, and submitting the requests to the hardware. After completing a transfer, the driver handles transfer completion events from the hardware and propagates the events up the driver stack. It also controls the xHCI controller device slots and endpoint contexts.
The xHCI driver is new in Windows 8 and is not an extension of the eHCI miniport driver that was available in earlier versions of the operating system. The new driver was written by using Kernel Mode Driver Framework (KMDF) interfaces and uses KMDF for all controller power management and PnP events. Windows loads the xHCI driver as the function device object (FDO) in the device stack for the host controller.
USB host controller extension (Ucx01000.sys)
The USB host controller extension driver (an extension to KMDF) is the new extension to the underlying class-specific host controller driver, such as the xHCI driver. The new driver is extensible and is designed to support other types of host controller drivers that are expected to be developed in the future. The USB host controller extension serves as a common abstracted interface to the hub driver, provides a generic mechanism for queuing requests to the host controller driver, and overrides certain selected functions. All I/O requests initiated by upper drivers reach the host controller extension driver before the xHCI driver. Upon receiving an I/O request, the host controller extension validates the request and then forwards the request to the proper KMDF queue associated with the target endpoint. The xHCI driver, when ready for processing, retrieves the request from the queue. The responsibilities of the USB host controller extension driver are:
- Provides USB-specific objects to the xHCI driver.
- Provides KMDF event callback routines to the xHCI driver.
- Manages and control the operations of the root hub associated with the host controller.
- Implements features that are configurable by the client driver, like chained MDLs, streams, and so on.
USB hub driver (Usbhub3.sys)
The new hub driver, in the USB driver stack for 3.0 devices, uses the KMDF driver model. The hub driver primarily performs these tasks:
- Manages USB hubs and their ports.
- Enumerates devices and other hubs attached to their downstream ports.
- Creates physical device objects (PDOs) for the enumerated devices and hubs.
Windows loads the hub driver as the FDO in the hub device stack. Device enumeration and hub management in the new driver are implemented through a set of state machines. The hub driver relies on KMDF for power management and PnP functions. In addition to hub management, the hub driver also performs preliminary checks and processing of certain requests sent by the USB client driver layer. For instance, the hub driver parses a select-configuration request to determine which endpoints will be configured by the request. After parsing the information, the hub driver submits the request to the USB host controller extension or further processing.
USB 2.0 driver stack
Windows loads the USB 2.0 driver stack for devices that are attached to eHCI, oHCI, or uHCI controllers. The drivers in the USB 2.0 driver stack ship in Windows XP with SP1 and later versions of the Windows operating system. The USB 2.0 driver stack is designed to facilitate high-speed USB devices as defined in the USB 2.0 specification.
At the bottom of the USB driver stack is the host controller driver. It consists of the port driver, Usbport.sys, and one or more of three miniport drivers that run concurrently. When the system detects host controller hardware, it loads one of these miniport drivers. The miniport driver, after it is loaded, loads the port driver, Usbport.sys. The port driver handles those aspects of the host controller driver's duties that are independent of the specific protocol.
The Usbuhci.sys (universal host controller interface) miniport driver replaces the Uhcd.sys miniclass driver that shipped with Windows 2000. The Usbohci.sys (open host controller interface) miniport driver replaces Openhci.sys. The Usbehci.sys miniport driver supports high-speed USB devices and was introduced in Windows XP with SP1 and later and Windows Server 2003 and later operating systems.
In all versions of Windows that support USB 2.0, the operating system is capable of managing USB 1.1 and USB 2.0 host controllers simultaneously. Whenever the operating system detects that both types of controller are present, it creates two separate device nodes, one for each host controller. Windows subsequently loads the Usbehci.sys miniport driver for the USB 2.0-compliant host controller hardware and either Usbohci.sys or Openhci.sys for the USB 1.1-compliant hardware, depending on the system configuration.
Above the port driver is the USB bus driver, Usbhub.sys, also known as the hub driver. This is the device driver for each hub on the system.
USB common class generic parent driver (Usbccgp.sys)
Lenovo Usb 2.0 Controller Driver
![2.0 2.0](/uploads/1/2/6/1/126155886/568562874.jpg)
The USB common class generic parent driver is the Microsoft-provided parent driver for composite devices. The hub driver enumerates and loads the parent composite driver if deviceClass is 0 or 0xef and numInterfaces is greater than 1 in the device descriptor. The hub driver generates the compatible ID for the parent composite driver as 'USBCOMPOSITE'. Usbccgp.sys uses Windows Driver Model (WDM) routines.
The parent composite driver enumerates all functions in a composite device and creates a PDO for each one. This causes the appropriate class or client driver to be loaded for each function in the device. Each function driver (child PDO) sends requests to the parent driver, which submits them to the USB hub driver.
Usbccgp.sys is included with Windows XP with SP1 and later versions of the Windows operating system. In Windows 8, the driver has been updated to implement function suspend and remote wake-up features as defined in the USB 3.0 specification.
For more information, see USB Generic Parent Driver (Usbccgp.sys).
WinUSB (Winusb.sys)
Windows USB (WinUSB) is a Microsoft-provided generic driver for USB devices. WinUSB architecture consists of a kernel-mode driver (Winusb.sys) and a user-mode dynamic link library (Winusb.dll). For devices that don't require a custom function driver, Winusb.sys can be installed in the device's kernel-mode stack as the function driver. User-mode processes can then communicate with Winusb.sys by using a set of device I/O control requests or by calling WinUsb_Xxx functions. For more information, see WinUSB.
In Windows 8, the Microsoft-provided information (INF) file for WinUSB, Winusb.inf, contains USBMS_COMP_WINUSB as a device identifier string. This allows Winusb.sys to get automatically loaded as the function driver for those devices that have a matching WinUSB compatible ID in the MS OS descriptor. Such devices are called WinUSB devices. Hardware manufacturers are not required to distribute an INF file for their WinUSB device, making the driver installation process simpler for the end user. For more information, see WinUSB Device.
USB client driver
Each USB device, composite or non-composite, is managed by a client driver. A USB client driver is a class or device driver that is a client of the USB driver stack. Such drivers include class and device-specific drivers from Microsoft or a third-party vendor. To see a list of class drivers provided by Microsoft, see Drivers for the Supported USB Device Classes. A client driver creates requests to communicate with the device by calling public interfaces exposed by the USB driver stack.
A client driver for a composite device is no different from a client driver for a non-composite device, except for its location in the driver stack.
A client driver for a non-composite device is layered directly above the hub driver.
Usb 2.0 Driver Windows 10
For a composite USB device that exposes multiple functions and does not have a parent class driver, Windows loads the USB generic parent driver (Usbccgp.sys) between the hub driver and the client driver layer. The parent driver creates a separate PDO for each function of a composite device. Client drivers (FDOs for functions) are loaded above the generic parent driver. Vendors might choose to provide a separate client driver for each function.
A USB client driver can run in either user mode or kernel mode, depending on the requirements of the driver. USB client drivers can be written by using KMDF, UMDF, or WDM routines.
Helper libraries for client drivers
Microsoft provides the following helper libraries to help kernel-mode drivers and applications to communicate with the USB driver stack:
- Usbd.sysMicrosoft provides the Usbd.sys library that exports routines for USB client drivers. The helper routines simplify the operational tasks of a client driver. For instance, by using the helper routines, a USB client driver can build USB Request Blocks (URBs) for certain specific operations, such as selecting a configuration, and submit those URBs to the USB driver stack.
- Usbdex.libThis helper library is new for Windows 8. The library exports routines primarily for allocating and building URBs. Those routines replace some of the legacy routines exported by Usbd.sys. The new routines require the client driver to register with the USB driver stack, which maintains the handle for registration. That handle is used for calls to other Usbdex.lib routines. Certain URBs allocated by the new routines have an URB context that the USB driver uses for better tracking and processing. For more information, see Allocating and Building URBs.
- Winusb.dllWinusb.dll is a user-mode DLL that exposes WinUSB functions for communicating with Winusb.sys, which is loaded as a device's function driver in kernel mode. Applications use these functions to configure the device, retrieve information about the device, and perform I/O operations. For information about using these functions, see How to Access a USB Device by Using WinUSB Functions.
Intel Usb 2.0 Controller Driver Windows 7
Related topics
Usb 2.0 Controller Driver Windows Xp
Universal Serial Bus (USB) Drivers
USB Driver Development Guide
USB Driver Development Guide