Why is FSX not working on Windows 10 or 11?

Flight Simulator X can run on Windows 10 and Windows 11, but it often fails because of a damaged configuration, missing legacy DirectX components, blocked file access, incompatible add-ons, a mixed boxed/Steam installation, or activation trouble. The right fix depends on whether FSX will not launch, crashes, or loads incorrectly.

Does FSX work on Windows 10 and Windows 11?

Yes, both boxed FSX and FSX: Steam Edition can work on Windows 10 and Windows 11. FSX was designed for an older Windows generation, however, and remains a 32-bit simulator using legacy components that modern Windows does not always configure cleanly.

FSX: Steam Edition is usually easier to repair because Steam can verify its files. Boxed Standard, Deluxe and Gold editions rely on older installers and product activation, so installation permissions and licensing faults are more common. Our FSX hardware and Windows compatibility notes explain the practical differences in more detail.

What does your FSX symptom tell you?

The point at which FSX stops working usually identifies the fault more reliably than changing random compatibility settings.

How do you fix FSX on Windows 10 or 11?

Work through these fixes in order and test a default aircraft at a default airport after each material change.

1. Confirm which FSX edition you are launching. Start Steam Edition through Steam and boxed FSX from its own installation. Old desktop shortcuts often point to an abandoned copy of fsx.exe. Do not combine files from boxed and Steam installations.
2. Reset the FSX configuration. Close FSX and Steam, open %APPDATA%\Microsoft\, and look for a folder named FSX or FSX-SE. Rename fsx.cfg to fsx.cfg.old, then start the simulator so it creates a clean file. If Windows hides extensions, the file may appear simply as fsx. Keep the old file until the test is complete.
3. Repair the core installation. For Steam Edition, use Steam's file-integrity verification command. For boxed FSX, run the repair option from the original installation media. Steam verification can restore modified default files, but it does not necessarily remove third-party files left in the FSX directory.
4. Restore the legacy prerequisites. Windows may include a newer DirectX version without every optional DirectX 9 library expected by FSX or its add-ons. Rerun the prerequisite installers supplied with FSX, or let Steam repair them. Never solve a missing-DLL error by downloading an individual DLL from an unknown source.
5. Disable external modules temporarily. In the same configuration folder, rename dll.xml and exe.xml if present. If FSX then opens, restore the files one at a time to identify the module responsible. Old installers, gauges and DLL modules require particular care; our guide to resolving FSX add-on compatibility and path problems covers those failures.
6. Check scenery paths and disconnected drives. A splash-screen hang often follows the removal of a drive containing add-on scenery. Reconnect that drive or disable the affected scenery entry. Network locations that no longer exist can produce the same delay.
7. Test Windows security and folder access. Run FSX as administrator once as a diagnostic, then check whether antivirus protection quarantined a gauge or blocked changes in the FSX and AppData folders. A permanent administrator setting is not the preferred fix, especially for Steam Edition.
8. Reset the display mode. Try windowed mode, regenerate fsx.cfg, and turn off Preview DirectX 10 if FSX opens with a black screen or corrupt textures. Remove graphics injectors or replacement DirectX DLLs while testing.
9. Inspect the faulting module. Windows Reliability Monitor or Event Viewer may identify the DLL loaded immediately before a crash. A named add-on gauge or module is actionable; a generic Windows component such as ntdll.dll often records the crash without being its root cause.

If FSX starts but crashes only during demanding flights, treat that as a stability or 32-bit memory problem rather than a Windows compatibility failure. Use our full FSX crash diagnostic process for aircraft, scenery, gauges and memory-related failures.

Should FSX use compatibility mode or administrator mode?

Compatibility mode should be a targeted test, not the first fix applied to every FSX installation. FSX and FSX: Steam Edition often run normally with no compatibility options selected.

For boxed FSX, running the installer as administrator can solve failures caused by protected folders. If the installed simulator still refuses to launch after configuration and add-on tests, try a Windows compatibility mode on fsx.exe and keep it only if it resolves a repeatable fault.

For Steam Edition, forcing administrator mode on FSX while Steam runs with ordinary permissions can create a privilege mismatch. Clear inherited compatibility settings first, then test Steam and FSX at the same permission level.

An out of date license message is a separate licensing problem rather than proof that FSX cannot run on Windows 11. Follow the boxed and Steam-specific Windows 11 licence fixes instead of repeatedly reinstalling the simulator.

When should you reinstall FSX?

Reinstall FSX only after configuration resets, file repair and add-on isolation fail, or when boxed and Steam files have become mixed across the same folders.

1. Back up personal content. Preserve saved flights, controller profiles and add-ons you can identify, but do not plan to restore every old file blindly.
2. Remove the failed installation. After uninstalling, rename any remaining FSX program and AppData configuration folders so the next launch cannot reuse them.
3. Install one edition only. Complete all components belonging to that edition in their intended order, then launch a default flight before adding anything else.
4. Restore add-ons individually. Test after each aircraft, scenery package or module. Copying an old Gauges, Modules or configuration folder wholesale commonly recreates the original failure.