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

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

Why does FSX report a scenery.cfg error?

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

The warning commonly identifies an area number and says its local scenery directory cannot be found. The scenery itself may be intact elsewhere on the drive; scenery.cfg is the index telling FSX where to find it and in which priority order to load it.

Typical causes include extracting an add-on one folder too deep, changing its folder name after installation, disconnecting an external drive, or uninstalling scenery without removing its library entry. If the warning names Nuuk or another airport, that name identifies the affected package; it does not necessarily mean FSX's whole regional scenery is damaged.

Selecting Yes or OK normally dismisses the message but does not repair the path. If a translated message says the directory non esiste or нету его, both mean that the named directory is not there. If non cambia nulla — nothing changes — after dismissing it, the invalid entry is still present.

Which scenery.cfg repair should I choose?

Match the repair to what the warning's Local= path is supposed to contain; rebuilding the entire file is unnecessary for one abandoned add-on.

How do I repair the broken scenery entry?

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

1. Record every warning. Note the full directory and each Area number shown. Several removed add-ons can produce several consecutive messages.
2. Dismiss the warnings and close FSX if necessary. If FSX reaches its menus, open Settings > Scenery Library. If it cannot reach the menus, inspect the active configuration manually as described below.
3. Check the named directory. Confirm that the package exists and locate the folder directly containing its Scenery subfolder. A neighbouring Texture folder is optional and depends on the package.
4. Apply the matching repair. Restore a missing folder, reconnect its drive, or select the obsolete or incorrect library area and remove it. If the add-on is still wanted, use Add Area to register the correct parent folder.
5. Check its priority and enabled state. Keep local airports above broader regional scenery when they overlap, and ensure the entry is enabled.
6. Restart FSX. Confirm both that the warning has stopped and that the scenery appears at its intended location.

Our detailed Scenery Library management instructions cover adding, removing, enabling and ordering entries without manually altering area numbers.

Why does FSX say the folder does not contain a Scenery subfolder?

FSX expects you to select the package root — the folder directly above Scenery — rather than the Scenery folder itself.

A correct package commonly looks like Addon Sceneryi_uff0eMy Airporti_uff0eSceneryi_uff0e*.bgl, with textures under Addon Sceneryi_uff0eMy Airporti_uff0eTexture. Select My Airport when adding the area. A mistake we see constantly is selecting My Airporti_uff0eScenery, which leaves FSX looking for another Scenery folder inside it.

Reports sometimes call this a “folder does not contain editor subfolder” error, but the folder FSX requires is literally named Scenery, not Editor. Also check for doubled extraction paths such as My Airporti_uff0eMy Airporti_uff0eScenery; in that case, select the inner My Airport.

Some simple downloads supply loose BGL files intended for the already registered Addon Sceneryi_uff0eScenery directory. Follow that package's installation notes instead of creating a second library entry for the same folder.

Why does Add Area fail to show up on Windows 10?

The legacy FSX folder picker can open the selected directory instead of accepting it, making it appear that Add Area has done nothing.

When this happens on an affected Windows 10 installation, browse into the package root until its Scenery and optional Texture folders are visible, then right-click an empty white area below or beside the folder icons. The picker should close and add the area. Return to the library and verify that the new title appears before restarting FSX.

If it still fails to show up, confirm that you selected the parent folder, not Scenery itself, and check whether Windows security software or folder permissions prevented FSX from updating its active configuration.

Where is scenery.cfg on Windows 10?

The active FSX scenery.cfg is normally in the hidden Windows ProgramData tree, not beside fsx.cfg in your user profile and not necessarily inside the simulator's installation directory.

Paste %ProgramData%i_uff0eMicrosoft 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 dates with the library used by your simulator. Editing the wrong copy is a common reason a fix appears to make no difference.

If someone in a forum calls this system.cfg or “system cfg”, they are usually referring to the wrong file. FSX has no global system.cfg that controls its Scenery Library, and fsx.cfg stores different simulator preferences. For edition-specific checks, see our guide to finding and safely editing the active scenery.cfg.

If the file appears not to exist, make sure File Explorer is showing file extensions and that you checked the correct FSX or FSX-SE directory. Do not download another simmer's configuration: its drive letters, installed packages and layer order will not match yours.

How can I edit scenery.cfg safely?

Manual editing is appropriate when FSX cannot open the Scenery Library or when the warning must be mapped from an Area number to its actual title and path.

1. Close FSX completely. Editing while the simulator is running risks having your changes overwritten when it exits.
2. Back up the active file. Copy scenery.cfg somewhere safe before opening it in a plain-text editor.
3. Find the reported section. Search for the matching header, such as [Area.123]. The nearby Title= line identifies the area and Local= contains its registered directory.
4. Compare the path with the disk. A relative path such as Local=Addon Sceneryi_uff0eMy Airport is resolved from the FSX installation directory. Scenery stored elsewhere may use a complete path including its drive letter.
5. Make the smallest necessary change. Correct an obvious path error, but do not casually alter default areas, layer priorities or unrelated entries. Removing an entry through Scenery Library is safer than deleting its section manually.
6. Save it as plain text. Retain the exact .cfg extension. If saving is denied, edit a copy and place it back while accepting the required 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. Never overwrite the active file with one supplied in an old scenery package.

When should I rebuild a corrupt scenery.cfg?

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

1. Close FSX.
2. Rename the active file from scenery.cfg to scenery.cfg.bak.
3. Launch the correct FSX edition. A normal installation should generate a clean default scenery library.
4. Check the default areas first. Do not begin reinstalling add-ons until FSX loads without default-scenery warnings.
5. Re-add add-ons one package at a time. Their files remain on disk, but their registrations, enabled states and custom priority order must be recreated.

If important add-on areas disappear after the reset, use our steps for restoring missing Scenery Library entries from folders or backups. Keep the renamed file until the rebuilt library has been checked.

Why does a scenery still fail to show up after the error is fixed?

Removing the warning proves only that FSX can resolve the registered path; it does not prove that the package contains active, compatible scenery for the location being viewed.

• Confirm that the entry is enabled in Scenery Library.
• Check that its BGL files are inside the registered package's Scenery subfolder and have not been renamed or disabled.
• Make sure you are viewing the airport or coordinates the package actually modifies; a title such as Nuuk may cover one airport rather than the entire region.
• Place a local airport above overlapping regional, mesh or landclass packages unless the add-on's instructions specify another order.
• Check that the download was made for FSX or FSX: Steam Edition rather than another simulator.

If the warning returns after every restart, FSX is still reading an invalid Local= value, the file is being restored by an installer, or a different FSX/FSX-SE configuration was edited. Match the active file's path character for character against the folder that actually exists.