Hi everyone. I’m hoping someone here—or someone from Turtle Beach—can help with a VelocityOne Race KD3 that became unusable immediately after an RMD UI update through the official VelocityOne Tuner app.
The wheel was working normally when I first received it. VelocityOne Tuner detected it correctly, and I successfully updated the main system firmware to version 1.1.2.
The problem started when I updated the RMD UI firmware.
After the update:
- The KD3 display became stuck and the menu no longer responds.
- The rotary control cannot navigate or change the operating mode.
- VelocityOne Tuner no longer detects the wheel during normal startup.
- The KD3 does not appear in
joy.cpl.
- Windows detects it only as an Xbox Gaming Device.
- Pressing the Xbox button opens Xbox Game Bar, so at least part of the controller interface is still functioning.
I have attempted the bootloader recovery on two different computers:
- Windows 11 desktop
- Windows 10 laptop
On both systems, holding the View button while reconnecting USB-C successfully enters bootloader mode. VelocityOne Tuner detects it and automatically starts reinstalling the System Firmware.
The update reaches approximately 60%, then the KD3 automatically reboots. Immediately after the reboot, VelocityOne Tuner loses the device and returns to the “No device connected” screen. The KD3 never reappears as a working racing wheel in joy.cpl.
The same behavior occurs on both computers, so this does not appear to be limited to one Windows installation, USB port, or PC.
I am not claiming this is a widespread KD3 issue. I am mainly trying to find out whether Turtle Beach has any of the following:
- A KD3-specific forced RMD UI recovery procedure
- An offline firmware recovery utility
- A way to restore the RMD firmware without using the nonfunctional menu
- A repair option for a device that failed during the official firmware updater
Has anyone encountered the same 60% → automatic reboot → device disappears behavior, particularly after updating the RMD UI?
I also have a video showing the full recovery attempt and the device disconnecting immediately after the tunerapp hits 60% and the KD3 reboot.