MSFS 2020 not recognising your Thrustmaster controller? Diagnose Windows detection, USB mode, drivers, profiles and axis bindings step by step.
Microsoft Flight Simulator 2020 usually fails to recognise a Thrustmaster controller because Windows has not detected it, the unit is in the wrong PC/console mode, or MSFS has loaded an empty profile. Test it in Windows first. If its axes respond there, repair the simulator profile rather than replacing the hardware.
How do I tell whether Windows or MSFS is the problem?
Run joy.cpl; it cleanly separates a Windows or hardware fault from an MSFS profile fault. Press Windows key + R, enter joy.cpl, select the Thrustmaster device and open its properties.
| Test result | Likely cause |
|---|---|
The controller is absent from joy.cpl | USB connection, platform selector, Windows driver, firmware or hardware fault |
| It appears, but no axes or buttons move | Incorrect mode, driver problem, failed calibration or hardware fault |
| It works in Windows but is absent from MSFS | Simulator restart required, remapping software conflict or device-detection problem |
| MSFS lists it but the aircraft does not respond | Blank preset, wrong device tab, missing bindings or duplicate assignments |
A yoke, throttle quadrant and rudder pedals may appear as separate devices. Test each entry rather than assuming that one Thrustmaster listing represents the complete setup. Our full Windows-to-MSFS controller checks cover the wider diagnostic sequence if no device appears at all.
How do I make MSFS 2020 detect the controller again?
- Reconnect it directly: close Microsoft Flight Simulator, remove any unpowered USB hub and connect the controller to a direct USB port. Try another port if necessary, and connect the hardware before launching MSFS.
- Check the platform selector: if the model has a PC/Xbox or PC/console switch, select PC mode before reconnecting it. A controller can receive power and illuminate while still presenting the wrong interface to Windows.
- Retest with
joy.cpl: confirm that every axis and button responds. If the device remains absent, install the official driver or firmware package intended for that exact model, restart Windows and test again. Do not use a package for a similarly named controller. - Stop virtual-controller software: close any remapping application before opening MSFS. A running Thrustmaster T.A.R.G.E.T. profile may replace the physical devices with a virtual Thrustmaster Combined device. Either bind that combined device or stop the profile and bind the physical units; switching between both arrangements leaves MSFS looking for hardware that is no longer exposed.
- Open Controls Options: find the Thrustmaster device in the device strip and select it. If several components are connected, inspect each one separately.
- Select or create a preset: choose the supplied default preset when one exists. If the selected preset is blank or damaged, create a fresh profile instead of deleting every cloud-synchronised control setting. We explain how to restore or switch an MSFS joystick profile without disturbing unrelated devices.
- Bind and save the axes: change the filter from assigned controls to all controls, use input search and move the required lever or axis. Assign yoke, stick, rudder and throttle movements to axis commands rather than digital increase/decrease commands, then use Apply & Save.
If the hardware is a TCA Boeing yoke or throttle quadrant, use our model-specific TCA Boeing troubleshooting for its Windows detection, USB and calibration checks.
Why is the Thrustmaster listed but not controlling the aircraft?
MSFS can list the correct device while loading a blank preset or assigning commands to another controller. A mistake we see constantly is configuring the highlighted keyboard, mouse or virtual device instead of the physical Thrustmaster tab.
- Use Search by input and move one control at a time. If MSFS detects the movement, recognition is working and only the binding needs attention.
- Remove duplicate primary-flight-control assignments from gamepads, throttles and other connected devices. Two devices commanding the same axis can cause jumping, centring or apparently ignored input.
- Bind analogue controls to commands containing Axis. Button-style left, right, increase or decrease commands are unsuitable for a joystick or yoke axis.
- Test with the autopilot and piloting assistance disengaged. If the cockpit control moves but the aircraft resists it, device recognition is no longer the problem.
Once inputs register, use the simulator's sensitivity screen to inspect the response curve and dead zone. Our guide to tuning joystick axes and removing binding conflicts covers that next stage.
Why does the controller disconnect during a flight?
Mid-flight drop-outs usually point to USB stability or Windows power management rather than an MSFS preset. Connect the controller directly, reseat any detachable lead and avoid an overloaded or unpowered hub.
In Windows Device Manager, inspect the relevant USB hub's power-management properties and disable permission for Windows to turn that hub off to save power. If the controller also disappears from joy.cpl after a drop-out, the fault is below the simulator level. Testing it on another USB port or PC helps distinguish a Windows installation problem from a failing cable or controller.
Does every Thrustmaster controller work with MSFS 2020 on Xbox?
No. On Xbox Series X|S, Microsoft Flight Simulator 2020 accepts only controllers designed and licensed for Xbox compatibility. A PC-only Thrustmaster device will not become Xbox-compatible through an MSFS profile or PC driver.
Xbox also lacks the Windows joy.cpl test, so check the model's stated platform support first. For a compatible unit, perform a full console restart, connect the controller directly and then inspect its device tile and preset in MSFS Controls Options.