Fix missing scenery file errors in FS2004 by repairing Scenery Library paths, folder structure, scenery.cfg entries and incomplete add-on installs.
In FS2004 (FS9), missing scenery file errors usually mean scenery.cfg points to an add-on folder that was moved, renamed or deleted. Note the reported area and path, restore that folder or remove its stale Scenery Library entry, then restart FS2004. Do not download individual BGL files blindly.
What does the FS2004 missing scenery message mean?
The wording tells you whether FS2004 has lost an entire scenery area, an add-on was installed incompletely, or default simulator files are damaged.
| Symptom | Likely cause | Correct action |
|---|---|---|
Local scenery directory ... in scenery Area.xxx not found | A path recorded in scenery.cfg no longer exists | Restore the folder, correct its path or remove the obsolete library entry |
| Airport, buildings or ground textures are absent without a start-up warning | Incorrect folder level, inactive scenery area or missing add-on dependency | Check the package structure and activate the correct parent folder |
| Default airports or terrain are missing | A required default area was removed or its files were damaged | Restore the original files rather than deleting the library entry |
| The scenery works only when FS2004 is run as administrator | Files or configuration changes have been redirected by Windows permissions | Find the active installation and VirtualStore copy before editing anything |
How do I repair a missing FS2004 scenery path?
Use the Scenery Library wherever possible because it updates the catalogue more safely than manual configuration editing.
- Record the complete error. Write down the reported
Area.xxxnumber and directory. If several warnings appear, record each one; separate stale entries can produce a chain of messages. - Find the active FS2004 installation. Locate the folder containing
fs9.exerather than assuming the simulator is in its original Program Files location. If the scenery was on another drive, confirm that the drive is connected and still has the same drive letter. - Check the package structure. A normal add-on area should resemble
Flight Simulator 9\Addon Scenery\Package\Scenery, often with a neighbouringTexturefolder. The library entry normally points toPackage, not to itsScenerysubfolder. Double nesting such asPackage\Package\Sceneryis a common extraction mistake. Our FS2004 scenery folder and library instructions show the correct layouts. - Restore or remove the area. If you still want the add-on, put its folder back at the reported location or add its new location through the Scenery Library. If it was intentionally uninstalled, dismiss the warning, open Settings and then Scenery Library, select the obsolete area and remove it.
- Restart FS2004. Allow the simulator to rebuild its scenery database. Check the affected airport before changing scenery priority or installing further files.
If the bad entry prevents you from reaching the Scenery Library, recreate an empty folder at the exact reported path, including a Scenery subfolder. Start FS2004, remove the now-accessible library entry, close the simulator and then delete the temporary folder.
Why does the scenery error return after I fix it?
A recurring warning usually means FS2004 is reading a different folder or configuration file from the one you changed.
- Multiple FS9 installations: The add-on may have been copied into an old or inactive installation. Confirm which
fs9.exeyour shortcut launches. - Windows VirtualStore: An installation under Program Files can leave one copy of a file in the simulator folder and another in Windows VirtualStore. Our guidance on FS2004 installation permissions on modern Windows explains how this redirection causes apparently successful changes to affect the wrong copy.
- Incorrect folder depth: Extracting the archive into an extra wrapper folder leaves the path present but keeps the actual
SceneryandTexturefolders one level too deep. - External storage: A changed drive letter makes an absolute scenery path invalid even though all the files remain on the disk.
- Incomplete package: Some add-ons use a separate object library or texture package. Reinstall the complete package from its original archive rather than searching for individual BGL or texture files.
If manual editing is unavoidable, close FS2004 and back up the active scenery.cfg first. This file is normally associated with the FS2004 installation; it is not the same as FS9.cfg in the user profile. Find the section matching the reported [Area.xxx] and correct its Local= path, but use the Scenery Library to remove areas so that area and layer numbering remain valid.
What if FS2004 reports missing default scenery?
Do not remove an area when the missing path belongs to FS2004's original Scenery directory or is marked as required.
Check that the default folders have not been moved, renamed or replaced while installing an add-on. If original files were deleted, restore them from your own FS2004 installation media or perform a clean reinstall after backing up add-ons and configuration files. For airport-specific symptoms, follow our checks for restoring missing FS2004 default airports.
Should I delete scenery.cfg or the scenery indexes?
No—neither is the first fix for a missing-directory warning. Deleting scenery.cfg can remove the entire library catalogue and may leave both default and add-on areas incorrectly ordered.
Once every listed path is valid, FS2004 rebuilds its scenery database after a library change. If the configuration itself is damaged, restore a known-good backup or the original default configuration, then reactivate add-on areas one at a time. The add-on that brings the warning back is the entry requiring correction.