Why does FS2004 crash to desktop when I open the map?

In FS2004 (FS9), a crash to desktop when opening the map is usually caused by a corrupted FS9.CFG, a bad saved flight or flight plan, malformed add-on scenery data, or a third-party gauge or module. Test a fresh configuration and stock flight first, then isolate scenery and add-ons; reinstall only as a last resort.

Why does FS2004 crash when the map opens?

The built-in map makes FS9 display stored interface settings and facility, navigation and route data, exposing faults that may not appear during normal cockpit rendering.

How do I reset the FS2004 map configuration?

Renaming FS9.CFG is the safest first repair because FS2004 creates a clean replacement without destroying the original file.

1. Close FS2004 completely. Confirm that FS9.EXE is no longer running before changing its configuration.
2. Open the FS9 settings folder. Press Windows key plus R, enter %APPDATA%\Microsoft\FS9, and press Enter.
3. Back up FS9.CFG. Rename it to something such as FS9.CFG.old, or move it to a separate backup folder. Do not delete it yet.
4. Start a clean flight. Select an unmodified default aircraft at a stock airport. Do not load a saved flight, weather file or flight plan.
5. Open the built-in map. Use the map command under FS2004's World menu rather than a map button on an add-on panel.
6. Interpret the result. If the map works, rebuild display and interface preferences gradually. Copying the old configuration back unchanged will also restore the problem.

A fresh FS9.CFG does not disable scenery, aircraft, gauges or DLL modules. If the crash remains, restore the old file if wanted and continue with the targeted tests below.

Could a saved flight or flight plan be causing the crash?

A saved flight or plan is the leading suspect when the map works in a newly created flight but fails after loading one particular .FLT or .PLN file.

Create a new flight at the same airport with the same default aircraft but no route. If its map opens, build the flight plan again from scratch rather than resaving the suspect file. If a newly created plan for the same route also crashes, the problem may instead be scenery or facility data along that route.

Saved flights can retain aircraft, location, weather and panel references, so changing only the flight plan does not always produce a clean test. Start from FS2004's flight creation screen rather than loading the old flight and modifying it.

How can I tell whether add-on scenery causes the map crash?

A crash confined to one airport, city or region strongly suggests a malformed add-on facility file, duplicate airport data or another scenery conflict.

Duplicate AFCAD-style files do not automatically crash FS2004, but overlapping or damaged airport and navigation records deserve attention because the map reads that information. Begin with recently installed airports, navigation-data replacements and packages that cover the affected location.

1. Disable relevant add-on areas. In the Scenery Library, turn off third-party entries covering the problem location, starting with the most recent installation.
2. Restart FS2004. Allow it to rebuild scenery information after the library change.
3. Retest under controlled conditions. Use a default aircraft at the same location without loading the original flight plan.
4. Narrow the group. If the map works, re-enable half the disabled areas and test again until one package reproduces the crash.

A mistake we see constantly is assuming every add-on has its own Scenery Library entry. Some installers copy BGL files into a shared scenery folder, so disabling the package's visible library area may leave the offending file active. Do not delete unfamiliar stock files; use the package's installation record and our controlled process for isolating scenery-related FS2004 crashes before moving confirmed add-on files.

What if the map crashes only with one aircraft?

A crash limited to one aircraft usually comes from its panel, gauge or supporting module rather than from the stock FS2004 map.

There is a useful distinction here: if the World-menu map works but a panel's MAP button crashes, that button may be calling a custom gauge, GPS or pop-up window. Test the same location in a default aircraft, then inspect only the affected aircraft's panel and documented dependencies.

Old binary gauges and DLL-based avionics can behave differently on later versions of Windows. Avoid removing random files from the global Gauges or Modules folders; first identify which components belong to the aircraft. Our guide to diagnosing incompatible FS2004 panel gauges explains how to separate aircraft-specific panel faults from global gauge problems.

What if a clean configuration and stock flight still crash?

If the map still crashes with a fresh configuration, default aircraft, stock location and no flight plan, concentrate on the FS2004 update level, display mode and global third-party modules.

• Check the FS9.1 update: An original unpatched FS2004 installation should be updated to FS9.1 before deeper troubleshooting. The update improves general stability, although it is not a guaranteed map-specific fix.
• Compare display modes: Press Alt+Enter before opening the map to test both windowed and full-screen operation. Failure in only one mode points towards graphics settings, a driver interaction or software drawing over the simulator.
• Turn off overlays temporarily: Disable recording overlays, performance displays and other utilities that hook into FS9. Change one item at a time so the result remains meaningful.
• Isolate known third-party modules: Back up and temporarily remove only DLLs that you know were installed by an add-on. Never empty the entire Modules folder or remove Microsoft files indiscriminately.
• Read the Windows crash entry: In Event Viewer, check the Application log for the corresponding FS9.EXE error. A named third-party DLL provides a useful lead; an entry naming only FS9.EXE does not prove that the executable itself is damaged.

FS2004 is a DirectX 9-era application, so later Windows graphics behaviour can expose old display assumptions. Apply compatibility changes individually rather than enabling several at once. Our modern-PC FS2004 crash checklist covers those display and Windows conflicts without duplicating them here.

Is it a real crash or an off-screen map window?

If FS9.EXE remains running after the simulator disappears, the map may be hidden behind another window or positioned on a disconnected monitor rather than having caused a true crash.

Use Alt+Tab to look for the map dialog and press Escape to dismiss it. Temporarily testing with one monitor and regenerating FS9.CFG can correct a stored window position. If the process has ended and Windows has recorded an application error, treat it as a genuine crash to desktop.

Do I need to reinstall FS2004?

Reinstall FS2004 only after the map also fails with a fresh FS9.CFG, default aircraft, no flight plan, stock scenery and known third-party modules disabled.

A repair installed over the existing copy can preserve the exact fault: the AppData configuration, add-on scenery and stray modules may remain untouched. If core simulator files were overwritten or damaged, back up personal content, repair or reinstall FS2004, apply the FS9.1 update where required, and test the map before restoring any add-ons.

Restore aircraft, scenery and modules in small groups. Reinstalling everything at once defeats the clean test and can copy the offending file straight back into FS9.