Usbhub.sys Driver Xp

Hi, Results verified by WinDBG, DumpCHK, and BlueScreenView. The Bug_Check was FE CAUSE usbhub.sys which is a Windows component which means something else.

Microsoft driver. Microsoft USB Drivers. This site maintains listings of USB drivers available on the web, organized by company. Includes links to useful resources.

usbhub.sys driver xp usbhub.sys driver xp usbhub.sys driver xp usbhub.sys driver xp

This topic lists the Microsoft-provided drivers for the supported USB device classes.

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 Windows System32 DriverStore FileRepository 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 Technology website.

For the current list of USB class specifications and class codes, visit the USB DWG website.

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 codeDevice setup classMicrosoft-provided driver and INFWindows supportDescription

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 editionsWindows 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

Custom INF that references mdmcpq.inf

Windows 10 for desktop editions

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

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

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

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

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

Usbstor.sys

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

Uaspstor.sys is the class driver for SuperSpeed USB devices that support bulk stream endpoints. For more information see:

Hub 09h

36fc9e60-c465-11cf-8056-444553540000

Usbhub.sys

Usb.inf

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

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

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

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

Usbvideo.sys

Usbvideo.inf

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

Microsoft provides the Bthusb.sys miniport driver to manage USB Bluetooth radios. For more information, see Bluetooth Design Guide.

Miscellaneous

EFh

Note  Supports SubClass 04h and Protocol 01h

Rndismp.sys

Rndismp.inf

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 editionsWindows 10 MobileRecommended driver: WinUSB Winusb.sys

Related topics

Microsoft-provided USB drivers

Send comments about this topic to Microsoft.

How to Install XP on an External Hard Drive | eHow

usbhub.sys driver xp

How to Install XP on an External Hard Drive. Windows XP was built to run on internal system hard drives. It has no simple setup or configuration option to run on an.

Set your BIOS so that USB booting is enabled. Your BIOS must support boot from USB. Connect the USB external hard drive directly to your computer.

Make an ISO image an. iso file is an archive disk image of an optical disk from the Windows XP CD-ROM using your preferred software. Save to your hard drive.

Open the ISO file you just created. Navigate to the I386 folder, and select the following files:

TXTSETUP.SIF, DOSNET.INF, USB.IN, USBPORT.IN, and USBSTOR.IN_.

Extract the files and put them into a folder to work with.

Open a command prompt and use Cab SDK to extract the contents of the. IN files; Cab SDK is a Microsoft compression and decompression program available as an. exe file in your Windows directory. Each of the. IN files contains exactly one. inf file. An example command line would be: cabarc x USBSTOR.IN . You should end up with three new files in the folder, called usb.inf, usbport.inf and usbstor.inf. Delete the. IN files.

Open the files using a simple text editor such as Notepad. Edit them according to the section below titled Editing Files.

Open the previously created ISO file and delete the files you extracted earlier. Replace them with the newly modified files.

Save the ISO files and burn them to a CD using the burning software of your choice.

Insert the CD you created and restart the computer. Make sure it is set to boot from CD. Most computers will do this automatically, but if not, hit F8 on startup to choose boot options. When asked, choose the external USB hard drive to install WIndows XP.

Open TXTSETUP.SIF and move the following entries from InputDevicesSupport.Load to the BootBusExtenders.Load :

usbehci usbehci.sys

usbohci usbohci.sys

usbuhci usbuhci.sys

usbhub usbhub.sys

usbstor usbstor.sys

Move the following entries from InputDevicesSupport to BootBusExtenders :

usbehci Erweiterter Hostcontroller, files.usbehci,usbehci

usbohci Open Hostcontroller, files.usbohci,usbohci

usbuhci Universeller Hostcontroller, files.usbuhci,usbuhci

usbhub Standard-USB-Hubtreiber, files.usbhub,usbhub

usbstor USB-Speicherklassentreiber, files.usbstor,usbstor

Insert the following in the HiveInfs.Fresh section:

AddReg hivedef.inf,AddReg

AddReg hivesys.inf,AddReg

AddReg hivesft.inf,AddReg

AddReg hivecls.inf,AddReg

AddReg hiveusd.inf,AddReg

AddReg dmreg.inf,DM.AddReg

AddReg usbboot.inf,usbservices

Insert the following commands into the SourceDisksFiles section:

SourceDisksFiles

usbboot.inf 1,,,,,,x,3,,3

bootvid.dll 1,,,,,,3,2,0,0,,1,2

kdcom.dll 1,,,,,,3_,2,0,0,,1,2

Open DOSNET.INF and change the second Files section to look like this:

Files

d1,usbboot.inf

d1,_default.pif

d1,12520437.cpx

d1,12520850.cpx

Open USB.INF and change lines in the StandardHub.AddService and CommonClassParent.AddService sections to look like this:

StandardHub.AddService

DisplayName StandardHub.SvcDesc

ServiceType 1 ; SERVICE_KERNEL_DRIVER

StartType 0 ; SERVICE_DEMAND_START

ErrorControl 1 ; SERVICE_ERROR_NORMAL

ServiceBinary 12 usbhub.sys

LoadOrderGroup Boot Bus Extender

CommonClassParent.AddService

DisplayName GenericParent.SvcDesc

ServiceBinary 12 usbccgp.sys

LoadOrderGroup Boot Bus Extender

Open usbport.inf and change lines in the EHCI.AddService, OHCI.AddService , UHCI.AddService and ROOTHUB.AddService sections to look like this:

EHCI.AddService

DisplayName EHCIMP.SvcDesc

ServiceBinary 12 usbehci.sys

OHCI.AddService

DisplayName OHCIMP.SvcDesc

ServiceBinary 12 usbohci.sys

UHCI.AddService

DisplayName UHCIMP.SvcDesc

ServiceBinary 12 usbuhci.sys

ROOTHUB.AddService

DisplayName ROOTHUB.SvcDesc

Open usbstore.inf and change lines in the USBSTOR.AddService section to look like this:

USBSTOR.AddService

DisplayName USBSTOR.SvcDesc

ServiceType 1

StartType 0

Tag 3

ErrorControl 1

ServiceBinary 12 USBSTOR.SYS

Create a new file called USBBOOT.INF in the same directory as the other modified files, and paste the following content into it:

usbservices

HKLM, SYSTEM CurrentControlSet Services USBSTOR, DisplayName, 0x00000000, USB Mass Storage Driver

HKLM, SYSTEM CurrentControlSet Services USBSTOR, ErrorControl, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services USBSTOR, Group, 0x00000000, System Reserved

HKLM, SYSTEM CurrentControlSet Services USBSTOR, ImagePath, 0x00020000, system32 DRIVERS USBSTOR.SYS

HKLM, SYSTEM CurrentControlSet Services USBSTOR, Start, 0x00010001,0

HKLM, SYSTEM CurrentControlSet Services USBSTOR, Type, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbehci, DisplayName, 0x00000000, USB 2.0 Enhanced Host Controller Miniport Driver

HKLM, SYSTEM CurrentControlSet Services usbehci, ErrorControl, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbehci, Group, 0x00000000, System Reserved

HKLM, SYSTEM CurrentControlSet Services usbehci, ImagePath, 0x00020000, system32 DRIVERS usbehci.sys

HKLM, SYSTEM CurrentControlSet Services usbehci, Start, 0x00010001,0

HKLM, SYSTEM CurrentControlSet Services usbehci, Type, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbhub, DisplayName, 0x00000000, USB2 Enabled Hub

HKLM, SYSTEM CurrentControlSet Services usbhub, ErrorControl, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbhub, Group, 0x00000000, System Reserved

HKLM, SYSTEM CurrentControlSet Services usbhub, ImagePath, 0x00020000, system32 DRIVERS usbhub.sys

HKLM, SYSTEM CurrentControlSet Services usbhub, Start, 0x00010001,0

HKLM, SYSTEM CurrentControlSet Services usbhub, Type, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbuhci, DisplayName, 0x00000000, Microsoft USB Universal Host Controller Miniport Driver

HKLM, SYSTEM CurrentControlSet Services usbuhci, ErrorControl, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbuhci, Group, 0x00000000, System Reserved

HKLM, SYSTEM CurrentControlSet Services usbuhci, ImagePath, 0x00020000, system32 DRIVERS usbuhci.sys

HKLM, SYSTEM CurrentControlSet Services usbuhci, Start, 0x00010001,0

HKLM, SYSTEM CurrentControlSet Services usbuhci, Type, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbohci, DisplayName, 0x00000000, Microsoft USB Open Host Controller Miniport Driver

HKLM, SYSTEM CurrentControlSet Services usbohci, ErrorControl, 0x00010001,1

HKLM, SYSTEM CurrentControlSet Services usbohci, Group, 0x00000000, System Reserved

HKLM, SYSTEM CurrentControlSet Services usbohci, ImagePath, 0x00020000, system32 DRIVERS usbohci.sys

HKLM, SYSTEM CurrentControlSet Services usbohci, Start, 0x00010001,0

HKLM, SYSTEM CurrentControlSet Services usbohci, Type, 0x00010001,1

Delete your original extracted. IN files. Open the command prompt and navigate to the folder with your changed files. Execute these commands to repack the files:

cabarc n USB.IN usb.inf

cabarc n USBPORT.IN usbport.inf

cabarc n USBSTOR.IN usbstor.inf

The three IN_ files should now exist again. Return to Step 6 above to complete.

USB device class drivers included in Windows

Medtronic CareLink USB Free Driver Download. World s most popular driver download site.

Creating an XP Installation Disk. After setting up your Eee BIOS, you need to go back to your other PC to make a custom XP install disk. I suggest using a rewritable.

Full article here. What is this about. To keep the introduction short, Microsoft denies that booting Windows off a USB drive works. See this page for example.