Why does FS2004 crash on startup, and how do I fix it?

FS2004 usually crashes on startup because its FS9.cfg is corrupt, the saved default flight loads a broken aircraft or gauge, or a recently installed module or scenery file fails during initialisation. Rename FS9.cfg first; if that fails, isolate third-party add-ons, then repair the simulator and check Windows compatibility.

What should I try first when FS2004 will not open?

Rebuilding FS9.cfg is the quickest safe test because it removes invalid display settings and restores the stock default flight without deleting aircraft or scenery.

1. Close FS2004 completely. Check Task Manager and end fs9.exe if it remains running in the background.
2. Open the FS9 settings folder. Press the Windows key and R, enter %APPDATA%\Microsoft\FS9, then press Enter.
3. Rename the configuration file. Change FS9.CFG to FS9.CFG.old. Renaming is safer than deleting because the original remains available.
4. Start FS2004 again. The simulator should create a clean configuration and load its stock default flight.
5. Keep the new file if FS2004 opens. Reconfigure graphics, sound and controls manually. Copying the entire old file back will usually restore the fault.

Our FS9.cfg location and safe rebuilding notes explain the configuration file in more detail. Leave the old file renamed while troubleshooting so every test uses the clean settings.

Where does FS2004 crash during startup?

The point at which FS2004 stops usually identifies the part that needs attention.

Windows Reliability Monitor can show the faulting module. A named third-party DLL is a useful lead; ntdll.dll or KERNELBASE.dll usually records where the crash ended, not what originally caused it.

If the message names PANEL.DLL, follow our panel and gauge fault procedure. PANEL.DLL is often only the component that encountered a defective or incompatible gauge.

How do I find the add-on causing the startup crash?

Remove third-party components in reverse installation order, testing FS2004 after each change. A mistake we see constantly is moving entire simulator folders and accidentally removing stock files along with the add-on.

1. Undo the newest change first. Remove the last aircraft, panel, scenery, weather utility or traffic package installed before the crashes began.
2. Quarantine automatic modules. Move only known third-party DLL files out of the Modules folder into a temporary folder outside FS2004. Do not remove files merely because their purpose is unfamiliar.
3. Test with stock content. Keep the fresh FS9.cfg and use the default aircraft and airport. If this works, the former saved flight, its aircraft or one of its gauges was involved.
4. Isolate scenery and traffic. Deactivate the latest scenery library entry or move only the files installed by that package. Third-party AI traffic BGL files can also fail while the scenery database is loading.
5. Restore items one at a time. Restart FS2004 after each restored component. Restoring a whole collection at once hides which file is responsible.

Do not download individual replacement DLL files from miscellaneous sources. If an add-on needs a supporting runtime or library, reinstall the prerequisite supplied with that add-on rather than placing an unknown DLL beside fs9.exe.

A crash that happens only while approaching one location needs the separate add-on airport crash checks. If FS2004 starts normally but later crashes at unpredictable points, use our modern-PC stability checklist instead.

What if a clean FS9.cfg and stock flight do not fix it?

Check Windows compatibility and the base installation only after configuration and add-ons have been ruled out.

• Run the executable directly: a shortcut may point to an old or moved FS2004 installation.
• Check security history: antivirus software may have quarantined an add-on DLL or altered executable. Do not disable protection permanently.
• Test administrator access once: if FS2004 works only as administrator, the installation probably has a permissions problem. Legacy simulators are often easier to maintain in a dedicated folder outside protected Windows application directories.
• Try compatibility options individually: apply one setting, test, then undo it if there is no improvement. Selecting every compatibility option at once creates extra variables and can cause display problems.
• Restore the legitimate executable: an altered fs9.exe may be incompatible with the FS9.1 update or installed modules.

An original disc edition may fail before the splash screen if the Windows version blocks its obsolete copy-protection driver. Compatibility mode does not restore a removed driver; use that disc edition on an operating system that supports it, and avoid unofficial replacement executables.

Will reinstalling FS2004 fix a startup crash?

A reinstall helps only when the base files are damaged, and it must be tested before any add-ons return. Installing over the existing directory can leave the same faulty gauge, DLL or BGL in place.

1. Back up personal content. Preserve downloaded aircraft, scenery, saved flights and configuration files separately.
2. Remove the existing installation. After uninstalling, rename or remove the residual FS2004 folder so the next installation is genuinely clean.
3. Install into an empty folder. Start unmodified FS2004 once and confirm that a stock flight loads.
4. Apply the official FS9.1 update. Start and test the simulator again before adding anything else.
5. Restore add-ons in small groups. Test between groups, starting with the packages you trust most and leaving the suspected package until last.