- Corsair USB Devices Driver Download For Windows 10
- Corsair Usb Dongle Driver
- Corsair Link Windows 10 Driver
Download Corsair other device drivers or install DriverPack Solution software for driver scan and update. Corsair Hydro Series 7289 USB Device. Windows XP, 7, 8, 8.1, 10 (x64, x86) Category: other devices. Subcategory: Corsair other devices. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in androidsdk extras google usbdriver. Click Next to install the driver. To install the Android USB driver on Windows 8.1 for the first time, do the following: Connect your Android device to your computer's USB port.
-->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.

Corsair USB Devices Driver Download For Windows 10
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
Gaming enthusiasts understand the importance of using a high-quality gaming headset like Corsair. Corsair gaming headsets have gained popularity among gamers due to their top-notch specs and versatility. With Dolby Surround 7.1, wireless capabilities of up to 40 feet, and staggering sound quality, Corsair gaming headsets take gaming audio to a whole new level.
If you play your games on a Windows 10 PC, chances are you’ve encountered several Corsair headset sound issues, such as no sound from the headset. Most users have reported that the issues start after upgrading from Windows 8 to Windows 10. If that’s the case, this post explains how to fix Corsair headset sound issues on Windows 10. We also show you how to download audio drivers for the Corsair headset using two methods.
What Causes Corsair Sound Issues?
Like we mentioned above, if you just upgraded to Windows 10, then there could be hardware and software conflicts affecting the Corsair headset. Likewise, if the errors appear immediately after installing Windows updates, then the updates could be causing the sound issues. Another factor that could trigger Corsair sound issues is an iCUE software update. iCUE is the complete software package that supports all of Corsair products, such as RGB LED lighting control, keyboards, and mice, in one central place.
The best way out is to update your Corsair headset drivers so that they correspond with the new software. But first, try connecting the Corsair headset to a different computer to check if it’s having the same sound issues. If it works fine, then your Windows system or hardware installed on your PC could be responsible for the errors. To fix Corsair sound issues, you could try running the sound troubleshooter or updating Corsair headset drivers.
Troubleshoot Sound Problems
Start by running the audio troubleshooter to check for and repair sound issues. Troubleshooter is an automated Windows utility that helps to fix common PC problems. The tool can be accessed via the “Settings” app using the steps below:

- Press Win + I.
- Once in the “Settings” app, open Update & Security > Troubleshoot.
- Click on “Playing Audio” and select “Run the troubleshooter”.
- Wait while Windows tries to detect and fix issues affecting audio output. Now launch your favorite game and check if the sound issues have been resolved.
How to Update Corsair Headset Driver on Windows 10
To enjoy smooth, uninterrupted audio while playing your PC games, it’s imperative to install the latest driver updates for your Corsair headset drivers. Since drivers enable your system to communicate with the headset, having outdated, corrupt, or missing drivers can cause sound issues.
Luckily, Corsair releases driver updates regularly. You can check on Corsair’s official website if you’re running the latest drivers. If not, you need to update them using one of the methods below:

Method 1: Manually Updating Corsair Headset Drivers
If you’re tech-savvy and have the time, you can manually update your Corsair headset drivers. The process involves searching for the correct drivers on the official Corsair website and downloading them. Next, extract the drivers and install them. Note that you must know the driver model and version that corresponds with your Windows operating system so that you can avoid downloading the wrong driver. Installing the wrong Corsair drivers can make sound issues even worse or create new problems.
- Open the official Corsair website, and click Support > Downloads.
- Find the correct drivers for your hardware and click the download icon to start the download.
- Before you install the new drivers, you should first uninstall the old drivers to avoid conflicts.
- Once you’re done, run the downloaded file and follow the installation wizard to the last step.
- Once the process completes successfully, restart Windows to apply the changes.
Now that you’re running the latest Corsair headset driver version, you should not encounter any audio issues.
Method 2: Using Auslogics Driver Updater
What if you don’t have the experience to download Corsair headset drivers manually? Well, you don’t have to worry. Auslogics Driver Updater makes the work easier for you. This is an automated tool that runs diagnostics on your PC to check for missing, outdated and corrupted drivers. After that, the program provides a comprehensive report of your drivers with clear details about the status of the drivers.
To fix the driver issues, simply select the drivers that you want to be updated and click the “Update all” button. The tool first creates a backup of your old drivers before installing the new ones. This way, if your computer develops driver-related problems, you can simply restore the drivers and get on with your work. Since Auslogics Driver Updater automatically updates all of the available device drivers on your PC, you can rest assured that only compatible drivers will be installed.
We recommend using this program to update your Corsair headset drivers since all related drivers will also be updated in the process. Once the tool finishes installing the latest drivers, restart your machine and check for sound issues. If they have been resolved, then you’re good to go. If not, then try the next solution below.
Reinstall Corsair Audio Drivers and iCUE Software
If updating Corsair audio drivers and troubleshooting sound issues doesn’t work, you could try uninstalling the drivers and iCUE software and reinstalling them again.
To uninstall Corsair audio drivers, follow these steps:
- Open “Device Manager”. To do so, press the Windows Key and S combination, and type “Device Manager” (without quotes). Select “Device Manager” from the results.
- Go to “Audio inputs and outputs” and expand it.
- Right-click on each of your Corsair devices and select “Uninstall device”.
- Now, unplug the Corsair headset from your PC and reboot Windows.
- Once Windows has finished loading, go to start and launch “Control Panel”.
- Open the “Uninstall a program” link.
- Navigate to Corsair iCUE, right-click on it, and select “Uninstall”. To make sure that you remove all the files associated with iCUE, go to C:Users<username>AppData and delete the Corsair folders in the “Local” and “Roaming” folders. If you don’t see AppData, click “View” in the “File Explorer” ribbon, and then check the “Hidden items” option.
- Restart your computer again.
- Now, go to the official Corsair website, download iCUE software afresh, and install it on your PC.
- Restart your computer for the changes to take effect.
- Make sure iCUE is running and then plug in your Corsair headset.
Corsair Usb Dongle Driver
Now, go ahead and test the headset for sound issues. Most users found this fix useful, and it should work on your PC as well. If you’re like other gamers who are wondering where to get the Corsair headset driver on Windows 10, click here to go directly to the official website.
Corsair Link Windows 10 Driver
Which of the solutions above fixed your Corsair audio issues? We’d love to hear your feedback on the comments section below.
