How do I repair or rebuild scenery.cfg in FS2004?

To repair or rebuild scenery.cfg in FS2004 (FS9), close the simulator, identify and back up the active file, then correct the faulty [Area.xxx] block or rename scenery.cfg so FS2004 creates a clean default copy. Check Windows VirtualStore first; editing the inactive copy is the most common reason nothing changes.

Where is the active scenery.cfg in FS2004?

The active scenery.cfg is usually in the main Flight Simulator 9 installation folder, but Windows may redirect it to VirtualStore.

A typical 64-bit Windows installation path is C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\scenery.cfg. A custom installation, or one made on 32-bit Windows, will use a different path.

FS2004 predates User Account Control. When it is installed under Program Files and run without administrator privileges, Windows can redirect changes to a per-user copy such as %LOCALAPPDATA%\VirtualStore\Program Files (x86)\Microsoft Games\Flight Simulator 9\scenery.cfg. The VirtualStore path mirrors the real installation path, so its exact folders may vary.

If both files exist, do not assume the first one found is active. Change the enabled state of a non-essential add-on in the FS2004 Scenery Library, exit the simulator normally, and check which file's content or modification time changed. Reverse the test afterwards. Alternating between standard and administrator launches can make FS2004 appear to use different configurations.

This file is separate from FS9.cfg, which stores display, sound and other simulator preferences. Use our instructions for rebuilding FS9.cfg when simulator settings are the problem.

Should I repair one scenery area or rebuild the whole file?

Repair one area when the error identifies a specific add-on; rebuild scenery.cfg when the catalogue has widespread structural damage or many unrelated entries fail.

scenery.cfg is a catalogue of scenery areas and priorities. Rebuilding it does not restore deleted BGLs, textures or stock scenery folders.

How do I repair a damaged scenery.cfg entry?

Use the FS2004 Scenery Library to remove or re-register an add-on whenever it remains accessible; edit the file manually when a bad entry prevents that.

1. Close FS2004 completely. If the simulator is still running, it may overwrite manual changes when it exits.
2. Back up the active configuration. Copy scenery.cfg to a clearly named backup such as scenery.cfg.before-repair. If you cannot establish which copy is active, back up both the installation-folder and VirtualStore files.
3. Find the reported area. Open the file in a plain-text editor and locate the heading named by the error, such as [Area.123]. A normal block commonly includes Title=, Local=, Layer=, Active= and Required=.
4. Check the Local path. A relative path is resolved from the FS2004 installation folder. For example, Local=Addon Scenery\My Airport should point to the add-on's base folder, with a Scenery subfolder beneath it and, where supplied, a neighbouring Texture folder. It should not point to an individual BGL file.
5. Correct the actual fault.
   • If the add-on still exists, repair the spelling, drive letter or folder level in Local=.
   • If the folder was moved, restore it to the recorded location or change the path to its new base folder.
   • If an unavailable network or removable-drive path is recorded in Local= or Remote=, reconnect that location or remove the obsolete area.
   • If the add-on was deleted, remove its entry through the Scenery Library. When the missing directory prevents this, temporarily recreate the expected base folder and its empty Scenery subfolder, remove the area through the library, then delete the temporary folders.
6. Preserve the file structure. If manual deletion is unavoidable, remove the complete [Area.xxx] block rather than selected lines. Keep area headings in a continuous sequence, layer values unique and the remaining priority order unchanged. Do not remove a stock area marked Required=TRUE merely to silence an error.
7. Save the exact filename. Use plain text and retain the name scenery.cfg. Enable file-name extensions or choose the editor's all-files option so it does not become scenery.cfg.txt.
8. Restart and test. FS2004 may spend longer loading while it updates its scenery indexes. Check the affected location and a default airport before making further changes.

If the message names a missing BGL, texture or scenery folder rather than a malformed area entry, use our guide to troubleshooting missing FS2004 scenery files and stale paths.

How do I rebuild scenery.cfg in FS2004?

A full rebuild restores FS2004's default scenery catalogue while removing add-on registrations and their saved priority order; it does not delete the add-on folders themselves.

1. Record the existing library. Keep the old file as a reference for add-on titles, paths and priority. Note the order shown in the Scenery Library if several packages depend on a specific layering arrangement.
2. Rename the active file. With FS2004 closed, rename scenery.cfg to scenery.cfg.old. Rename rather than delete it. If both installation-folder and VirtualStore copies exist and you are uncertain which is active, back up and rename both.
3. Launch FS2004 consistently. Start it using the same standard-user or administrator mode you intend to use afterwards. FS2004 should create a fresh default scenery.cfg and update its scenery indexes.
4. Test the default world first. Confirm that several stock airports and surrounding terrain load without configuration errors. Add-ons being absent from the rebuilt Scenery Library is expected.
5. Register add-ons again in small batches. Select each package's base folder, not its individual Scenery folder or BGL files. Restore the intended priority gradually and restart when FS2004 requests it. Do not paste every block from the damaged file into the new one, as that can immediately recreate the fault.

If FS2004 does not create a fresh file, restore the backup before doing anything else. Check whether another copy was left in VirtualStore and whether FS2004 can write to its effective location. If the new file lacks required default areas, use the original installation media or installer repair option after backing up add-ons stored inside the FS2004 directory.

Never substitute a scenery.cfg from FSX, Prepar3D or an unrelated installation. Their default areas, paths and layering are not interchangeable with FS2004.

What if rebuilding scenery.cfg does not fix the scenery?

A rebuild only fixes the scenery catalogue, so persistent visual faults point to missing files, inactive stock layers, duplicate BGLs or priority conflicts.

• Missing default airports: confirm the required stock layers are active and that their folders still exist. Our checks for restoring missing FS2004 stock airports cover the relevant layers, files and indexes.
• Duplicate runways or buildings: look for more than one AFCAD or airport BGL covering the same location.
• Plateaus, trenches or shifted scenery: examine mesh compatibility, scenery priority and packages made for a different airport layout. Follow our guide to resolving layered, corrupted or misaligned FS2004 scenery.
• Changes still do not persist: repeat the active-file test and stop switching between administrator and standard-user launches.

Which mistakes cause scenery.cfg problems to return?

The repeat failures we see most often come from restoring the same bad path or editing a configuration FS2004 is not using.

• Creating a blank file: FS2004 needs its general section and default area entries; let the simulator generate the replacement.
• Deleting scenery folders: rebuilding the catalogue only requires renaming scenery.cfg. Do not delete the main Scenery or Addon Scenery directories.
• Selecting the wrong folder level: an area's base directory should contain the Scenery subfolder.
• Restoring every add-on at once: one invalid package can recreate the original error and hide which entry caused it.
• Removing required layers: disabling a stock area may suppress one warning while causing missing airports, terrain or textures elsewhere.