Download the file hyperxcloudiifirmwareupdaterrev0010.exe from the official HyperX support archive. Right-click the .exe file and select .
Press and hold the microphone mute button on the USB control box for 2–3 seconds. You should hear a faint beep or see a change in the LED behavior.
Running a legacy Kingston firmware updater on a newer HP-manufactured headset can permanently brick the USB control box. How to Safely Install Rev 0010 Firmware
It addresses sync issues between the Windows system volume mixer and the hardware buttons on the dongle. hyperxcloudiifirmwareupdaterrev0010 exe file 2021
Before seeking out and running this executable, you must check the physical branding of your headset.
In late 2020, HP acquired the HyperX peripherals division from Kingston Technology. Consequently, there are two distinct versions of the Cloud II floating around:
: Added full audio and microphone support for PS4 and PS5 via the USB control box. Download the file hyperxcloudiifirmwareupdaterrev0010
If the standalone .exe fails, you can use the HyperX NGENUITY software from the Microsoft Store, which can automatically detect and update many newer versions of the headset.
: Never unplug the headset while the progress bar is moving, as this can permanently disable the USB sound card. If you'd like, I can help you: official download link for this specific file. Troubleshoot why your PC isn't recognizing the headset even after the update. Check if your headset is the HP or Kingston
This is where the update shines. It fixes the "low volume" bug on PS4/PS5, ensuring the hardware buttons on the dongle actually scale the audio correctly within the console's OS. The Downsides You should hear a faint beep or see
Some users noted a slight reduction in "static hiss" when using the mic monitoring (if enabled via Windows), though this wasn't an officially documented fix.
This feature moves the updater from a simple "file copier" to a robust diagnostic tool. By adding the Read-Back Verification and SafeState Bootloader , we protect the user from the most common causes of hardware failure during firmware updates.