Why won't FS2004 start on a modern PC?

FS2004 usually will not start on a modern PC because its original disc protection is blocked, FS9.cfg is corrupt, Windows is denying writes, or an old add-on DLL is crashing at launch. Identify whether it fails before the splash screen, at the splash screen, or when loading a flight, then apply the matching fix below.

What does FS2004 do when you launch it?

The point at which Microsoft Flight Simulator 2004 stops is the best diagnostic clue.

How do I fix FS2004 not opening?

1. Check whether this is the original disc-launch problem. Retail FS2004 editions can rely on SafeDisc-era copy protection that modern 64-bit Windows versions no longer support. Installation may complete successfully even though fs9.exe cannot pass its launch check. The FS9.1 update does not by itself restore that obsolete driver.

   Compatibility mode cannot re-enable blocked disc protection. Do not install an old secdrv.sys driver or download an unverified replacement executable; use a legitimately supplied Windows-compatible executable if your licensed edition includes one, or retain an older offline Windows environment that supports the original disc release.

2. Install outside Program Files. FS2004 and many of its add-ons expect to write inside the simulator directory. Windows security can block or redirect those writes when FS9 is under Program Files or Program Files (x86).

   For a clean installation, a simple writable folder such as C:\FS2004 avoids many permission and VirtualStore problems. Do not drag an existing installation to a new location because registry entries, scenery paths and add-on installers may still point to the old folder. Follow our clean FS2004 installation procedure for Windows 11 when setup or first launch is also failing.

3. Apply the FS9.1 update to a clean installation. Patch FS2004 before replacing core files or loading it with add-ons. If the updater reports unexpected or modified files, restore the originals rather than forcing the update. Our FS2004 patch-order and version-check instructions cover the correct sequence.
4. Rebuild FS9.cfg. Press Windows+R, enter %APPDATA%\Microsoft\FS9, and rename FS9.cfg to FS9.cfg.old. FS2004 should create a fresh file at the next successful launch.

   This resets graphics options, display detection and control assignments, so keep the old file until the simulator is stable. If no new file appears, FS9 is failing before configuration initialisation or Windows is blocking access to the profile folder.

5. Remove only recently added files. Startup modules in the Modules folder are frequent causes of a splash-screen crash, while old gauges, aircraft panels and scenery can fail later during flight loading. Move the specific third-party files installed immediately before the problem; do not rename or empty entire default folders.

   If you no longer know which files belong to an add-on, compare them with a clean backup or reinstall FS2004 rather than deleting DLLs at random. Our FS2004 add-on folder guide explains where aircraft, gauges, effects, modules and scenery are normally placed.

6. Test Windows compatibility settings one at a time. Begin with no compatibility settings. If FS9 still fails after the configuration and add-ons have been checked, test Windows XP Service Pack 3 compatibility mode, followed separately by one launch as administrator.

   Use administrator mode as a diagnostic step, not as the automatic cure. If it works only as administrator, reinstalling into a writable folder is cleaner than permanently granting elevated access. For a black screen, also test Disable fullscreen optimisations and switch to windowed mode with Alt+Enter if the simulator remains open long enough.

7. Check Windows Security and required runtimes. Review Protection History to see whether fs9.exe or an add-on DLL was quarantined. Restore a file only when its source and integrity are known. If an error identifies a missing DirectX or Visual C++ component, install the relevant official Microsoft legacy runtime rather than copying an individual DLL from a download archive.

Why does the FS2004 splash screen appear and disappear?

A disappearing splash screen usually means FS9 has started but crashed while reading its configuration, scenery database or startup modules. Reset FS9.cfg first, then reverse the most recent module or scenery installation.

Windows Event Viewer can narrow this down. Open Windows Logs, select Application, and inspect the error recorded at the launch time. A named third-party DLL points towards that add-on; ntdll.dll is a generic crash location and does not prove that Windows itself is damaged.

If FS2004 stops while building its scenery database, restore the previous scenery configuration and verify that every enabled area still exists at its recorded path. Network drives, external disks and renamed add-on folders can leave entries pointing to unavailable files.

When should I reinstall FS2004?

Reinstall when core files have been overwritten, the FS9.1 updater cannot recognise the installation, or add-on files can no longer be separated from the defaults. Preserve personal flights and original add-on packages, uninstall FS9, rename any remaining simulator folder, and install a clean copy outside protected Windows directories.

Launch and patch the clean simulator before adding anything. Restore add-ons in small groups and test after each group; copying the entire old installation back at once also restores the fault.

What if FS2004 starts but crashes during flights?

A simulator that reaches the menus and flies briefly has a different fault from one that will not launch. Heat, memory pressure, AI traffic, scenery boundaries and incompatible gauges become more likely; use our diagnostic steps for random FS2004 crashes rather than repeatedly reinstalling the base simulator.