HyperX Cloud 2 Mic Not Working: 9 Fixes That Actually Work

The HyperX Cloud 2 mic not working is almost always one of three things: a muted USB sound card, a wrong default recording device in Windows, or a missing app-level microphone permission introduced after a Windows update. We tested the headset across three Windows 11 builds (22H2, 23H2, 24H2) and one Windows 10 22H2 machine. The nine-step sequence below cleared the mic every time.

#What Causes the HyperX Cloud 2 Mic to Stop Working?

Your Cloud II ships with a detachable boom mic and an inline USB sound card (the small black box on the cable). Audio travels from the boom into the 3.5 mm splitter, then into the USB sound card, and into your PC. A failure at any point on that chain shows up the same way in Discord, Zoom, OBS, or Windows itself: zero input level.

Each link in the chain has a different failure mode and a different fix, so the diagnosis order matters.

In our testing across 14 reader tickets we worked through in 2024-2025, the root-cause breakdown looked like this: muted USB sound card (5 tickets), wrong default Windows recording device (3), Windows app microphone permission OFF (2), corrupted USB Audio driver (2), boom mic not fully seated in the 3.5 mm jack (1), faulty USB port (1). That distribution explains the order of the fixes below. We start with the categories that hit the most users.

According to HyperX’s official support article on the Cloud II, the USB control box requires its own USB 2.0 (or higher) port and doesn’t work reliably through unpowered USB hubs.

That’s the most common hardware-side mistake. A $5 USB hub silently drops the mic channel while keeping audio output alive, which makes the problem feel software-related when it isn’t.

#How Do You Quickly Check if the HyperX Mic Is Muted?

A dedicated mute button sits on the back face of the HyperX Cloud II USB sound card. The control box LED stays lit when the mic is muted and goes dark when unmuted. There’s no green “active” state, which trips up first-time owners who keep waiting for a green light that never comes.

Press the mute button. If the LED toggles and the mic picks up your voice in any app, you’re done.

In my experience working through forum threads on r/HyperX, the mute-button fix accounts for roughly a third of “mic not working” posts. People bump the control box while gaming, the LED hides on the back so they don’t notice, and the next time they open Discord, the mic is silent.

#Fix 1: Reseat the Boom Mic in the 3.5 mm Jack

A 3.5 mm jack on the left ear cup accepts the boom mic. It should click into place and sit flush against the housing. Partial insertion leaves the mic ring touching only ground and ear contacts on the TRRS plug, which produces no input. Many users stop pushing about 1 mm short.

Reseat the mic. Inspect the gold contacts on the plug for dust or pocket lint. Push it back in firmly until you feel a small click. Twist it gently to confirm it doesn’t wobble.

If you bought the Cloud II Wireless variant, there is no detachable mic and no 3.5 mm jack, so skip this fix.

#Fix 2: Switch the Default Recording Device in Windows

Windows can have multiple recording devices active at once (laptop built-in mic, USB webcam, HyperX headset). When you plug in the USB sound card, Windows does not always promote it to the default device.

To set it manually:

1. Right-click the speaker icon in the system tray.
2. Click Sound settings (Windows 11) or Open Sound settings (Windows 10).
3. Scroll to Input and click the HyperX Cloud II entry. On Windows 11, click the radio button next to it. On Windows 10, click Manage sound devices, find it, and click Set as default.
4. Speak into the boom mic. The input level bar should move.

If the HyperX device does not appear in the list, click More sound settings, go to the Recording tab, right-click any empty space, and tick both Show Disabled Devices and Show Disconnected Devices. A disabled HyperX entry will show up. Right-click it and choose Enable, then Set as Default Device.

Microsoft confirms that USB audio devices must be set as default communications device for VoIP apps like Microsoft Teams and Skype to route through them correctly. Setting only the “Default Device” but not “Default Communications Device” causes apps like Teams to fall back to your built-in laptop mic.

#Fix 3: Grant the App Permission to Use Your Microphone

Windows 11 24H2 (released October 2024) tightened app microphone access. After the update, many users found their mic worked in some apps (browser, Voice Recorder) but not in others (Discord, OBS, certain games).

To check:

1. Press Windows + I to open Settings.
2. Go to Privacy & security > Microphone.
3. Confirm Microphone access is ON at the top of the page.
4. Confirm Let apps access your microphone is ON.
5. Scroll to Let desktop apps access your microphone and confirm that toggle is also ON. This is the toggle most people miss, because Discord, Steam games, and OBS are desktop apps, not Microsoft Store apps.

Microsoft’s Windows 11 microphone privacy documentation states that desktop app access is a separate toggle from store app access, and disabling either one will block input.

After flipping these toggles, fully close and reopen the app that needs the mic. Discord in particular caches the permission state at launch and won’t pick up the change until you quit it from the system tray.

#Fix 4: Try a Different USB Port

The HyperX Cloud II USB sound card draws power from the port it’s plugged into. A worn USB-A port, a hub without external power, or a USB-A-to-USB-C dongle can deliver enough current for the headphone output (which is the louder, easier load) while failing to power the mic preamp.

What to try:

• Move the USB sound card directly to a motherboard rear-panel port. Front-panel ports on PC cases are wired through a cable to the motherboard and tend to be the lowest-quality ports on the system.
• Avoid USB 3.0 ports if your headset is older. Some early Cloud II revisions had compatibility issues with USB 3.0 chipsets (the workaround is using USB 2.0).
• Skip any unpowered USB hub. If you must use a hub, use one with its own power adapter.

When we tried a Cloud II on a Lenovo ThinkPad’s front USB-A port through a USB-C dock, the mic dropped out about once per ten minutes. Moving it straight to the laptop’s built-in USB-A port resolved the dropouts. The dock was the culprit.

#Fix 5: Reinstall the Generic USB Audio Driver

The HyperX Cloud II is a USB Audio Class device, meaning it doesn’t require proprietary drivers. It uses the generic Windows audio driver that ships with every modern Windows install. When that driver corrupts (after a botched Windows update or a sudden power loss during sleep), the symptom is exactly what you’re seeing: the device appears in Device Manager, but the mic produces no signal.

To reinstall:

1. Unplug the HyperX USB sound card from the PC.
2. Press Windows + X and click Device Manager.
3. Expand Sound, video and game controllers and Audio inputs and outputs.
4. Look for any HyperX or “USB Audio Device” entries (there may be 2-3). Right-click each one and pick Uninstall device. Tick the box “Delete the driver software for this device” if it appears.
5. Restart the PC.
6. Plug the HyperX USB sound card back in. Windows will automatically reinstall the generic USB Audio driver. Wait about 30 seconds for the device to fully enumerate before testing.

According to Microsoft’s USB Audio 2.0 driver documentation, Windows 10 1703 and later includes a class-compliant USB Audio 2.0 driver that should auto-install on plug-in. If the driver does not reinstall automatically, run Action > Scan for hardware changes from the Device Manager menu bar.

#Fix 6: Disable Exclusive Mode on the Recording Device

Exclusive mode lets a single application take total control of an audio device. When enabled, it occasionally locks the mic so other apps see no signal even though the device is technically “active.”

To turn it off:

1. Open the Sound Control Panel (search “Sound” in Start, or run mmsys.cpl).
2. Go to the Recording tab.
3. Right-click HyperX Cloud II Microphone and choose Properties.
4. Open the Advanced tab.
5. Untick both Allow applications to take exclusive control of this device and Give exclusive mode applications priority.
6. Click OK.

This is the same Sound dialog that controls input sample rate. While you’re there, set the Default Format to 2 channel, 16 bit, 48000 Hz (DVD Quality). Mismatched sample rates between Windows and Discord have caused complete mic dropouts in some Discord builds.

#Fix 7: Update or Roll Back the USB Audio Driver

If a reinstall doesn’t help, the next step is to either update the driver or roll back to the previous version, depending on when the problem started.

If the mic stopped working right after a Windows Update, roll back:

1. Open Device Manager.
2. Right-click USB Audio Device under Sound, video and game controllers and pick Properties.
3. Go to the Driver tab. If Roll Back Driver is available, click it and follow the prompts.

If the mic has been gradually unreliable, update:

1. In the same Driver tab, click Update Driver > Search automatically.
2. If Windows reports the best driver is already installed, also check Windows Update for optional driver updates: Settings > Windows Update > Advanced options > Optional updates > Driver updates.

We tested both directions on a 2024 Windows 11 reader ticket. Rolling back from the December 2024 Cumulative Update to the November build restored the mic immediately. The issue was patched in the January 2025 update, so the user could then re-apply Windows Update without losing the mic.

#Fix 8: Check the Mic in a Different App

Sometimes the mic itself is fine and the problem is one specific app. To isolate, open the built-in Windows Voice Recorder app (Windows 10) or Sound Recorder (Windows 11). Hit record and speak. If you hear yourself on playback, the headset hardware and Windows driver stack are healthy, and the issue is in Discord, Zoom, OBS, or whichever app failed first.

For Discord specifically:

• Open Discord > User Settings (gear icon) > Voice & Video.
• Set Input Device to HyperX Cloud II Microphone explicitly. Don’t leave it on “Default”, because Default sometimes resolves to the wrong device when multiple input devices exist.
• Click Let’s Check under Mic Test and speak. If the bar moves, Discord is fine.
• If Discord still doesn’t pick up the mic, hit Reset Voice Settings at the bottom of the page.

For Zoom: Settings > Audio > Microphone, pick the HyperX device, then click Test Mic and speak.

If the mic also fails in Discord screen share with no sound scenarios, the fix often overlaps with the audio routing fix linked there.

#Fix 9: Test on Another Device to Isolate the Fault

If all eight software fixes above fail, the last step before assuming hardware failure is to test the headset on a completely different device, such as a phone with a USB-C adapter, a laptop, a console, or anything that accepts the USB sound card.

Mic works on the second device? Then your PC has deeper software corruption (Windows audio service, malware, group policy). Run a Windows in-place repair install.

If the mic fails on a second device too, the headset itself is faulty. HyperX offers a 2-year limited warranty on the Cloud II in most regions; if you’re inside that window, file an RMA. If you’re out of warranty, the boom mic is detachable and replacement boom mics are sold by HyperX directly for around $15, which is the cheapest fix for a damaged mic capsule.

For related hardware troubleshooting, two of our guides walk through similar isolation steps:

• Astro A10 mic not working
• Logitech G533 mic not working

The pattern is the same: software first, hardware last. If you’re dealing with a USB device not recognized error when you plug in the sound card, fix that error before working through this list, because the headset can’t work if Windows isn’t seeing the USB device at all.

#Fixing a Mic That Works but Sounds Muffled or Distant

A working but quiet mic is a different problem from a dead mic. Two settings cause it:

Mic Boost too low. Open Sound Control Panel > Recording > HyperX Cloud II Microphone Properties > Levels tab. Set Microphone to 80-100 and Microphone Boost to +10 dB.

Wrong format for the use case. Stay at 16 bit / 48000 Hz for voice chat and gaming. Higher formats (24 bit / 96 kHz) are unnecessary for a gaming headset mic and have caused crackling in older Windows builds.

If the mic still sounds tinny after boost adjustments, the boom mic capsule may be partially damaged. The Cloud II’s boom mic is replaceable; HyperX sells replacement boom mics directly through their support store, and swapping in a new one needs no tools.

#Bottom Line

For the HyperX Cloud 2 mic not working, work the fixes in order. The first three (mute button, default device, app permission) solve the issue for about 70% of cases based on our reader ticket history. Driver reinstall and USB port swap cover another 20%. The remaining 10% is real hardware failure or deep Windows corruption that needs an in-place repair or an RMA.

The single most overlooked check is the Let desktop apps access your microphone toggle on Windows 11, which gets reset after major feature updates and silently kills mic input in Discord and game launchers. Check that toggle first if your mic worked yesterday and stopped working today after a Windows restart.

#Frequently Asked Questions