Description
Expected result
No command are working
headsetcontrol --capabilities
Found 1 supported device(s):
HyperX Cloud II Wireless (Kingston) (HyperX Cloud II Wireless) [0x0951:0x1718]
Capabilities:
* sidetone
* battery
* inactive time
headsetcontrol -b
Found 1 supported device(s):
HyperX Cloud II Wireless (Kingston) (HyperX Cloud II Wireless) [0x0951:0x1718]
Battery:
Status: BATTERY_UNAVAILABLE
Error: [battery] HID communication error
headsetcontrol -s 0
Found 1 supported device(s):
HyperX Cloud II Wireless (Kingston) (HyperX Cloud II Wireless) [0x0951:0x1718]
HID communication error
Ruled out software conflict
I fully uninstalled and purged HyperX NGENUITY (Store app, services, scheduled tasks, AppData/ProgramData folders, registry keys) to rule out a background process locking the HID handle. The error is byte-for-byte identical before and after the purge, so this does not appear to be a conflict with HyperX's own software.
Tried with and without CMD as admin.
Headset Name
HyperX Cloud II Wireless, Kingston-branded (pre-HP acquisition)
On which OS does the problem happen?
Windows
Device information
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col01#9&13cc65bc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0x000c Usage-ID: 0x0001
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col02#9&13cc65bc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0x000c Usage-ID: 0x0001
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col03#9&13cc65bc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0xff13 Usage-ID: 0x0001
Description
Expected result
No command are working
Ruled out software conflict
I fully uninstalled and purged HyperX NGENUITY (Store app, services, scheduled tasks, AppData/ProgramData folders, registry keys) to rule out a background process locking the HID handle. The error is byte-for-byte identical before and after the purge, so this does not appear to be a conflict with HyperX's own software.
Tried with and without CMD as admin.
Headset Name
HyperX Cloud II Wireless, Kingston-branded (pre-HP acquisition)
On which OS does the problem happen?
Windows
Device information
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col01#9&13cc65bc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0x000c Usage-ID: 0x0001
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col02#9&13cc65bc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0x000c Usage-ID: 0x0001
Device Found
VendorID: 0x0951
ProductID: 0x1718
Path: \?\HID#VID_0951&PID_1718&MI_03&Col03#9&13cc65bc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
Serial: 000000000001
Manufacturer: Kingston
Product: HyperX Cloud II Wireless
Interface: 3
Usage-Page: 0xff13 Usage-ID: 0x0001