Skip to content
FSX & FSX: Steam Edition 10 min read 320 views

How do I fix a scenery.cfg error in FSX?

Adam McEnroe
In short

Fix an FSX or FSX: Steam Edition scenery.cfg error by finding the bad Area path, correcting the folder level, or safely rebuilding the file.

To fix a scenery.cfg error in FSX or FSX: Steam Edition, note the reported Area number and Local path, then restore the missing scenery folder or remove and re-add that Scenery Library entry at the correct folder level. Back up scenery.cfg before editing; rebuild it only when several entries or its structure are corrupt.

Why does FSX report a scenery.cfg error?

An FSX scenery.cfg error means a Scenery Library entry points to a directory that has been moved, renamed, deleted or registered at the wrong folder level.

The warning usually identifies an Area number and says that its local scenery directory cannot be found. The actual scenery may still exist elsewhere; scenery.cfg is the index that tells FSX where each package is and in which priority order it should load.

Common causes include extracting an add-on one folder too deep, renaming it after installation, disconnecting an external drive, changing a drive letter, or deleting scenery without removing its library entry. Dismissing the warning with OK or Yes lets FSX continue when possible, but it does not correct the path.

The error appeared suddenly: what happened?

A sudden warning usually means something outside FSX changed while the registered path stayed the same.

An external or network drive may be unavailable, Windows may have assigned a different drive letter, an installer may have removed or relocated a package, or a folder may have been renamed during file organisation. The warning by itself does not mean the entire FSX installation is damaged.

What if those files or folders are not there?

If the missing directory belonged to an add-on you no longer use, remove its obsolete Scenery Library entry rather than creating empty folders to silence the warning.

If it is still wanted, reinstall or restore the package to its registered location, or re-add it from its new location. If the missing path belongs to stock FSX scenery, do not delete the entry: use the Steam file-verification process for FSX: Steam Edition or the repair option for a boxed FSX installation.

Which scenery.cfg repair should I choose?

Choose the repair according to what the reported Local= path is meant to contain.

What you findCorrect repair
The add-on folder was moved or renamedRestore its original path, or remove and re-add the library entry using the new location.
Scenery is nested another folder deeperRegister the package root directly containing the Scenery subfolder.
The add-on was uninstalledRemove its obsolete Scenery Library entry.
The path is on an unavailable driveReconnect the drive with its previous letter, or register the scenery at its new path.
A stock path such as Scenery\... is missingRepair or verify the FSX installation. Do not remove a required default area merely to suppress the message.
Many areas are malformed, duplicated or unreadableBack up and rebuild the active scenery.cfg.

How do I repair the broken scenery entry?

The safest repair is to correct the package on disk and let the FSX Scenery Library rewrite its registration.

  1. Record every warning. Note the complete directory and each reported Area number. Several abandoned add-ons can produce a series of almost identical messages.
  2. Open the Scenery Library. After dismissing the warning, use Settings > Scenery Library. If FSX cannot reach its menus, close it and inspect the active configuration manually.
  3. Check the named path. Find the folder directly containing the package's Scenery subfolder. A neighbouring Texture folder is common but not required by every package.
  4. Apply the appropriate fix. Restore the folder, reconnect its drive, or remove the obsolete or incorrect entry. If the package is still required, use Add Area to register the correct package root.
  5. Check its state and priority. Ensure the entry is enabled. Place a local airport above overlapping regional scenery unless the package instructions require a different order.
  6. Restart FSX. Confirm that the warning has stopped and visit the affected location to check that the scenery loads.

Our step-by-step instructions for adding, removing and ordering FSX scenery entries cover the library controls without requiring manual Area-number changes.

Why do I see folder does not contain editor subfolder?

The reference to an Editor subfolder is a misreading or mistranslation: FSX requires a folder literally named Scenery.

A normal package might be arranged as Addon Scenery\My Airport\Scenery\*.bgl, with textures under Addon Scenery\My Airport\Texture. Select My Airport when adding the area. Selecting My Airport\Scenery makes FSX look for another Scenery folder inside it.

Also check for doubled extraction paths such as My Airport\My Airport\Scenery. In that example, the inner My Airport is the folder to register. Some small downloads instead provide loose BGL files for the existing Addon Scenery\Scenery directory; those should not receive a separate library entry unless their instructions specifically require one.

Why does Add Area appear to do nothing on Windows 10?

The legacy FSX folder picker can open the selected directory instead of accepting it on some Windows 10 systems.

Browse to the package root so its Scenery and optional Texture folders are visible, then right-click an empty area of the folder window. The picker should close and add the entry. Return to Scenery Library and verify that the new title appears before restarting FSX.

If it still fails, check that you selected the parent of Scenery, not Scenery itself. A read-only configuration file or insufficient permission to update the active scenery.cfg can also prevent the new area from being saved.

Where is scenery.cfg for FSX and FSX: Steam Edition?

The active scenery.cfg is normally under the hidden Windows ProgramData directory, not beside your user-specific fsx.cfg.

FSX installationLikely active file
Boxed FSX%ProgramData%\Microsoft\FSX\scenery.cfg
FSX: Steam Edition without boxed FSXUsually %ProgramData%\Microsoft\FSX\scenery.cfg
Boxed FSX and Steam Edition installed togetherSteam Edition may use %ProgramData%\Microsoft\FSX-SE\scenery.cfg

Paste %ProgramData%\Microsoft into File Explorer's address bar; this works even when ProgramData is hidden. If both FSX and FSX-SE exist, compare their area titles and modification times with the edition you just closed. Editing the wrong copy is a common reason nothing changes.

fsx.cfg is a different file containing simulator preferences, so resetting it will not repair a broken scenery path. Our guide to finding the active scenery.cfg for each FSX edition and editing it safely provides the edition-specific checks.

If no scenery.cfg appears, enable file-name extensions and check both possible directories. Do not download another simmer's file: its drive letters, installed packages and layer order will not match your system.

How can I edit scenery.cfg safely?

Manual editing is appropriate when FSX cannot open Scenery Library or when you need to match a reported Area number to its registered path.

  1. Close FSX completely. Changes made while it is running may be overwritten when the simulator exits.
  2. Back up the active file. Copy scenery.cfg to a safe location before opening the original in a plain-text editor.
  3. Find the reported section. Search for a header such as [Area.123]. Its Title= line identifies the entry, while Local= contains the path FSX is trying to load.
  4. Compare the path with the disk. A relative value such as Local=Addon Scenery\My Airport is resolved from the FSX installation directory. Scenery elsewhere may use a complete path with a drive letter.
  5. Make the smallest correction. Fix an obvious path error, but do not casually remove default areas or renumber unrelated sections. Removing an add-on through Scenery Library is safer than deleting its section manually.
  6. Save it as plain text. Keep the exact .cfg extension. If access is denied, edit a copy and place it back while accepting the necessary Windows administrator prompt.

The Area number identifies a configuration section, while Layer controls loading priority. They should not be blindly renumbered or forced to match, and the active file should never be overwritten with an old configuration supplied by a scenery package.

Why do I get the same thing again after restarting FSX?

If FSX shows the same thing again, either the invalid path was never changed, another bad entry is now being reported, or you edited a configuration file that the running edition does not use.

  • Compare the new Area number with the previous one. If it changed, FSX has advanced to another broken entry even though the warning wording is identical.
  • Check that the corrected folder still exists under exactly the same path and drive letter.
  • Confirm that you changed the active FSX or FSX-SE copy of scenery.cfg.
  • Make sure the file is not read-only and that FSX can save changes to it.
  • Check whether an installer, restoration utility or copied backup is putting the old entry back.

If the warning returns only after a particular add-on installer runs, remove its invalid entry and reinstall that package using a location that remains available whenever FSX starts.

When should I rebuild a corrupt scenery.cfg?

Rebuild scenery.cfg only when many unrelated entries fail or the file's section structure is malformed; one missing add-on path should be repaired individually.

  1. Close FSX.
  2. Rename the active file. Change scenery.cfg to scenery.cfg.bak rather than deleting it.
  3. Launch the correct FSX edition. A normal installation should generate a clean default scenery library.
  4. Test the default areas first. Do not re-register add-ons until FSX starts without stock-scenery warnings.
  5. Re-add add-ons one at a time. Their files remain on disk, but their registrations, enabled states and custom priority order must be recreated.

Keep the backup until the rebuilt library has been checked. If wanted packages disappear from the list, follow our procedure to restore missing add-on entries from existing folders or a backup.

What if none of those worked?

If none of those worked, determine whether the warning comes from an add-on entry, missing stock scenery or the wrong active configuration before making further changes.

  1. Photograph or copy the complete warning. The Area number and directory are more useful than the generic error wording.
  2. Verify the active configuration. Close FSX and check which scenery.cfg received the latest modification time. Steam and boxed installations can use different directories when both are installed.
  3. Classify the missing path. Remove a stale add-on entry, but repair or verify the simulator if the absent directory belongs to default FSX scenery.
  4. Test a clean configuration. Rename the active file and let FSX build a default one. If the clean library works, re-add packages gradually until the faulty entry is identified.
  5. Check write access. If every change disappears after closing FSX, the active file may be read-only or protected from modification.

If a newly generated default library still reports missing stock directories, the problem is no longer just scenery.cfg; the FSX installation itself needs repairing. Retain backups of add-on folders and configurations before running a repair or Steam verification.

Why does the scenery still not appear after fixing the error?

Removing the warning proves that FSX can resolve the registered folder; it does not prove that the package is enabled, correctly structured or compatible with FSX.

  • Confirm that the area is enabled in Scenery Library.
  • Check that its BGL files are inside the registered package's Scenery subfolder.
  • Make sure you are viewing the airport or coordinates that the package actually changes.
  • Place a local airport above conflicting regional scenery, mesh or landclass unless its instructions say otherwise.
  • Confirm that the download was made for FSX or FSX: Steam Edition rather than another simulator.

For the remaining visibility checks, use our focused guide to diagnosing an installed add-on that FSX still ignores.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members