Why is FS2004 not working on Windows 11 or 10?

Microsoft Flight Simulator 2004 can run on Windows 10 and Windows 11. When FS2004 installs but will not open, the usual cause is its blocked legacy disc check, a protected Program Files installation, a damaged fs9.cfg, or an old add-on—not modern hardware itself.

Does Flight Simulator 2004 run on Windows 11 and Windows 10?

Yes—FS2004’s 32-bit simulator engine can run under both Windows 10 and Windows 11, although these operating systems were released long after official support ended.

The two versions of Windows present much the same trouble spots: unsupported disc authentication, User Account Control, file redirection and add-ons written for an XP-era installation. Compatibility mode sometimes helps with display or permission faults, but it cannot restore a disc-check driver that Windows no longer supports.

If you have not installed the simulator yet, follow our complete FS2004 installation sequence for Windows 11; the same folder and clean-install principles also apply to Windows 10.

Which FS2004 failure do you have?

The point at which FS2004 fails usually identifies the right fix faster than reinstalling or changing every compatibility option.

How do I fix FS2004 on a modern PC?

The safest repair is a clean, patched installation tested before any aircraft, scenery or utilities are added.

1. Run setup directly from the installation media. If the old autorun menu does nothing, open the disc in File Explorer and start its setup executable. Use administrator rights for the installer only if Windows blocks normal installation.
2. Install outside protected folders. Use a simple location such as C:\FS2004 rather than Program Files. This avoids many write-permission and VirtualStore problems with FS2004 and its older add-on installers.
3. Keep the new installation clean. Do not immediately copy an old Aircraft, Gauges, Modules or scenery folder over it. Doing so can put the original fault straight back.
4. Apply the final official update. Install the official FS2004 v9.1 update package before using add-ons or a version-specific executable. The update fixes simulator faults and is expected by many later FS2004 add-ons, but it does not remove the original disc check.
5. Separate disc authentication from other faults. If the boxed edition installs but fails before reaching the menu, use the guidance in the next section. Graphics settings and a new configuration file will not repair a blocked media check.
6. Reset the configuration when the splash screen fails. Rename %APPDATA%\Microsoft\FS9\fs9.cfg to fs9.cfg.old. FS2004 should generate a clean file at its next successful start.
7. Test only default content. Load a default aircraft at a default airport. Once that works, add aircraft, scenery and utilities back individually rather than in one large batch.
8. Apply compatibility options one at a time. Try a normal launch first, administrator mode only as a diagnostic, and an older compatibility mode only if a specific problem remains. Stacking several options makes the result difficult to interpret.

Why does boxed FS2004 install but not launch?

The original boxed release can install successfully and then fail because Windows 10 and Windows 11 do not support the legacy SafeDisc driver used for its disc authentication.

This commonly produces no useful error: fs9.exe may appear briefly in Task Manager and then disappear, or the simulator may keep asking for valid media. Reinstalling graphics drivers, changing resolution or running compatibility mode cannot restore that blocked driver.

For a lawfully owned installation already updated to v9.1, use a version-matched v9.1 no-CD replacement where local law permits. This is an unofficial modified executable, not part of Microsoft’s v9.1 update.

• Back up the original fs9.exe before replacing it.
• Match the replacement to the installed simulator version; do not mix an original-release executable with an updated v9.1 installation.
• Keep Windows Security enabled. Modified executables can trigger warnings, so check the protection history rather than disabling antivirus protection wholesale.
• Do not download or attempt to re-enable an abandoned secdrv.sys driver from an unknown source.

It still doesn’t open after installation—what next?

If FS2004 still does not open after a clean installation, diagnose the exact launch stage with no add-ons present and only one change between attempts.

Nothing happens when you start fs9.exe

When no window or splash screen appears, the boxed edition’s disc check is the leading suspect.

Look in Task Manager for a stranded fs9.exe process and end it before trying again. Check Windows Security’s protection history as well, particularly if an executable was replaced or quarantined. If no fs9.cfg has ever been created, the simulator probably has not progressed far enough for configuration or graphics settings to be the cause.

The splash screen appears and then closes

A splash-screen exit usually points to the configuration, startup flight or a DLL-style add-on loaded during startup.

Type %APPDATA%\Microsoft\FS9 into File Explorer’s address bar and rename fs9.cfg; do not delete it until the replacement has been tested. If that does not work, inspect Windows Reliability Monitor for the faulting module. A named third-party .dll or .gau file is a strong lead, while fs9.exe alone does not identify the underlying cause.

Why do FS2004 settings or scenery changes not stick?

Settings that appear to save but later vanish usually mean Windows is redirecting files from a protected installation folder.

Look under %LOCALAPPDATA%\VirtualStore for another copy of files from the FS2004 installation path. A mistake we see constantly is editing the visible file under Program Files while the simulator is using a redirected copy elsewhere. Reinstalling into C:\FS2004 is cleaner than trying to maintain both locations.

If FS2004 can launch but cannot save flights or other user files, also check whether Windows controlled-folder protection blocked the write. Allow only a verified executable rather than turning the protection off globally.

Why does FS2004 show a black screen or crash in fullscreen?

A black screen or fullscreen crash is normally a display-compatibility fault rather than insufficient or excessively powerful hardware.

• Reset fs9.cfg before carrying old display settings into the new installation.
• If the menu is accessible, use Alt+Enter to compare windowed and fullscreen operation.
• Remove anti-aliasing, anisotropic filtering and frame-rate overrides forced through the graphics driver until the base simulator is stable.
• Disable recording overlays, monitoring tools and other software that hooks into 3D applications.
• If only fullscreen fails, test Windows’ fullscreen-optimisation compatibility option for fs9.exe. Change no other setting during that test.

Why did FS2004 stop working after an add-on?

If a default installation works and the fault begins after adding content, treat the newest aircraft, panel, gauge, module or scenery package as the cause until it is ruled out.

Some old add-on installers are themselves incompatible with 64-bit Windows even though their aircraft or scenery files can still work in FS2004. Use a documented manual installation when one is supplied; do not guess where shared gauges and modules belong.

Reintroduce one package at a time and launch the simulator between changes. Do not copy an entire old Gauges or Modules folder into a clean installation, because obsolete shared files can break unrelated aircraft. Once the default simulator is stable, our curated FS2004 aircraft, scenery and utility library provides content you can add in controlled stages.