Fix FS2004 slow loading by finding faulty scenery, aircraft or AI files, correcting index problems and choosing storage upgrades that help.
FS2004 usually loads slowly because it is scanning a large or faulty scenery library, thousands of add-on aircraft or AI files, or files held on a slow drive. Test a default flight, disable add-ons in batches, ensure scenery indexes can be saved, and place the complete installation on an SSD.
What makes FS2004 take so long to load?
The point at which FS2004 slows down usually identifies the cause.
| Where it slows | Likely cause | First test |
|---|---|---|
| Before the opening screen | Large aircraft collection, a third-party module, antivirus scanning or slow storage | Temporarily remove recently added aircraft or modules and test with security software configured appropriately |
| While creating every flight | Scenery, AI traffic, weather or a storage bottleneck | Load a default aircraft at a default airport with traffic disabled |
| Only with one aircraft | Faulty panel, gauge, texture, sound or aircraft configuration | Load the same location with a default aircraft |
| While rebuilding scenery on every launch | Invalid scenery paths or index files that FS9 cannot retain | Check scenery entries and folder permissions |
| Only after changing scenery | A normal one-time scenery database rebuild | Let FS2004 finish and test the next launch |
A slow first load after installing or reordering scenery is expected. Rebuilding the same database after every clean shutdown is not.
How do I find the add-on causing slow loading?
The quickest method is to establish a clean baseline, then restore add-ons in groups until the delay returns.
- Back up the active configuration. Copy
FS9.cfg,scenery.cfgand any files you plan to move. Do not remove default scenery, aircraft or shared gauges. - Test a simple default flight. Use a default aircraft, default airport, simple weather and no AI traffic. Time program startup separately from flight loading. If FS9 normally starts directly into a saved flight, change that flight to one using default content.
- Disable non-default scenery in batches. Untick roughly half the add-on areas in the Scenery Library, close FS2004 and restart it. Repeat with the slow half until one area remains. Missing network drives, unplugged external drives, duplicate layers and enormous catch-all scenery folders are frequent offenders. Our explanation of how FS2004 scenery folders and library layers should be arranged covers the correct structure.
- Test aircraft separately. If the default aircraft loads normally, move the suspect add-on's complete folder out of
Aircraftand reinstall a clean copy. Check its panel, gauge, texture and sound dependencies rather than assuming the aircraft model itself is at fault. - Isolate AI traffic. Set AI traffic to zero first. If that fixes the delay, temporarily move third-party traffic schedule files into a holding folder outside the FS2004 tree, then restore them one package at a time. Keep the aircraft used by those schedules backed up as well.
- Check startup modules and utilities. A newly installed gauge module, weather utility or other program configured to connect when FS9 starts can hold up the opening screen. Disable only known third-party components, one at a time, and preserve their original locations.
- Regenerate FS9.cfg last. With FS2004 closed, rename
%APPDATA%\Microsoft\FS9\FS9.cfgtoFS9.cfg.old. FS9 will create a fresh file at the next launch. This resets many preferences, so retain the old file until the test is complete. Use conservative FS9.cfg adjustments and their trade-offs when rebuilding your settings.
A mistake we see constantly is changing scenery, aircraft, AI and configuration settings simultaneously. That may hide the symptom, but it does not identify the bad package and makes restoring the simulator much harder.
Why does FS2004 rebuild the scenery database every time?
Repeated scenery rebuilding means FS2004 is detecting a change on every launch or cannot save and reuse its generated scenery indexes.
- Confirm that every enabled Scenery Library path still exists and that removable or network storage is connected.
- Make sure your Windows account can write to the FS2004 installation, configuration and scenery-index locations. Legacy installations under a protected system folder can be affected by permissions or file virtualisation.
- Remove invalid or duplicate library entries through the Scenery Library rather than editing unrelated files blindly.
- Allow one complete rebuild and close FS2004 normally. Interrupting the process can force another rebuild.
- Check whether antivirus or cleanup software is quarantining or deleting generated files after FS9 exits.
Do not delete scenery indexes before every flight. That guarantees a slower next launch and masks the permissions or path problem that caused the repeated rebuild.
Will an SSD, more RAM or lower settings make FS2004 load faster?
An SSD usually provides the most useful hardware improvement because FS2004 add-ons contain large numbers of small files, but it cannot repair faulty scenery or configuration data.
- SSD: Move the complete FS2004 installation and frequently used add-on scenery, not just
FS9.exe. Scenery left on a slow or disconnected drive remains a bottleneck. - Hard disk: Check free space and disk health, then use Windows' optimisation tools. Do not manually defragment an SSD.
- RAM: Extra memory helps only when Windows is paging to disk. FS2004 is a 32-bit application, so adding large amounts of RAM beyond a healthy system baseline will not make its file scans proportionally faster.
- CPU: Faster per-core performance can help, but FS9 benefits less from numerous processor cores than modern simulators. Raising process priority cannot fix damaged scenery or an inaccessible drive.
- Antivirus: Real-time scanning can delay thousands of texture, gauge and scenery files. After scanning the installation, exclude only trusted FS2004 folders if necessary; do not disable protection globally.
Lower AI traffic, scenery complexity, autogen and detailed weather can reduce flight-creation time and runtime pauses. They have little effect on a long delay before the opening screen. Use our breakdown of the FS2004 settings with the largest performance cost rather than reducing every slider indiscriminately.
If competing background applications are the confirmed problem, the optional FS2004 background-process and priority helper may reduce interference. Treat it as a secondary measure: scenery isolation, valid file paths, persistent indexes and suitable storage should be fixed first.