Fix a Logitech or Saitek yoke not recognised in Microsoft Flight Simulator with targeted USB, driver, profile and axis-binding checks.
A Logitech/Saitek yoke usually goes unrecognised in Microsoft Flight Simulator because Windows has not enumerated it correctly, the USB connection is unstable, its MSFS control profile is empty, or another controller is interfering. Test the yoke in Windows first; then repair the USB connection or rebuild its MSFS bindings.
How do I tell whether Windows or MSFS is the problem?
Windows must recognise the yoke and receive its inputs before Microsoft Flight Simulator can use it. Press Windows key + R, enter joy.cpl, select the yoke and open its properties. Older units may appear under a Saitek name even when newer software uses Logitech branding.
Move the yoke through pitch and roll, operate its buttons and move the throttle quadrant levers. Our Windows joystick test procedure explains what each result means and separates a USB or hardware fault from an MSFS configuration problem.
| Test result | Likely cause | Next action |
|---|---|---|
Yoke is absent from joy.cpl | USB, power, driver or hardware problem | Repair Windows detection before changing MSFS |
| Yoke appears and every input responds | MSFS profile, binding or controller conflict | Create or repair the yoke preset in MSFS |
| Yoke appears but axes do not move | Driver, calibration or hardware fault | Reinstall the correct driver, calibrate and retest |
| Yoke disconnects during use | Weak hub, USB power saving or damaged connection | Use a direct port and disable power saving for that connection |
Fix Windows USB detection first
- Close Microsoft Flight Simulator. Disconnect the yoke and temporarily unplug other flight controllers, USB hubs and devices attached to any hub built into the yoke.
- Connect the yoke directly. Use a rear motherboard USB port on a desktop PC where possible, without an extension lead or unpowered hub. Trying a different USB generation can help older Saitek hardware, but moving repeatedly between ports before Windows finishes detection can create duplicate device entries.
- Retest with
joy.cpl. If the yoke now appears and responds, leave it connected and restart MSFS. Hot-plug detection is not always reliable after the simulator has opened. - Inspect Device Manager. Look for the named yoke or an unknown USB device with a warning symbol. If that entry clearly belongs to the yoke, uninstall that device entry, disconnect the yoke, restart Windows and reconnect it. Do not remove USB host controllers at random.
- Repair the model-specific driver. Install or reinstall the appropriate Logitech or Saitek Windows driver if the device remains unidentified or its axes do not report. Avoid stacking an older Saitek package, a newer Logitech package and third-party controller drivers for the same device.
- Check USB power management. If the yoke works initially and then vanishes, disable the option allowing Windows to turn off the relevant USB hub to save power. Where available, temporarily disabling USB selective suspend is also a useful diagnostic test.
Reinstalling the entire simulator cannot fix a yoke that is missing from joy.cpl; MSFS is not involved at that stage.
Do I need Logitech software for the yoke?
Not in every case, but Windows must expose the yoke as a working game controller. Software intended for separate switch, radio or instrument panels does not make the yoke's pitch and roll axes work. Use the yoke's proper Windows driver when required, then disable controller remappers and virtual joystick tools temporarily while testing for conflicts.
What if MSFS sees the yoke but no controls work?
If the yoke works in joy.cpl, repair its Microsoft Flight Simulator control preset rather than its driver. The MSFS 2020 and MSFS 2024 control screens look different, but the same checks apply.
- Select the yoke itself on the Controls screen. Do not edit the keyboard, mouse or gamepad preset by mistake.
- Show all commands rather than only assigned controls. An empty search result can simply mean the active filter is hiding unassigned commands.
- Create a fresh custom preset if the default profile is blank, read-only or behaves unpredictably. Check that the intended preset is active, including any aircraft-specific preset used by the simulator.
- Bind continuous axes. Assign the roll movement to
Ailerons Axisand pitch toElevator Axis, or the equivalent entries containing the wordAxis. Do not use digital commands such as aileron left/right or elevator up/down for an analogue yoke. - Remove duplicate assignments. Clear pitch and roll axes from unused gamepads, joysticks and virtual controllers. Two devices commanding the same axis can cause twitching, recentering or apparently dead controls.
- Save and test in a simple aircraft. Use a default light aircraft with the autopilot and AI piloting disabled. Check the cockpit yoke or external control surfaces before adding other peripherals back one at a time.
For the complete binding sequence, see our guide to creating and testing an MSFS yoke profile. If the preset remains blank or corrupted, use the simulator's own profile tools first; our instructions for clearing conflicting controller bindings safely cover the next step without deleting unrelated simulator data.
Calibration is separate from detection. Use Windows calibration when the full physical travel is not reported in joy.cpl; use MSFS sensitivity and dead-zone settings when Windows reports the axis correctly but the aircraft feels too abrupt, drifts or reaches full deflection too early. Our calibration and sensitivity checklist explains which adjustment belongs in each place.
Why is the throttle quadrant missing?
A quadrant supplied with some Logitech/Saitek yokes connects to the yoke base and may appear as extra axes under the same Windows device, not as a separate MSFS controller. A standalone USB quadrant normally appears separately. Check its connector before powering the yoke, then look for throttle, propeller and mixture movement in joy.cpl.
When to suspect a yoke hardware fault
Treat hardware as the likely cause when the yoke fails to appear in joy.cpl through several direct USB ports and on a second Windows PC. Intermittent disconnection when the cable moves, buttons that vanish together, or an axis permanently stuck at one value after recalibration also points to a physical fault rather than an MSFS setting.
If Windows receives every movement correctly but a particular aircraft ignores it, the yoke hardware is working. Recheck the active aircraft profile, duplicate bindings, assistance settings and autopilot state instead.
Console compatibility
These troubleshooting steps apply to Windows PC. Xbox and PlayStation do not accept arbitrary PC flight controllers, and installing a Windows driver is not possible there. The common PC Logitech/Saitek yoke will not become console-compatible through an MSFS binding change; console users need a yoke explicitly supported on their particular console.