The following explains how to resolve an issue where HyperX Cloud III headsets randomly disconnect or stop working on some client PCs. The headset can be restored by restarting its USB device through a PowerShell script, which can be configured to run automatically during client startup using CCBoot.

  1. On some PCs, HyperX Cloud III USB headsets are not detected or do not function correctly after Windows starts or when users connect them.
  2. The headset starts working normally only after physically unplugging and reconnecting the USB cable.

Solution

  1. A PowerShell script has been created to automatically:
  2. Search for the HyperX Cloud III USB device using its hardware ID.
  3. Disable the device.
  4. Wait 2 seconds.
  5. Re-enable the device.

[Save the following code as restart_hyperx.ps1:]

—-----------------------------------------------------------------------------------------------------

# Define the device ID

$DeviceID = 'USB\VID_03F0&PID_089D&MI_00*'

# Find the device

$device = Get-PnpDevice | Where-Object {

    $_.InstanceId -like $DeviceID

}

if ($device) {

    Write-Host "Device found: $($device.FriendlyName). Restarting..." -ForegroundColor Cyan

    # Disable the device

    $device | Disable-PnpDevice -Confirm:$false

    Start-Sleep -Seconds 2

    # Enable the device

    $device | Enable-PnpDevice -Confirm:$false

    Write-Host "Device successfully restarted." -ForegroundColor Green

}

else {

    Write-Host "Error: Device with this ID is not connected." -ForegroundColor Red

}

—----------------------------------------------------------------------------------------------------

  1. Open super client and add the restart_hyperx.ps1 in the Windows image:
    C:\Scripts\restart_hyperx.ps1
  2. Close super client and save changes.
  3. Open the CCBoot Control Panel.
  4. Navigate to Boot - Settings.
  5. Locate Run batch command at client.
  6. Enter the following command:
  7. powershell.exe -NoProfile -ExecutionPolicy Bypass -File "C:\Scripts\restart_hyperx.ps1"

Hyperx Cloud 3 reconnect issue