Fix a Saitek yoke not recognised in Microsoft Flight Simulator with USB checks, driver repair, fresh profiles and correct axis bindings.
A Saitek yoke is usually not recognised in Microsoft Flight Simulator because Windows has lost the USB device, the simulator created an empty or incorrect control profile, or another input layer is intercepting it. Test it in Windows first, then reconnect it directly, repair the device entry, and rebuild its MSFS axis bindings.
This process applies to Microsoft Flight Simulator 2020 and 2024, although their Controls screens have different layouts. The Saitek Pro Flight Yoke may also appear under its later name, Logitech G Flight Yoke System.
How can I tell whether Windows or MSFS is at fault?
If the yoke does not respond in Windows Game Controllers, Microsoft Flight Simulator cannot detect it. Checking this first prevents the common mistake of reinstalling the simulator to fix a USB or hardware fault.
- Close Microsoft Flight Simulator. The simulator can miss a device connected after it has started.
- Connect the yoke directly. Remove extension cables and unpowered hubs, disconnect accessories attached to the yoke's built-in USB hub, and use a different USB port on the PC.
- Open the Windows controller test. Press Windows key and R, enter
joy.cpl, select the yoke and open its properties. Turn the yoke, push and pull it, and press several buttons. - Repair a failed device entry. If the yoke is absent or shown as an unknown USB device, remove only that matching entry in Device Manager, unplug the yoke, restart Windows and reconnect it. Do not remove every Human Interface Device, because that category also contains keyboards and mice.
- Test another computer if possible. A yoke that remains absent from
joy.cplon two computers probably has a cable, connector or internal electronics fault.
If Windows shows the yoke but its axes do not move, remove obsolete Saitek profiling software while testing and use only the driver package appropriate to the exact model and Windows edition. Our broader MSFS USB controller troubleshooting sequence covers detection conflicts affecting other yokes, pedals and joysticks as well.
| Symptom | Most likely cause |
|---|---|
Yoke missing from joy.cpl | USB connection, Windows device entry, driver or hardware |
| Working in Windows but absent from MSFS | Input-mapping layer, hot-plug detection or simulator profile |
| Visible in MSFS but aircraft does not respond | Empty, incorrect or conflicting assignments |
| Axes jump or the yoke disconnects | USB power, a poor cable connection or worn axis sensors |
How do I restore the Saitek yoke inside MSFS?
A yoke that works in joy.cpl but not in the aircraft normally needs a fresh MSFS control preset with analogue axes assigned correctly.
- Restart MSFS with the yoke connected. Open the Controls screen and select the device labelled Saitek, Logitech or, occasionally, a generic USB controller.
- Show all available commands. An Assigned-only filter can make an empty profile look as though the simulator has no yoke commands.
- Create a new preset. Do not overwrite a suspect profile until the replacement works.
- Bind the analogue controls. Assign the wheel to
Ailerons Axisand the push-pull movement toElevator Axis. Avoid the separate left, right, up and down commands, which are digital inputs intended for keys or buttons. - Assign the throttle quadrant. Bind each lever to the appropriate throttle, propeller or mixture axis for the aircraft being flown. A quadrant connected to the yoke by a round plug normally appears as part of the yoke, not as a separate USB controller.
- Save and test the preset. Check that the cockpit controls move through their full travel. Enable Reverse Axis only when a control moves in the wrong direction.
If Windows input works but MSFS still cannot see it, temporarily close controller-mapping utilities. For a Steam installation, disable Steam Input for the simulator while testing because it can wrap or hide specialist flight controls.
Corrupted presets and duplicate assignments can survive an ordinary restart. When the device appears but every new assignment behaves incorrectly, use our steps for clearing and rebuilding MSFS controller bindings rather than reinstalling the entire simulator.
Why does the yoke disconnect or produce jumping axes?
Intermittent detection usually points to USB power or hardware rather than an MSFS profile. Connect the yoke directly to the computer and avoid running pedals, panels and other demanding devices through the same unpowered hub.
- The optional power input on many Saitek yokes powers accessories connected to the yoke's built-in USB hub; the yoke itself normally receives its operating power through its main USB cable.
- If disconnects happen after the PC has been idle, test with USB selective suspend disabled or prevent Windows from turning off the relevant USB hub to save power.
- If the device remains connected but an axis flickers, reset or calibrate it through Windows Game Controllers, then apply only a small MSFS dead zone if needed.
- A dead zone can hide minor centre jitter. It cannot repair full-scale spikes, repeated USB disconnects or a physically damaged cable.
Also remove duplicate aileron and elevator axes from gamepads, joysticks and unused profiles. Conflicting axes often make a correctly recognised yoke seem unresponsive because two devices are continuously sending opposing inputs.
Does the Saitek yoke work with MSFS on Xbox or PlayStation?
The standard Saitek Pro Flight Yoke and Logitech G Flight Yoke System are Windows PC peripherals, not native Xbox or PlayStation controllers. Running Microsoft Flight Simulator on a console does not make a PC-only USB yoke compatible; console users need hardware explicitly approved for that platform.