Why is FSX not working on Windows 10 or 11?

Yes. Microsoft Flight Simulator X (FSX), including boxed Standard, Deluxe and Gold editions and FSX: Steam Edition, can run on Windows 10 and Windows 11. Failures usually come from a corrupt configuration, missing legacy components, permissions, incompatible add-ons, bad scenery paths or mixed installations, rather than Windows 11 itself.

Does FSX work on Windows 11 and Windows 10?

FSX works on both operating systems, but it is an older 32-bit simulator that depends on components and installation practices from an earlier Windows generation. The simulator itself may run correctly while an old aircraft gauge, weather utility or scenery installer does not.

For boxed FSX, follow the correct service-pack and Acceleration installation order. Applying the wrong update to the wrong edition can leave fsx.exe unable to start.

What does the FSX failure tell you?

The stage at which FSX stops is the best starting point for diagnosis.

How do you fix FSX on Windows 10 or 11?

Apply one fix at a time, then test a default aircraft at a default airport with fair weather and no external utilities. Changing several settings together makes the real cause almost impossible to identify.

1. Confirm the edition and executable. Remove obsolete shortcuts and start the edition you actually installed. Launch Steam Edition from the Steam library while Steam is running. Never copy core files between boxed FSX and FSX: Steam Edition; old add-on installers frequently target the wrong folder when both editions have existed on the same computer.
2. Reset fsx.cfg. Close FSX and Steam. Boxed FSX normally stores the file under %APPDATA%\Microsoft\FSX; Steam Edition may use FSX or FSX-SE, depending on the installation history. Rename fsx.cfg to fsx.cfg.old and restart FSX so it creates a clean configuration. If extensions are hidden, the file may appear simply as fsx. Our FSX.cfg location and reset instructions cover both editions.
3. Repair the core files. For Steam Edition, run Steam’s file-integrity verification. It restores missing or changed default files but does not necessarily remove third-party files left in the FSX directory. For boxed FSX, use the original media’s repair option if available, then restore the updates appropriate to that edition.
4. Restore the supplied legacy components. Windows 10 and 11 can have a newer DirectX version without every optional DirectX 9 file used by FSX and its add-ons. Rerun the prerequisite installers supplied with FSX or the affected add-on. Because FSX is 32-bit, a 32-bit module needs its corresponding x86 runtime even on 64-bit Windows. Never download a loose d3dx9_*.dll or other DLL from an unknown source.
5. Disable startup modules. In the active FSX configuration folder, temporarily rename dll.xml and exe.xml if they exist. If FSX then opens, a module or external utility listed in one of those files is responsible. Restore the files and isolate the entries rather than leaving every add-on disabled.
6. Test without third-party aircraft and scenery. If a default flight works but one aircraft or airport fails, Windows is not the primary problem. Check that product’s gauges, scenery dependencies and FSX edition compatibility. A splash-screen hang often follows the removal of a drive containing scenery; reconnect the drive long enough to remove or correct the Scenery Library entry.
7. Check permissions without making them permanent. Run FSX as administrator once as a diagnostic and review Windows Security for quarantined gauges or blocked folder access. For Steam Edition, Steam and FSX should normally run at the same privilege level. Running FSX as administrator while Steam remains unelevated can itself prevent launching.
8. Return to a plain graphics setup. Remove third-party graphics wrappers or injectors temporarily, regenerate fsx.cfg and disable Preview DirectX 10 if the menu is black or textures are corrupt. If FSX opens, use windowed mode while testing; Alt+Enter switches between windowed and full-screen modes.
9. Read the recorded crash rather than guessing. Windows Reliability Monitor or Event Viewer may name the faulting module. An aircraft gauge or add-on DLL gives you a useful suspect. A generic module such as ntdll.dll or KERNELBASE.dll often records the final crash without being the underlying cause, so do not replace Windows system DLLs.

If Steam Edition still closes before its menu appears, use our focused Steam startup checks for file verification, configuration, scenery and permissions.

Why does FSX keep crashing on Windows 11?

Repeated FSX crashes on Windows 11 are usually caused by the loaded flight or add-ons, not a blanket incompatibility with Windows 11.

Memory-related crashes are made worse by high-resolution aircraft, dense scenery, large texture sets, AI traffic and long sessions. Lowering a single display slider may not be enough; reduce the combination of aircraft, scenery and traffic loading. Our repeated-crash diagnostic process explains how to separate memory exhaustion from aircraft, scenery and gauge faults.

Should FSX use compatibility mode or administrator mode?

FSX should first be tested with no compatibility options selected, because both boxed FSX and Steam Edition often run normally without them.

For boxed FSX, running the installer as administrator can help when setup cannot write to a protected location. Compatibility mode on fsx.exe is reasonable only after configuration, update and add-on checks fail, and it should be retained only when it fixes a repeatable problem.

A mistake we see constantly is enabling Windows XP compatibility, administrator mode, reduced colour options and disabled full-screen optimisation at the same time. Clear inherited settings first, then test one change at a time. Steam and FSX should use matching permission levels.

What if the Windows flight fix was not successful and nothing changes?

There is no universal Windows flight fix: if a change was not successful and nothing changes, undo it before moving on. No effect often means you edited the inactive edition’s files, used the wrong AppData folder or tested through an old shortcut.

Try FSX from a separate Windows user account before reinstalling. If it works there, the core installation is usable and the fault lies in the original profile’s AppData configuration, saved files or folder permissions. If it fails identically, concentrate on the program files, prerequisites, activation and machine-wide modules.

When should you reinstall FSX?

Reinstall only when repair, a clean configuration and add-on isolation all fail, or when boxed and Steam files have become mixed. An ordinary uninstall can leave the exact files that caused the problem, especially third-party gauges and modules.

1. Back up only personal material you recognise. Preserve saved flights, controller settings, flight plans and original add-on installers. Do not plan to restore an old configuration wholesale.
2. Uninstall the failed edition. After uninstalling, rename any remaining FSX program folder and the active FSX or FSX-SE AppData folder. Renaming is safer than immediate deletion because it preserves files you may need later.
3. Install one edition cleanly. Keep boxed FSX and Steam Edition separate. Apply only the updates belonging to that edition and complete boxed activation when prompted.
4. Test an entirely default flight. Do this before copying aircraft, scenery, gauges, weather software or an old fsx.cfg back into the installation.
5. Restore add-ons individually. Test after each aircraft, scenery package or startup utility. Copying old Gauges, Modules or configuration folders back in one batch commonly recreates the original failure.