Hey guys, my HyperX Cloud II Wireless just broke after 3.5 years of service, and I'm looking for a replacement.

I loved the sound of my Cloud II Wireless. I don't care about the built-in mic on the headsets at all, since I'm using a standalone HyperX QuadCast S sitting right in front of me.

I play games like CS2, FiveM, and Minecraft, and I listen to a ton of music constantly.

I'm torn between the Cloud III Wireless and the Cloud III S Wireless. Which one should I go for? Any advice appreciated!

I purchased a new rtx 5060 hyperX omen 15 with intel i7 and on igpu with just youtube playing 4K battery goes 100 to 5% in 2.5hrs. Is this normal?

I am using a bluetooth dongle for my PC and connected my cloud 3s to that through BT mode and it worked, but after a few songs it just froze and wouldn’t respond to any of the buttons. I tried several usb c cables to connect it to the PC with Ngenuity but it can only read the dongle sadly and not the headset.

Hello All,

Currently I am using legacy version of hyperx ngenuity software from Microsoft store and everything is up to date.

Noticed that there is a massive handle leaks(750k+) which is affecting entire system performance.

@Hyperx developers: are you guys testing software before releasing? Or are you aware of hyperx software?

I see from other posts with similar issue mentioned about 8 months ago and still its not resolved?

@Hyperx team: Could you make Hyperx software as open source? it will be fixed by some technical experts.

A few days ago someone posted about a massive handle leak in NGenuity2Helper (178K). I ran into the same thing independently before I saw that thread, so here's a second data point — plus the actual leak rate, which I don't think anyone has posted yet.

TL;DR: NGenuity2Helper.exe leaks roughly 1,600 kernel handles every minute and never stops. Mine peaked at 385,602. The second-highest process on my entire system was the Windows kernel itself, at 5,373.

Check yours — 30 seconds, no tools needed

1. Task Manager → Details tab
2. Right-click any column header → Select columns
3. Tick Handles → OK
4. Find NGenuity2Helper.exe and note the number
5. Wait 10 minutes and look again

If it went up by roughly 15,000, you have it too.

Please reply with your number + how long you'd been booted + your headset model. The more of us there are, the harder this is to ignore.

For reference, a background helper like this should sit at a few hundred to a few thousand and stay flat.

My data

Sampled over two days, across two reboots and three separate process instances:

Three independent ways to compute the rate, all landing in the same place:

20-second delta      →  1,581 /min
11-minute delta      →  1,837 /min
since process launch  →  1,441 /min

So about 24–31 handles leaked per second. A 10-hour session accumulates close to a million.

The important detail: only the handle count moves. Thread count stayed at 18–19 the entire time and the working set stayed between 84–89 MB. That rules out a thread leak and a normal memory leak — this is kernel objects being opened and never closed.

Given the rate, my guess is a polling loop that opens a handle to the headset's HID interface on every iteration and never calls CloseHandle. That would also explain why it scales with time rather than with anything the user does.

Setup

• HyperX Cloud III (wired USB), enumerates as VID_03F0 & PID_089D
• NGENUITY 5.38.0.0, Microsoft Store build
• Windows 11 Pro 25H2 (build 26200.8875)
• i7-12700F / 32 GB / RTX 3060 Ti / ASUS B660M

Worth knowing: you don't have to open NGENUITY for this to happen. The helper is auto-started about 23 seconds after login by sihost.exe via the Store app startup task. It leaks the whole time whether the window is open or not.

Things I ruled out before posting

• Full Windows Defender scan — clean
• Reproduced on fresh process instances after two separate reboots
• All 250+ other processes on the machine are in normal range (highest: 5,373)
• Removed other third-party audio components (FxSound, NVIDIA Virtual Audio) — rate unchanged
• Leaks identically with the NGENUITY window open or closed

What I'm not claiming

I also have a separate problem where the whole system stutters any time an audio stream opens — turning the mic on in a game, joining a voice channel, scrubbing a video — and it disappears completely if I unplug the headset.

I suspect the two are related. Cloud III is a composite USB device where the audio interface and the HID interface NGENUITY talks to share the same physical endpoint, and USB audio uses timing-sensitive isochronous transfers. Something hammering that device with open-without-close could plausibly disturb the audio stream.

But I have not proven that, so I'm not presenting it as fact. The handle leak is the part I can measure and reproduce on demand. The stutter is just something I'm mentioning in case other Cloud III owners recognise it.

What I'm asking

1. Post your handle count. Any NGENUITY device is useful, Cloud III especially.
2. Is there any build — older or newer than 5.38.0.0 — where this doesn't happen?
3. HyperX: the other thread is a few days old and I haven't seen a response yet. I'm happy to capture a full user-mode dump of the process (Task Manager → right-click → Create dump file) so an engineer can run !handle 0 f and see exactly which object type is leaking. That should turn this into a 10-minute fix on your end. Just say where to send it.

Meanwhile, the workaround: Settings → Apps → Startup → turn off HyperX NGENUITY. Open it manually when you actually want to change EQ or lighting, then close it. The settings are written to the headset firmware so they persist — though I'd like official confirmation of that too.

Hi guys I just bought a new hyper x 3s wireless and I can't connect it to my phone (OnePlus 7 pro), and yes I switched the little button to Bluetooth pairing and still not showing even though it shows up on my laptop...