Fix a Thrustmaster joystick not detected on PC: check USB and mode settings, test Windows HID, reinstall drivers, update firmware and spot hardware faults.
A Thrustmaster joystick is usually not detected because of a bad or underpowered USB connection, the wrong hardware mode, an incomplete driver or firmware installation, a Windows HID conflict, or a cable or base fault. Connect it directly, select its PC-compatible mode, then use joy.cpl to see whether Windows recognises it.
For PC flight simulators generally, separate Windows detection from simulator configuration. If the stick works in Windows, the USB connection is established and the remaining problem is normally a controller profile, binding or remapping tool inside the simulator.
How do I get Windows to detect my Thrustmaster joystick?
The decisive test is whether Windows can see and read the joystick before any simulator starts.
- Disconnect the joystick and restart Windows. Use Restart rather than simply unplugging the device or shutting down, because this clears more of the existing USB state. Close simulators, Thrustmaster configuration software and controller-remapping tools.
- Check the hardware mode switch. If the base has PC and console-compatible modes, select the mode specified for PC before reconnecting it. Labels and required switch positions vary by model, so do not assume that another Thrustmaster stick uses the same setting.
- Inspect every physical connection. Seat any detachable grip, throttle lead and USB cable with the device unpowered. Look for bent connector pins, damaged cable insulation or a loose socket, and never force a keyed connector.
- Use a direct USB port. Bypass hubs, monitor ports, docks, extension leads, KVM switches and USB adaptors. On a desktop, try a rear motherboard port; if available, test both USB 2 and USB 3 ports because older controllers can behave differently between USB controllers.
- Open the Windows game-controller panel. Press
Windows key + R, enterjoy.cpland open the device's Properties page. Move every axis and press each button. Our full Windows-level joystick test covers the additional Device Manager and alternate-PC checks. - Watch Device Manager while reconnecting it. Check Human Interface Devices and Universal Serial Bus controllers. A new controller entry means Windows is enumerating the hardware;
Unknown USB Device,Device Descriptor Request Failedor Code 43 points to a lower-level USB, firmware or hardware problem. - Reinstall the exact Thrustmaster driver package if required. Disconnect the joystick, remove its existing Thrustmaster software through Windows Installed apps, restart, and install the package intended for that exact model. Connect the hardware only when the installer requests it. Avoid generic driver-updater utilities and similarly named packages for another base.
- Update firmware only through the model-specific procedure. Use a direct USB connection, close other controller software and prevent the PC from sleeping. Do not disconnect the joystick during an update. Bootloader and recovery button combinations differ between models, so do not improvise them.
- Test another computer. If a second PC also shows no connection response through a known-good direct port, the cable, USB socket or joystick electronics are the likely cause.
What does the Windows test result mean?
The result in joy.cpl or Device Manager identifies whether the fault is in the hardware connection or the flight simulator.
| Observed result | Likely cause | Next action |
|---|---|---|
| No USB sound and no Device Manager change | Dead port, damaged cable, wrong mode or failed joystick electronics | Try direct ports, recheck the mode switch and test another PC |
Device Descriptor Request Failed or Code 43 | USB enumeration, power, cable or firmware failure | Restart, change ports, remove hubs and follow the exact recovery procedure for the model |
Listed in joy.cpl, but no axes or buttons respond | Wrong mode, incomplete driver, firmware fault or internal hardware problem | Reinstall the correct package and test without remapping software |
Axes and buttons work in joy.cpl | Windows connection is working | Repair the simulator profile and control bindings |
| Connects and disconnects repeatedly | Loose cable, unstable USB power, power saving or failing socket | Use a direct port and check the cable and USB power settings |
Why does Windows detect the joystick but not my flight simulator?
If the Thrustmaster works in joy.cpl, reinstalling USB drivers is unlikely to fix the simulator.
- Create a fresh controller profile and bind the pitch, roll, yaw and throttle axes manually.
- Remove duplicate axis assignments from gamepads, throttles and other controllers; a mistake we see constantly is two devices commanding the same flight axis.
- Close TARGET scripts and other virtual-controller tools for a raw hardware test. When a profile creates a virtual device such as a combined controller, the simulator may need that virtual device selected instead of the physical stick.
- Disable per-game controller remapping such as Steam Input temporarily if it is replacing or masking the raw joystick.
- Calibrate only after Windows shows stable axis movement. Follow our PC joystick calibration and axis setup sequence rather than trying to compensate for a USB fault with sensitivity settings.
If the problem occurs only in Microsoft Flight Simulator, use the MSFS controller-profile and binding checks; they cover empty profiles, duplicate assignments and axes that the simulator has not mapped automatically.
Why does my Thrustmaster joystick keep disconnecting?
Repeated disconnects usually indicate an unstable USB path, cable movement, power management or a failing connector rather than bad calibration.
- Keep the joystick on a direct motherboard USB port and remove unpowered hubs or long extensions.
- Gently check whether movement near the cable or USB socket triggers the Windows disconnect sound. If it does, stop using that connection until the cable or socket is repaired.
- If the model includes an external power supply, confirm that the specified adaptor is connected securely.
- As a diagnostic test, open the relevant USB Root Hub properties in Device Manager and clear
Allow the computer to turn off this device to save powerwhere that option exists. USB selective suspend can also be disabled temporarily to establish whether sleep-related power management is responsible. - Do not attempt a firmware update while the connection is intermittent; losing power during the update can leave the device requiring its model-specific recovery procedure.
When is the Thrustmaster joystick probably faulty?
A hardware fault is likely when the joystick produces no USB response on multiple direct ports and another PC, despite using the correct hardware mode.
The same applies when Device Manager repeatedly reports a descriptor failure after a restart and model-specific driver installation, or when slight cable movement disconnects the controller. At that point, further simulator reinstalls and profile resets cannot help; the cable, USB socket, internal circuit board or detachable connector needs inspection, repair or replacement.