Fix FS2004 crashes when opening the map by resetting FS9.CFG, testing add-on scenery, checking modules and applying the FS9.1 update.
FS2004 usually crashes when the map opens because its saved map or display state is corrupt, an add-on scenery file contains malformed or conflicting facility data, or an old module or graphics setting fails as the map window is created. Reset FS9.CFG first, then test a stock flight and isolate scenery before reinstalling.
How do I reset the FS2004 map configuration?
Moving FS9.CFG aside is the fastest first test because FS2004 creates a fresh configuration file when it next starts.
- Close FS2004 completely.
- Open the configuration folder. Press Windows key plus R, enter
%APPDATA%\Microsoft\FS9, and press Enter. - Back up FS9.CFG. Move
FS9.CFGto the desktop rather than deleting it. This file also contains display, control and other preferences. - Start a clean test flight. Use an unmodified default aircraft at a stock airport, without loading a saved flight or flight plan, and then open the map.
- Rebuild settings gradually. If the map works, re-enter your preferences in small groups. Copying the entire old file back will restore the fault.
The FS9 Configurator utility can help back up and inspect FS9 settings, but keep the untouched configuration until the cause is confirmed.
| Crash pattern | Likely area | Best next test |
|---|---|---|
| Every flight, including a default flight | FS9.CFG, display system or global module | Use a newly generated configuration |
| Only one saved flight or flight plan | Saved-flight or plan data | Create a new flight without a plan |
| Only near one airport or region | Add-on scenery or facility data | Disable scenery covering that location |
| Only with one add-on aircraft | Panel gauge or aircraft-related module | Repeat the flight with a default aircraft |
How can I tell whether add-on scenery causes the map crash?
A crash tied to one region, airport or recently installed scenery strongly points to an add-on BGL or facility-data conflict.
- Open the Scenery Library and untick only third-party scenery areas, beginning with recent airport and AFCAD-style additions.
- Restart FS2004 after changing the active scenery library.
- Test the map from the same location with a default aircraft.
- If it works, re-enable half the disabled areas and test again. Continue narrowing the group until one package reproduces the crash.
A common mistake is assuming that every add-on appears in the Scenery Library. Some installers place BGL files directly in shared or default scenery folders; unticking a library area will not disable those files. Use the add-on's installation record or backup rather than deleting unfamiliar BGLs. Our step-by-step method for scenery-related FS2004 crashes covers that broader isolation process.
What if a clean configuration and stock scenery still crash?
If a fresh FS9.CFG and stock scenery still crash, test the simulator version, aircraft, global modules and display mode in that order.
- Apply FS9.1: If the simulator has not already been patched, install the FS2004 9.1 update package. It includes stability and configuration fixes, although it is not a guaranteed map-specific cure.
- Test a default aircraft: A third-party panel gauge can remain active until the aircraft is changed. If the default aircraft works, repair or remove the affected aircraft rather than changing scenery.
- Isolate third-party modules: Back up and temporarily move only non-default DLLs from the simulator's
Modulesfolder. Do not remove Microsoft or stock files. Restore third-party modules individually until the crash returns. - Change display mode: Press Alt+Enter before opening the map to compare windowed and full-screen operation. A crash in only one mode points towards the display configuration, graphics driver or an overlay that hooks into FS9.
After a crash, Windows Event Viewer may provide a useful faulting-module name. A named third-party DLL gives a direct lead, while a display-driver DLL supports testing graphics settings and overlays. An entry naming only FS9.EXE does not identify the underlying cause.
On Windows 10 or 11, avoid applying several compatibility options at once because that obscures which change helped. Our modern-Windows FS2004 troubleshooting checklist explains configuration corruption, permissions and add-on conflicts in more detail.
Do I need to reinstall FS2004?
No—reinstallation should be the last step, after the map also crashes with a new FS9.CFG, default aircraft, no flight plan, stock scenery and third-party modules disabled.
An installation performed over the existing copy may preserve the faulty configuration or rogue add-on BGL, leaving the map crash unchanged. If core simulator files were overwritten, back up saved flights and add-ons, perform a clean repair or reinstall, apply FS9.1, and test the map before restoring anything. Add old content back in small groups so the offending file is not copied straight into the repaired installation.