-->

For certain Universal Serial Bus (USB) devices, such as devices that are accessed by only a single application, you can install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.

This topic contains these sections:

Download Realtek USB Audio Driver 6.3.9600.40 for Windows 10 64-bit (Sound Card). Feb 04, 2021 Below, we are sharing the links to USB drivers for most of the popular Android device manufacturers like Samsung, LG, Sony, Google, HTC, Motorola, Dell, etc. These USB drivers are safe to use as they are from their respective manufacturers. All the links are valid and official. We recommend you to download the latest USB drivers.

Automatic installation of WinUSB without an INF file

As an OEM or independent hardware vendor (IHV), you can build your device so that the Winusb.sys gets installed automatically on Windows 8 and later versions of the operating system. Such a device is called a WinUSB device and does not require you to write a custom INF file that references in-box Winusb.inf.

When you connect a WinUSB device, the system reads device information and loads Winusb.sys automatically.

For more information, see WinUSB Device.

Lighting Soft Usb Devices Driver Download For Windows 7

Installing WinUSB by specifying the system-provided device class

When you connect your device, you might notice that Windows loads Winusb.sys automatically (if the IHV has defined the device as a WinUSB Device). Otherwise follow these instructions to load the driver:

Driver Download For Windows 10

1. Plug in your device to the host system.
2. Open Device Manager and locate the device.
3. Select and hold (or right-click) the device and select Update driver software.. from the context menu.
4. In the wizard, select Browse my computer for driver software.
5. Select Let me pick from a list of device drivers on my computer.
6. From the list of device classes, select Universal Serial Bus devices.
7. The wizard displays WinUsb Device. Select it to load the driver.

If Universal Serial Bus devices does not appear in the list of device classes, then you need to install the driver by using a custom INF.The preceding procedure does not add a device interface GUID for an app (UWP app or Windows desktop app) to access the device. You must add the GUID manually by following this procedure. Intellitools driver jobs.

1. Load the driver as described in the preceding procedure.

2. Generate a device interface GUID for your device, by using a tool such as guidgen.exe.

3. Find the registry key for the device under this key:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB<VID_vvvv&PID_pppp>

4. Under the Device Parameters key, add a String registry entry named DeviceInterfaceGUID or a Multi-String entry named DeviceInterfaceGUIDs. Set the value to the GUID you generated in step 2.

5. Disconnect the device from the system and reconnect it to the same physical port.Note If you change the physical port then you must repeat steps 1 through 4.

Writing a custom INF for WinUSB installation

As part of the driver package, you provide an .inf file that installs Winusb.sys as the function driver for the USB device.

The following example .inf file shows WinUSB installation for most USB devices with some modifications, such as changing USB_Install in section names to an appropriate DDInstall value. You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufacture's name, the name of your signed catalog file, the correct device class, and the vendor identifier (VID) and product identifier (PID) for the device.

Also notice that the setup class is set to 'USBDevice'. Vendors can use the 'USBDevice' setup class for devices that do not belong to another class and are not USB host controllers or hubs. Idblue driver.

If you are installing WinUSB as the function driver for one of the functions in a USB composite device, you must provide the hardware ID that is associated with the function, in the INF. You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. The hardware ID string format is 'USBVID_vvvv&PID_pppp'.

The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system.

Starting in Windows 10, version 1709, the Windows Driver Kit provides InfVerif.exe that you can use to test a driver INF file to make sure there are no syntax issues and the INF file is universal. We recommened that you provide a universal INF. For more information, see Using a Universal INF File.

Only include a ClassInstall32 section in a device INF file to install a new custom device setup class. INF files for devices in an installed class, whether a system-supplied device setup class or a custom class, must not include a ClassInstall32 section.

Except for device-specific values and several issues that are noted in the following list, you can use these sections and directives to install WinUSB for any USB device. These list items describe the Includes and Directives in the preceding .inf file.

• USB_Install: The Include and Needs directives in the USB_Install section are required for installing WinUSB. You should not modify these directives.

• USB_Install.Services: The Include directive in the USB_Install.Services section includes the system-supplied .inf for WinUSB (WinUSB.inf). This .inf file is installed by the WinUSB co-installer if it isn't already on the target system. The Needs directive specifies the section within WinUSB.inf that contains information required to install Winusb.sys as the device's function driver. You should not modify these directives.Note Because Windows XP doesn't provide WinUSB.inf, the file must either be copied to Windows XP systems by the co-installer, or you should provide a separate decorated section for Windows XP.

• USB_Install.HW: This section is the key in the .inf file. It specifies the device interface globally unique identifier (GUID) for your device. The AddReg directive sets the specified interface GUID in a standard registry value. Drivers ibm motherboards drivers. When Winusb.sys is loaded as the device's function driver, it reads the registry value DeviceInterfaceGUIDs key and uses the specified GUID to represent the device interface. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID.

  Note User-mode software must call SetupDiGetClassDevs to enumerate the registered device interfaces that are associated with one of the device interface classes specified under the DeviceInterfaceGUIDs key. SetupDiGetClassDevs returns the device handle for the device that the user-mode software must then pass to the WinUsb_Initialize routine to obtain a WinUSB handle for the device interface. For more info about these routines, see How to Access a USB Device by Using WinUSB Functions.

The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system. The example shows INF with WDF coinstallers.

• USB_Install.CoInstallers: This section, which includes the referenced AddReg and CopyFiles sections, contains data and instructions to install the WinUSB and KMDF co-installers and associate them with the device. Most USB devices can use these sections and directives without modification.

• The x86-based and x64-based versions of Windows have separate co-installers.

  Note Each co-installer has free and checked versions. Use the free version to install WinUSB on free builds of Windows, including all retail versions. Use the checked version (with the '_chk' suffix) to install WinUSB on checked builds of Windows.

Each time Winusb.sys loads, it registers a device interface that has the device interface classes that are specified in the registry under the DeviceInterfaceGUIDs key.

Note If you use the redistributable WinUSB package for Windows XP or Windows Server 2003, make sure that you don't uninstall WinUSB in your uninstall packages. Other USB devices might be using WinUSB, so its binaries must remain in the shared folder.

How to create a driver package that installs Winusb.sys

To use WinUSB as the device's function driver, you create a driver package. The driver package must contain these files:

• WinUSB co-installer (Winusbcoinstaller.dll)
• KMDF co-installer (WdfcoinstallerXXX.dll)
• An .inf file that installs Winusb.sys as the device's function driver. For more information, see Writing an .Inf File for WinUSB Installation.
• A signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows starting with Vista.

Note Make sure that the driver package contents meet these requirements:

• The KMDF and WinUSB co-installer files must be obtained from the same version of the Windows Driver Kit (WDK).
• The co-installer files must be obtained from the latest version of the WDK, so that the driver supports all the latest Windows releases.
• The contents of the driver package must be digitally signed with a Winqual release signature. For more info about how to create and test signed catalog files, see Kernel-Mode Code Signing Walkthrough on the Windows Dev Center - Hardware site.

1. Download the Windows Driver Kit (WDK) and install it.

2. Create a driver package folder on the machine that the USB device is connected to. For example, c:UsbDevice.

3. Copy the WinUSB co-installer (WinusbcoinstallerX.dll) from the WinDDKBuildNumberredistwinusb folder to the driver package folder.

   The WinUSB co-installer (Winusbcoinstaller.dll) installs WinUSB on the target system, if necessary. The WDK includes three versions of the co-installer depending on the system architecture: x86-based, x64-based, and Itanium-based systems. They are all named WinusbcoinstallerX.dll and are located in the appropriate subdirectory in the WinDDKBuildNumberredistwinusb folder.

4. Copy the KMDF co-installer (WdfcoinstallerXXX.dll) from the WinDDKBuildNumberredistwdf folder to the driver package folder.

   The KMDF co-installer (WdfcoinstallerXXX.dll) installs the correct version of KMDF on the target system, if necessary. The version of WinUSB co-installer must match the KMDF co-installer because KMDF-based client drivers, such as Winusb.sys, require the corresponding version of the KMDF framework to be installed properly on the system. For example, Winusbcoinstaller2.dll requires KMDF version 1.9, which is installed by Wdfcoinstaller01009.dll. The x86 and x64 versions of WdfcoinstallerXXX.dll are included with the WDK under the WinDDKBuildNumberredistwdf folder. The following table shows the WinUSB co-installer and the associated KMDF co-installer to use on the target system.

   Use this table to determine the WinUSB co-installer and the associated KMDF co-installer.

   WinUSB co-installer	KMDF library version	KMDF co-installer
   Winusbcoinstaller.dll	Requires KMDF version 1.5 or later	Wdfcoinstaller01005.dll Wdfcoinstaller01007.dll Wdfcoinstaller01009.dll
   Winusbcoinstaller2.dll	Requires KMDF version 1.9 or later	Wdfcoinstaller01009.dll
   Winusbcoinstaller2.dll	Requires KMDF version 1.11 or later	WdfCoInstaller01011.dll

5. Write an .inf file that installs Winusb.sys as the function driver for the USB device.

6. Create a signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows.

7. Attach the USB device to your computer.

8. Open Device Manager to install the driver. Follow the instructions on the Update Driver Software wizard and choose manual installation. You will need to provide the location of the driver package folder to complete the installation.

Related topics

WinUSB Architecture and Modules
Choosing a driver model for developing a USB client driver
How to Access a USB Device by Using WinUSB Functions
WinUSB Power Management
WinUSB Functions for Pipe Policy Modification
WinUSB Functions
WinUSB

As some people may know I am a big fan of Windows 95 because it canbe installed without any web browser. Unfortunately for me manufacturersno longer provide Windows 95 drivers for most newer devices, or if theydo they install a mess of software that often requires IE. As such I amvery cautious about what hardware I add to my computer.

From using flash drives on other computers I have discovered how incrediblyuseful these things are. They can store as much as or more than a CD-ROMbut they can be written to randomly. Supposedly there is a write limitof perhaps a hundred thousand writes but this still makes them way morereliable than floppy disks.

Of course the only driver I could find for my Sandisk Cruzer only workedon Windows 98 SE. Now the funny thing is that USB mass storage deviceslike this use a somewhat standard communication protocol and work 'outof the box' on most newer operating systems. This is true for Linux, MacOSX, OS/2 eComstation, and Windows XP. So I looked around to see if anybodyhad a USB mass storage driver for Windows 95 that would work with standarddevices like this.

I eventually found one that was intended for an older Sandisk USB device.I had to modify the Plug-And-Play ID numbers to match the one being sentby the Cruzer before Windows would accept the driver. But after that itworked perfectly! I just plug in the Cruzer and a new removable drive letterappears in My Computer.

I also added PNP ids for many devices. I don't know if it works withall of the IDs I added, but feel free to let me know what works and whatdoesn't. You should even be able to use it even if it doesn't specificallyrecognize your device!

Requirements:

• Windows 95 OSR/2.1 ('B' version with the 'USB Supplement to OSR2' installed)or Windows 98 with a USB port that is already recognized by the system.

1. This driver is not supported by SanDisk or any other manufacturer.
2. This driver may not work on your machine or with your USB memory device,I only know it works for me.
3. For all I know this driver may cause damage to your machine, your USB memorydevice, or the files on your USB memory device.
4. Any additional software that comes with your USB memory device probablywill not work and should not be used.

• Unzip the file below in to a folder on your 95/98 machine's hard drivesuch as C:USB95
• Insert your USB memory device in to a USB port.
• The 'Add New Hardware' wizard should appear and ask for a driver.
• Point it to C:USB95. It will copy the files and start the driver. (Itmay ask for the location more than once)
• Your drive should now appear as an icon in 'My Computer'.

Download USB mass storage driver for Windows 95 OSR/2.1 (Updated 1/24/2007)

w95usbflash11.zip

Same thing as above, but in a self extracting executable format incase you do not have a program to uncompress ZIP files.

95usbflash11.exe

• If you are running the OSR/2.0 'B' version of Windows 95 you must firstinstall the USB supplement from Microsoft if it is not already installed.(search for 'Usbsupp.exe').Note that none of this will work on the original 'A' version of Windows95.
• If your USB flash drive or mass storage device is not specifically recognizedby this driver, Windows will prompt you to install a new driver. Keep theabove driver on your hard disk and point the New Hardware Wizard to thedriver. This *should* let it use the driver if it really is a compatiblestorage device.
• If your system freezes up while communicating with your USB device checkand see if your USB port uses the same IRQ as another device and changeit if possible.
• If your motherboard USB hardware is not recognized, check your BIOS toensure the USB hardware is enabled (some have an option to enable or disablebuilt in USB).
• If you previously attempted to install a driver on 95 intended for Windows98 you may need to remove all INF files from that driver in 'c:windowsinf'before this one will work.
• I noticed sometimes after installing/re-installing the driver the drivefails to mount or show up in 'My Computer' even after rebooting.If this happens, try going to the device manager, open the hard drivesgroup, and find and remove the entry for your drive from there. Then removeand re-insert the flash drive and it should be found again.
• USB 1.1 hardware found on older machines is slower than modern USB ports.This is not a software or OS issue.
• If you have many small files to copy to the device, consider zipping themfirst. This can speed things up and reduce the number of writes to thefile system area.
• Regardless of what OS you are running, if your USB ports are all on theback of your computer I highly recommend buying a USB extension cable.Makes life much easier. (And reduces wear on your computer's USB plug)
• There is also a USB system with a generic USB mass storage driver for WindowsNT 4 locatedhere(it is part of a bundle for some camera device.) For larger flash driveson NT 4 you may also need the FAT32 filesystem driver located here.(Interesting trick, using this FAT32 driver and the Win2000 bootloaderyou can boot NT 4 from FAT32)
• And believe it or not, there is even a USBstorage driver for DOS! This can also be used under the 'a' versionof Windows 95.
• Avoid the Sandisk models with the 'U3' autorun stuff on it. Those can havefreezing issues even after the U3 stuff is removed. Currently I have hadvery good luck with the Kingston DataTraveler USB Flash drives.