Fix FSX add-on installation problems by correcting paths, folder nesting, permissions, dependencies and Steam Edition compatibility.
To fix add-on installation problems in FSX or FSX: Steam Edition, first confirm the add-on’s compatibility and the exact folder containing fsx.exe. Extract the archive fully, preserve its folder structure, install any supplied dependencies, then restart FSX and test the add-on alone. Most failures are wrong paths, extra folder nesting or missing support files.
Identify where the FSX installation is failing
The symptom usually reveals which part of the installation went wrong. An installer error, a missing aircraft and a start-up crash require different fixes.
| Symptom | Likely cause | First check |
|---|---|---|
| Installer says FSX is not installed | Wrong registry entry or boxed-FSX path | Browse directly to the folder containing fsx.exe |
| Aircraft does not appear | Extra folder level, wrong SimObjects folder or missing base aircraft | Find aircraft.cfg and check its location |
| Scenery is missing | Incorrect folder structure or inactive scenery area | Check for Scenery and Texture subfolders |
| Black cockpit or missing gauges | Gauge, panel alias or runtime dependency is absent | Re-read the dependency and support-file instructions |
| FSX crashes after installation | Incompatible module, bad configuration entry or add-on conflict | Remove the most recently added package and retest |
How do I install an FSX add-on in the correct folder?
- Read the package instructions first. Determine whether it is a complete aircraft, livery, scenery area, utility or module. A livery normally requires a specific base aircraft and cannot be installed as a standalone model.
- Confirm compatibility. Check whether the package requires boxed FSX, Acceleration, FSX: Steam Edition or another simulator. Older installers can mistake Steam Edition for an absent or separate FSX installation; our explanation of Steam Edition paths and legacy add-on compatibility covers those differences.
- Locate the real FSX root. This is the directory containing
fsx.exe. Typical boxed and Steam locations areC:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator XandC:\Program Files (x86)\Steam\steamapps\common\FSX, but custom installations and additional Steam libraries use different paths. - Extract the download completely. Do not run an installer from inside a ZIP archive. Extract it to a temporary folder, inspect the readme and unblock the downloaded archive or executable in Windows file properties if that option appears.
- Remove extra folder nesting. A complete aircraft’s folder should normally place
aircraft.cfg, its AIR file and themodel,panel,soundand texture folders directly below the aircraft folder. If they are buried one level deeper, FSX will not find the aircraft. Follow our aircraft folder and support-file installation instructions when diagnosing a missing model. - Copy support files only as instructed. Packages may include files for the root
Effects,GaugesorSoundfolders. Do not move every similarly named folder into the FSX root: aircraft-specific panel, sound and texture folders usually remain with that aircraft. - Activate scenery where required. A scenery area should normally have a folder containing
Sceneryand, when supplied,Texture. Add it through FSX’s Scenery Library unless its installer handles activation. Our scenery folder and activation examples explain the common incorrect-folder-level problem. - Restart and test one add-on. Close FSX before changing its files, then restart it after installation. Test at the relevant aircraft or airport before installing another package, so any conflict has an obvious source.
FSX and FSX: Steam Edition do not use a Community folder. Instructions mentioning that folder are intended for newer Microsoft Flight Simulator releases, not FSX.
Why can’t an old installer find FSX: Steam Edition?
Legacy installers often search for the boxed edition’s registry information or assume its default directory. If the installer offers a destination selector, point it to the folder containing Steam Edition’s fsx.exe, not merely the Steam or steamapps directory.
If there is no destination option, look for a documented manual-install method in the package. Avoid creating guessed registry keys or directing the installer to an arbitrary folder and copying everything afterwards; modules and shared files may require specific configuration entries.
When an installer reports success but no files appear, Windows permissions may have blocked or redirected writes from a legacy program. Check the intended FSX directory and the user account’s VirtualStore location. Run the installer as administrator only when it needs access to a protected FSX folder, and keep a backup of files it replaces.
Why does an installed aircraft or scenery not appear?
An add-on that installs without errors but remains invisible is usually in the wrong folder or is not a complete package. Check these points before reinstalling FSX:
- Wrong simulator directory: the installer may have written to an old boxed-FSX folder while Steam Edition is the copy being launched.
- Double nesting: folders such as
SimObjects\Airplanes\PackageName\PackageName\aircraft.cfgare one level too deep. - Missing base product: a repaint, expansion or sound set may depend on another aircraft or scenery package.
- Aircraft selection filters: search under the manufacturer, publisher or aircraft type defined in
aircraft.cfg, which may differ from the download name. - Duplicate aircraft title: two aircraft entries with the same internal
title=value can prevent one variation from appearing correctly. - Inactive scenery: copied scenery still needs a valid Scenery Library entry unless its installer created one.
- Missing requirement: some add-ons need Acceleration content, SimConnect components or Microsoft runtime libraries supplied with the package.
What should I do when the add-on installer gives an error?
Run the installer from a short local path after extracting the complete download, close FSX and verify that the destination drive has free space. Security software may quarantine an unfamiliar installer or component, so review its protection history rather than disabling protection across the entire system.
Install only the official dependencies supplied or named by the package. Never download an individual missing DLL from an unrelated DLL repository; the filename alone does not identify the required version or architecture.
InstallShield error 1607 is an installer-runtime and permissions problem rather than an FSX folder-layout problem. Use our specific repair steps for FSX error 1607 if that exact message appears.
How do I recover if FSX crashes after adding an add-on?
Remove or disable the newest add-on first, then launch FSX again. Moving a newly installed aircraft folder outside SimObjects\Airplanes is a quick isolation test; deactivate scenery before deleting its files.
For utilities and modules, restore backups of any edited XML or configuration files instead of deleting unrelated entries. A rejected FSX trust prompt can also prevent a gauge or module from loading, but approve executable code only when you trust its source.
If FSX works after the add-on is removed, reinstall that package alone and verify its edition requirements and dependencies. If it still fails, restore the files replaced during installation. Reinstalling the entire simulator should be the last resort, not the first troubleshooting step.