Fix FS2004 freezing when selecting or loading a flight by isolating corrupt saved flights, aircraft, scenery, modules and FS9.cfg.
FS2004 usually freezes when you choose a flight because the selected saved flight, aircraft, panel gauge, scenery area or weather file is corrupt or incompatible. Test a basic flight with a default aircraft and airport, then isolate the linked add-on; if every flight hangs, rebuild FS9.cfg and check third-party modules.
Where exactly does FS2004 freeze?
The point at which FS2004 stops tells you which files to test first. A Windows “Not responding” message alone does not prove that the simulator has frozen: complex scenery, aircraft and gauges can block the interface while they load.
| Where it stops | Likely cause | Best next test |
|---|---|---|
| Opening the saved-flight list | Damaged .FLT or companion weather file | Temporarily move saved flights out of the Flight Simulator Files folder |
| Highlighting a particular aircraft | Faulty aircraft model, texture or package | Select a default FS2004 aircraft |
| After pressing Fly Now with one aircraft | Panel gauge, aircraft file, sound or module | Use the same airport with a default aircraft |
| At one airport or scenery area | Add-on scenery, AFCAD, mesh or AI traffic | Use the same aircraft at a stock airport |
| With every aircraft and airport | FS9.cfg, global module, graphics setting or broad scenery problem | Generate a fresh FS9.cfg |
Do not diagnose a specific file from the loading percentage alone; the percentage varies with the selected content. If the status text or disk activity is still changing, allow the load to finish. Our advice on checking whether a loading pause is a real hang explains the distinction in more detail.
How do I isolate the cause?
A clean default flight is the fastest way to separate an FS2004 installation problem from a bad saved flight or add-on.
- Back up the relevant files. Copy your user Documents
Flight Simulator Filesfolder andFS9.CFGbefore moving or renaming anything. - Create a new basic flight. Do not load the troublesome saved flight. Choose a default Cessna, a stock airport, clear weather and daytime conditions.
- Reduce AI traffic temporarily. If the basic flight still hangs, set the airline and general aviation traffic sliders to zero and test again.
- Change one component at a time. First try the problem aircraft at the stock airport. Then use the default aircraft at the problem airport. Test the saved weather only after both combinations work.
- Rebuild the flight rather than reusing it. Once all components load correctly, create the route again and save it under a new name.
A mistake we see constantly is changing the aircraft, airport, weather and scenery together. That may make the flight load, but it does not reveal which component failed.
Which fix matches the cause?
Fix only the component that fails the comparison test; removing unrelated add-ons creates new variables and can hide the original fault.
Corrupt saved flight or weather file
FS2004 stores user flights in the Flight Simulator Files folder under Documents. Move the suspect .FLT file and its matching .WX file to a temporary folder; also move the associated .PLN if that flight uses one.
If merely opening the saved-flight list freezes FS2004, move all user-saved flight sets out temporarily, start the simulator, and return them one set at a time. Recreating a damaged flight is safer than manually editing its references to aircraft, weather and scenery.
Aircraft, panel or gauge problem
If only one aircraft freezes, restore that package from its original FS2004-compatible archive or remove it for testing. Check its panel and gauges, especially anything added shortly before the fault appeared.
Temporarily move only known third-party files from the FS2004 Modules or Gauges folders; leave Microsoft’s default files in place. Do not copy a similarly named gauge from an unrelated aircraft, as gauge dependencies and versions are not interchangeable. If the aircraft uses FSUIPC or displays an FSUIPC message, follow our FSUIPC-specific checks for FS2004.
Airport, scenery or AI traffic problem
If the freeze follows one airport, disable that add-on’s Scenery Library entry, restart FS2004 and try the default version of the airport. A duplicate AFCAD, incompatible scenery BGL, nearby mesh or faulty AI aircraft can all stall loading even when the selected aircraft is sound.
When setting AI traffic to zero fixes the flight, restore the sliders gradually and inspect recently added traffic packages. For a failure tied to one location, use our airport and scenery isolation procedure rather than reinstalling the whole simulator.
What if every FS2004 flight freezes?
If a default aircraft at a stock airport also hangs, regenerate FS2004’s main configuration file before touching the installation.
- Close FS2004 completely.
- Open the configuration folder. Enter
%APPDATA%\Microsoft\FS9in the Windows Run box or File Explorer. - Rename the configuration. Change
FS9.CFGtoFS9.CFG.old; do not delete it. - Start FS2004. The simulator creates a clean configuration. Test a default flight before restoring controls or graphics options.
- Keep or restore the file. If the fresh configuration works, rebuild settings manually. If it changes nothing, close FS2004 and restore the original file.
Next, isolate recently installed third-party modules and global scenery entries. If the freezes are not tied specifically to flight selection, our modern-PC configuration and add-on checks cover permissions, graphics conflicts and memory exhaustion.
Reinstall only after a clean stock test fails
A reinstall is justified only when stock aircraft and airports still freeze after the user configuration, saved flights, third-party modules and add-on scenery have been isolated. Uninstalling FS2004 often leaves files in Documents or AppData, so immediately restoring those files can restore the same freeze. Test the stock simulator first, then return add-ons in small batches.