How do I remove an add-on from Flight Simulator 2004?

To remove an add-on from Microsoft Flight Simulator 2004 (FS2004), close the simulator and use the add-on’s uninstaller if it has one. Otherwise, reverse its installation: disable any Scenery Library entry, remove only the package’s own files and configuration references, then restore any stock files it replaced from backup.

The safest way to uninstall an FS2004 add-on

The reliable method is to reverse the package’s original installation one step at a time.

FS2004 has no universal add-on manager. Older packages commonly copied files into shared folders such as Gauges, Effects and Scenery\World\Scenery, so deleting an entire shared folder can break unrelated aircraft and scenery. An uncertain file left behind is usually less harmful than a shared file deleted by mistake.

1. Find the original readme or archive. Look for an installation file list, folder structure or uninstall instructions. If those are missing, inspect a fresh copy of the same package rather than relying solely on file dates; ZIP archives and installers may preserve old timestamps.
2. Back up everything you may change. Copy the add-on folder, relevant configuration files and any uncertain shared files to a temporary location outside the FS2004 directory.
3. Use the supplied uninstaller first. Check the package’s shortcuts and the Windows application list. Some installers also offer a removal option when run again. Do this before manually deleting the package because the uninstaller may require its installation log or original folder.
4. Disable the add-on where possible. Deactivate scenery through the Scenery Library. For a self-contained aircraft, move its complete folder outside FS2004 for a reversible test; renaming it inside Aircraft may not prevent the simulator from scanning it.
5. Close FS2004 completely. Do not edit configurations or remove scenery, gauges, effects or modules while fs9.exe is running.
6. Remove only confirmed package files. Delete its dedicated aircraft or scenery folder and any additional files explicitly named by the documentation. Never empty a shared folder to remove one add-on.
7. Undo configuration changes. Remove the matching repaint section, Scenery Library entry, sound or panel alias, module reference or other entry created by the add-on. Restore stock files if the installer replaced them.
8. Restart and test. Load a default aircraft first, then test the affected aircraft, airport or utility. If a problem appears, restore the last item removed before changing anything else.

How can I identify an add-on’s files?

The most dependable evidence is the package’s original folder structure and file list, not the date shown in Windows Explorer.

The main FS2004 directory is the folder containing fs9.exe. Our guide to the standard FS2004 add-on folders explains where aircraft, gauges, effects and scenery are normally copied.

If an old add-on installer asks whether it should remove a shared file, keep the file unless you have verified that no other package uses it.

How do I remove an aircraft or repaint from FS2004?

Remove a complete aircraft by moving or deleting its dedicated folder, but check its dependencies before doing so.

Complete aircraft

Move the aircraft’s folder out of Aircraft and start FS2004 to confirm that the intended entry has disappeared. Before permanent deletion, inspect the readme for files copied into Gauges, Effects or shared sound locations.

Do not remove a base aircraft until you have checked whether other repaints, panel aliases, sound aliases or AI schedules use it. Deleting the model can cause dependent liveries to disappear and AI traffic to lose an assigned aircraft.

Individual repaints and liveries

A repaint requires two changes: remove its texture folder and delete its matching entry from aircraft.cfg.

1. Back up aircraft.cfg. Keep the copy outside the aircraft folder while editing.
2. Match the repaint correctly. In its [fltsim.x] block, the texture= value normally identifies the corresponding texture.* folder.
3. Delete the complete repaint block. Remove from its [fltsim.x] heading down to, but not including, the next configuration section.
4. Renumber the remaining entries. Keep the headings consecutive from [fltsim.0] and avoid duplicate numbers, otherwise later liveries may not appear.
5. Remove the matching texture folder. Do not delete the aircraft’s model, panel or sound folders merely to remove one livery.

How do I remove scenery without causing startup errors?

Deactivate or delete the scenery’s library entry before removing its folder from the drive.

Leave the folder in place while changing the Scenery Library, accept the change and allow FS2004 to rebuild its scenery database. Then close the simulator and remove the package folder. Our explanation of FS2004 scenery structure and library entries shows how package folders and their Scenery and Texture subfolders relate to the library.

If the installer copied individual files directly into Addon Scenery\scenery or Scenery\World\Scenery, there may be no separate library entry. Remove only the exact .bgl files listed by the package. A single airport, exclusion or landclass file can affect an area larger than its filename suggests.

A missing-scenery warning at startup means that an active library entry still points to a deleted folder. An unexpected or duplicated airport usually means that another AFCAD-style airport file, exclusion file or second copy of the package remains active.

What should I do with AI traffic, gauges and modules?

These components need extra care because they are often shared by several add-ons.

AI traffic

Disable an AI package by moving its identified traffic .bgl outside the FS2004 directory, not by deleting every aircraft it uses. One traffic file may contain routes for many airlines, while one AI model may be referenced by several schedule packages.

Our safe method for removing unwanted FS2004 AI traffic explains how to isolate traffic files without breaking aircraft used by other schedules.

Gauges, effects and sounds

Treat files in Gauges, Effects and shared sound locations as common components unless the package documentation proves otherwise. Gauge files, effect files and sound aliases may be used by aircraft that were installed at a different time.

If removing one produces a blank panel, missing instruments or absent visual effects, restore it from the temporary backup. There is little benefit in deleting an uncertain shared component merely to recover a small amount of disk space.

Modules and stand-alone utilities

Use the utility’s own uninstaller because deleting a file from Modules may leave configuration data, companion programmes or Windows settings behind. If no uninstaller exists, follow the package’s removal notes and move suspected files out temporarily before deleting them.

Why does the add-on or an error remain after removal?

A persistent add-on or new error normally points to a leftover reference, a duplicate file, Windows file redirection or a shared dependency removed by mistake.

• The aircraft still appears: another copy of its folder exists, or a repaint’s [fltsim.x] block remains in aircraft.cfg.
• Later repaints have disappeared: the remaining [fltsim.x] headings contain a gap or duplicate number, or the base aircraft was removed.
• FS2004 reports a missing scenery path: the Scenery Library still contains an entry for a folder that no longer exists.
• The airport is duplicated or has the wrong layout: a second airport-layout or exclusion .bgl remains in another active scenery area.
• The panel is blank: a shared gauge or panel file was deleted.
• AI traffic has vanished: a traffic .bgl containing several schedules, or an aircraft model used by those schedules, was removed.
• A module warning appears at startup: part of the utility or one of its configuration references remains after an incomplete uninstall.

On Windows systems where FS2004 is installed under Program Files, User Account Control may have redirected edited files to a matching location beneath %LOCALAPPDATA%\VirtualStore. Check both locations if a deleted add-on returns or a configuration edit appears to be ignored. Compare the files carefully; do not empty VirtualStore indiscriminately.

What if the add-on overwrote default FS2004 files?

Deleting the add-on cannot restore a stock texture, panel, sound or configuration file that its installer replaced.

Restore the original from your pre-installation backup. If no backup exists, use a repair option only if your FS2004 installation media or installer offers one, or reinstall the affected simulator files. Back up personal aircraft, scenery and configuration changes before attempting either process.

Do I need to reinstall FS2004 to remove one add-on?

No; reinstalling the whole simulator is a last resort for widespread damage or unknown overwritten stock files, not the normal way to remove an add-on.

A stale Scenery Library entry, broken repaint block or missing shared gauge can usually be repaired directly. If the installation is damaged beyond practical repair, follow our procedure for removing FS2004 and its leftover files before a clean reinstall, taking care to preserve any aircraft, scenery and settings you still need.