Completely uninstall an FSX Steam Edition add-on without breaking shared gauges or scenery. Follow the correct clean-up steps for every add-on type.
To completely uninstall an add-on from FSX: Steam Edition, run its own uninstaller first, then remove only files and configuration entries that belong to it. Check the FSX installation folder, Scenery Library and per-user configuration files. Never delete shared gauges, effects, SimConnect components or libraries unless you know no other add-on uses them.
The safest FSX add-on removal order
The safest method is to let the original installer reverse its changes before cleaning up anything it leaves behind.
- Close FSX and related utilities. Exit weather engines, traffic programs, launchers and configuration tools associated with the add-on.
- Identify how it was installed. Check Windows' installed-apps list, the Steam DLC controls, the product folder and any original readme or file manifest. Do not delete the main folder before looking for its uninstaller; some removal records are stored there.
- Back up relevant files. Copy the add-on's folder and any configuration files you plan to edit. This lets you restore a shared file if another aircraft or utility stops working.
- Deactivate the licence if required. Some commercial products count computer activations. Use the product's documented deactivation option before uninstalling when one exists.
- Run the supplied remover. Use the product uninstaller for an installer-based package. For Steam-delivered DLC, disable or uninstall it through Steam rather than deleting its folders manually.
- Inspect known leftovers. Remove only dedicated files listed by the installer manifest or clearly belonging to that product. Check scenery registrations and any entries the add-on placed in
dll.xml,exe.xmlorfsx.cfg. - Start FSX and test a default flight. Confirm that the add-on has disappeared and that unrelated aircraft, gauges, scenery and utilities still load.
Where does FSX: Steam Edition store add-on files?
FSX: Steam Edition can store one add-on across the simulator folder, Windows profile folders and shared application-data folders. Use Steam's command for browsing installed files to find the actual simulator directory; a common location is C:\Program Files (x86)\Steam\steamapps\common\FSX, but a custom Steam library may be elsewhere.
SimObjects\Airplanes,SimObjects\Rotorcraftand otherSimObjectssubfolders contain aircraft and related objects.Gauges,Effects,SoundandTexturemay contain support files shared by several products.Addon Sceneryand custom scenery folders contain airports, terrain and mesh packages.%APPDATA%\Microsoft\FSXnormally contains per-user configuration files. A side-by-side installation with boxed FSX may use anFSX-SEprofile instead.%PROGRAMDATA%\Microsoft\FSX, or itsFSX-SEcounterpart in some installations, can contain shared scenery configuration and indexes.
Boxed FSX and Steam Edition can leave similarly named folders on the same computer. Our explanation of how FSX:SE handles older FSX add-on folders will help if both versions have been installed. Check folder contents and modification dates rather than cleaning both profiles blindly.
What should I remove for each type of FSX add-on?
Remove the package's own files and registration entries, but preserve shared dependencies unless the documentation confirms that nothing else uses them.
| Add-on type | Items to remove | Main precaution |
|---|---|---|
| Aircraft | Its complete folder under SimObjects, plus dedicated gauges, effects and sounds documented by the package | Do not delete a shared gauge or sound folder merely because the aircraft used it |
| Scenery | The scenery area from the FSX Scenery Library, followed by its installed folder | Remove the library entry before deleting the folder to avoid a missing-area warning |
| Utility or module | Its program folder and exact launch block in dll.xml or exe.xml | Keep the XML valid and do not remove another module's block |
| AI traffic | Dedicated AI models and the package's traffic BGL files | A remaining traffic BGL can continue spawning traffic after the main program is gone |
| Texture or weather replacement | Files handled by its uninstaller and any documented product-specific folders | Stock files may need repairing through Steam after removal |
Aircraft packages often spread support files beyond their main aircraft folder. Follow our dedicated FSX aircraft-removal checklist rather than deleting only the folder visible in the aircraft-selection menu.
Do not remove Microsoft SimConnect runtimes, Visual C++ components or an independently installed shared module as part of routine add-on clean-up. Other FSX products may depend on them.
Why does the add-on still appear after uninstalling it?
A removed add-on usually remains visible because a second copy, scenery registration or start-up entry was left behind.
- Search all configured
SimObjectPathslocations infsx.cfg, not just the standardSimObjectsfolder. - Check for another Steam library or an old boxed-FSX installation containing the same package.
- Remove a deleted scenery package from the Scenery Library if its area is still registered.
- Inspect
dll.xmlandexe.xmlfor the product's exact launch entry. Back up the file before editing it. - For AI packages, locate the dedicated traffic BGL rather than removing only the visible aircraft models.
A saved flight can still name a removed aircraft and report that it is missing; that does not mean the aircraft remains installed. Product-specific settings under Documents, AppData or ProgramData can also remain without being loaded by FSX. Delete those only when they are clearly identified and you do not want to preserve profiles or settings.
A registry cleaner is unnecessary and can damage unrelated software registrations. Remove registry entries only when the product's documentation identifies them and its own uninstaller has failed.
Will Steam Verify remove every FSX add-on file?
No. Steam's file verification restores missing or altered files that belong to FSX, but it generally does not delete untracked files added by third-party packages.
Verification is useful after uninstalling a texture or weather package that replaced stock files. Be aware that it can also reverse intentional edits made to default FSX files by other add-ons.
Uninstalling and reinstalling FSX through Steam may likewise leave third-party files behind in the simulator directory. If the simulator itself must be returned to a genuinely clean state, use our process for removing FSX, its configuration folders and residual files; a full simulator removal should be the last resort, not the normal way to uninstall one add-on.