Fix FSX Scenery Library add-ons that vanish after restarting by finding the active scenery.cfg, correcting permissions and stopping file overwrites.
FSX usually loses Scenery Library entries after a restart because the change was written to the wrong scenery.cfg, Windows blocked that file from being saved, or a utility replaced it. This is especially common with FSX: Steam Edition, where boxed-FSX and Steam configuration folders can coexist.
Why do FSX scenery entries disappear?
A disappearing entry means FSX is no longer reading the registration added to its active scenery.cfg. The scenery files themselves are usually still installed; the library has lost or ignored the reference pointing to them.
- Wrong configuration file: an older installer may update the boxed-FSX file while Steam Edition reads another one.
- FSX was running during installation: when FSX closes, it can overwrite an external edit with the library configuration already held in memory.
- Write access was blocked: the active file may be read-only, have unsuitable permissions or be protected by Windows security software.
- Another utility restored the file: scenery managers, launchers, backup tools and system-cleaning utilities can replace a modified configuration.
- The file contains invalid manual edits: malformed
[Area.xxx]sections, duplicate section identifiers or missingLocal=lines can cause entries to be ignored or rewritten.
Which scenery.cfg does FSX actually use?
The active file is normally under %ProgramData%\Microsoft\, but its subfolder depends on the edition and installation history. The usual candidates are FSX\scenery.cfg and FSX-SE\scenery.cfg.
A Steam-only installation may use the folder named FSX, while a side-by-side boxed and Steam installation may create a separate FSX-SE branch. Our explanation of boxed FSX and Steam Edition add-on compatibility covers why legacy installers often select the wrong location.
Do not assume that every file named scenery.cfg is active. A copy in the FSX installation directory, an installer folder or a backup directory may be a template or an inactive copy.
| What you find | Likely cause |
|---|---|
| The add-on appears only in the other edition's file | The installer targeted the wrong FSX configuration |
| No candidate file changes after editing the library | Write access is blocked, or a different installation was launched |
| The active file gains the entry and later reverts | FSX or another utility is overwriting it |
| The entry remains listed but the scenery is absent | The problem is its path, folder structure, activation or priority |
How do I stop FSX Scenery Library entries disappearing?
- Close FSX and related utilities. Do not run a scenery installer or edit
scenery.cfgwhile the simulator, a launcher or a scenery-management tool is open. - Back up every candidate file. Copy the relevant
scenery.cfgfiles somewhere safe before changing permissions or repairing entries. - Identify the active file. Note each file's modified time, start the intended FSX edition, add one scenery area through the in-sim Scenery Library and exit normally. The file whose timestamp and contents change is the active one; search it for the area's
Title=entry. - Correct a wrong-edition installation. If the scenery files are already present, leave them in place and add their correct parent folder through the active Scenery Library. Point future installers at the actual boxed or Steam installation rather than copying registrations between configuration files.
- Restore write access. Remove the read-only attribute from the active file and confirm that your Windows account can modify its containing folder. If security software blocks FSX, allow the simulator executable rather than weakening permissions across the whole system.
- Check for redirected files. Search
%LOCALAPPDATA%\VirtualStorefor anotherscenery.cfg. A recently modified copy there suggests that Windows redirected an installer or programme which lacked permission to update the real file. - Find anything replacing the file. Start FSX once without optional launchers or scenery tools, add one area and restart. If it now remains, reintroduce those utilities one at a time until the overwrite returns.
- Repair damaged entries cautiously. Restore the last known-good backup where possible. Otherwise, retain a safety copy, remove only the malformed add-on block and add that scenery again through the library instead of inventing section or layer numbers by hand.
- Test before restoring everything. Add one package, close FSX normally and reopen it twice. Once that entry survives both starts, add the remaining scenery in small groups.
Should FSX always run as administrator?
No. One elevated test is useful: if FSX saves the library only when run as administrator, that confirms a permissions problem. The better fix is to grant suitable access to the active configuration and add-on folders, then use a consistent launch method; mixing elevated and standard runs can produce confusing file redirection.
What if the add-on stays listed but does not appear?
If the entry remains in the Scenery Library after restarting, the registration has been saved and the fault lies elsewhere. Check that the area is active, its folder still exists and the selected root contains a Scenery subfolder, with an optional Texture subfolder.
A common mistake is selecting an outer wrapper directory, leaving FSX one level above the folder it needs. Follow our manual FSX scenery installation procedure to verify the package structure.
If the structure is correct, check the area's priority and any airport, landclass or mesh packages covering the same location. Our guide to setting FSX scenery library priority explains which types belong above or below others. An unavailable external drive or a moved scenery folder can also leave an entry listed while giving FSX no files to load.