Logitech Extreme 3D (non-Pro) not working in MSFS 2020 on Windows 11

Extreme 3D (non‑Pro) + Windows 11 + MSFS: “clean slate” checklist (no BIOS rabbit holes)

Most of the time with older Logitech sticks on Win11, the issue isn’t MSFS “support” so much as Windows ending up with messy/duplicate HID entries, or MSFS holding onto a broken/blank control profile. The goal is to prove the stick works at the Windows level first, then force MSFS to build a fresh mapping.

1) Confirm Windows sees it as a working game controller

1. Unplug the joystick.
2. Plug it directly into a rear motherboard USB port (no hub/front panel for the first test).
3. Open the old Game Controllers panel: search Windows for Set up USB game controllers.
4. Select the Logitech device (or “USB Game Controller”) -> Properties.
5. On the Test tab, verify:
   • X/Y move smoothly
   • Twist (rudder) moves smoothly
   • Throttle slider moves smoothly
   • Buttons light up when pressed

If it’s not clean here, MSFS can’t fix it. If it IS clean here, keep going.

2) Remove ghost/duplicate device entries (this fixes a lot of “dead in MSFS” reports)
After “driver hacks,” Windows often accumulates hidden copies of the same controller.

1. Unplug the joystick.
2. Open Device Manager.
3. In View, enable Show hidden devices.
4. Expand these sections and uninstall any greyed-out/duplicate entries that look like they belong to the stick:
   • Human Interface Devices
   • Sound, video and game controllers
   • Universal Serial Bus controllers
5. Reboot.
6. Plug the stick back into the same USB port and let Windows detect it again.

3) Calibrate in Windows (don’t skip this step)
Even when it “shows up,” bad calibration can make MSFS look like it’s ignoring input.

1. Back to Set up USB game controllers -> select the stick -> Properties.
2. If there’s a Settings tab with Calibrate, run the wizard fully.
3. Re-check movement on the Test tab afterward.

4) Force MSFS to create a fresh control profile
MSFS can latch onto a weird/empty mapping and never recover unless you create a new profile.

1. Start MSFS.
2. Go to Options -> Controls Options.
3. At the top, click your joystick device (make sure you’re not still on Keyboard/Mouse).
4. Set the filter to All so you can see everything MSFS thinks the device can do.
5. Create a New Profile for the stick (don’t keep fighting a broken default profile).
6. Bind only the basics first:
   • Ailerons Axis
   • Elevator Axis
   • Rudder Axis (twist)
   • Throttle Axis (slider)
7. Apply & Save, then test in a simple default aircraft on the runway.

5) If the axes are backwards / jumpy

• In each axis binding in MSFS, use the axis Reverse option if needed.
• For testing, set dead zones small (or zero) just to confirm you get consistent movement, then fine-tune later.

6) Quick sanity check if Windows sees it but MSFS doesn’t

1. Temporarily unplug/disable other controllers (Xbox pad, wheel, HOTAS, etc.).
2. Restart MSFS and check Controls Options again.

A few targeted questions (so we don’t guess)

1. In Set up USB game controllers -> Properties, do you get clean axis movement and button presses, yes/no?
2. In MSFS Controls Options, does the joystick appear as a device at the top at all, or is it missing entirely?
3. When you say “Windows 10 drivers installed,” what exactly did you install (name/version), or did you let Windows install it automatically?
4. Are you connected through a hub/front panel, or directly into the PC?

Answer those four and it’ll be pretty clear whether you’re dealing with (a) Windows/HID enumeration, or (b) MSFS profile/mapping getting stuck.