Back up and restore default FS2004 textures safely, find the right folders, handle VirtualStore, and recover originals without a needless reinstall.
To back up default textures in Microsoft Flight Simulator 2004 (FS2004), close the simulator and copy its entire installation folder to a safe location before installing replacements. To restore them, copy the matching original files or folders back; if the mod added files, replace or clean the affected set rather than merely merging it.
Which FS2004 texture folders should I back up?
A clean copy of the complete FS2004 installation folder is the safest source for restoring stock textures. In the paths below, [FS2004] means the folder containing fs9.exe, Aircraft, Scenery and Texture.
| Folder area | What it normally affects | When to back it up |
|---|---|---|
[FS2004]\Texture | Shared textures and many environment replacements | Before installing grass, water, sky or other global texture sets |
[FS2004]\Scenery\...\Texture | World, terrain, airport and scenery-specific surfaces | Before installing runway, ground, terrain or airport texture packages |
[FS2004]\Addon Scenery\[add-on]\Texture | Textures belonging to one add-on scenery package | Before updating or modifying that particular scenery |
[FS2004]\Aircraft\[aircraft]\texture* | Aircraft liveries and model-specific textures | Before changing a stock aircraft repaint or its shared texture files |
Entire [FS2004] folder | Textures, effects, configuration files and other simulator files | Best clean baseline before installing multiple add-ons |
The asterisk in texture* covers folders such as texture and named or numbered livery variants. Folder names are not case-sensitive in a normal Windows installation.
The mistake we see most often is backing up only [FS2004]\Texture. A replacement may instead modify an aircraft folder, a scenery subfolder or several locations. The instructions for a simple FS2004 grass texture replacement illustrate a single-file backup, while a multi-file water replacement package shows why the complete list of installed files matters.
A full installation-folder copy does not include every FS2004 preference stored under your Windows user profile. It is still sufficient as a clean source for the simulator's installed texture files.
How do I make a reliable FS2004 texture backup?
Make one untouched master copy of FS2004, then save the exact files affected before each later texture installation.
- Close FS2004 and its utilities. Do not copy or replace files while
fs9.exe, a scenery tool or the add-on installer is running. - Confirm the active installation folder. If you have more than one FS2004 installation, inspect the target of the shortcut you actually use. Backing up a different copy will not protect the live installation.
- Copy the complete folder. Put the clean copy outside the live FS2004 directory, preferably on another drive. Name it clearly, such as
FS2004 Clean Backup. If the simulator was already modified, this is a backup of that state rather than a source of guaranteed default files. - Read the add-on instructions before installation. Record every destination folder and preserve the original files with their folder structure. Broad packages, such as an upgrade replacing numerous airport surfaces, require more than a single-file backup.
- Keep a package-specific rollback copy. Store the original files in a folder named for the add-on and installation date. This avoids having to compare thousands of files later.
- Install one replacement package at a time. Start FS2004 and test it before adding another set. Otherwise, identifying which package produced a bad runway, black aircraft or mismatched night texture becomes much harder.
If FS2004 is installed under Program Files, Windows may require administrator permission to replace files. Legacy installers and editing tools can also be redirected to a per-user location under %LOCALAPPDATA%\VirtualStore. If an installation or restoration appears to work but FS2004 does not change, check both the real installation path and any matching VirtualStore path.
How do I restore default textures in FS2004?
Restore the smallest complete texture set that matches the problem, while removing any files added by the replacement package.
- Close FS2004 completely. Restarting the simulator is required because textures already loaded into a running session will not be replaced reliably.
- Identify the package and affected location. Re-read its instructions or file list. A single aircraft problem usually points to that aircraft's
texture*folder; widespread environment problems point to shared or world texture folders; one affected airport usually points to local scenery. - Preserve the modified version temporarily. Rename a dedicated add-on texture folder or move the changed files elsewhere. Do not rename an entire shared folder if it also contains unrelated add-ons.
- Copy back the matching originals. Restore them to exactly the same path and retain their original names. Use originals from the same FS2004 edition and update level.
- Remove package-specific additions. Copying originals over a modified folder does not delete extra files installed by the mod. Remove only additions identified in the package documentation; guessing can delete files needed elsewhere.
- Test the same conditions. Load the same aircraft, airport, season, weather, time of day and viewing angle. Day, night, winter and reflective variants may not appear under other conditions.
Do not copy the entire clean backup over a heavily modified installation unless you intend to roll everything back. A normal copy-and-overwrite operation leaves extra mod files behind, while replacing the whole live folder removes aircraft, scenery and other add-ons installed since the backup.
Use an add-on's uninstall or restore tool only when its documentation says that it saved and reinstates the original files. An uninstaller that merely removes its own files cannot recreate stock textures that were overwritten.
Can I restore just one texture file?
Yes, provided you know exactly which file was replaced and have the matching original from the same FS2004 installation state. Copy it back to the original folder and allow Windows to overwrite the modified version.
Many FS2004 texture packages contain related day, night, seasonal, alpha-channel or reflective variants. Restoring only one member of such a set can produce inconsistent colours, missing night lighting or surfaces that fail only in a particular season. When the package replaced several related files, restore the complete set together.
What if I never backed up the default textures?
FS2004 has no built-in file verification system that automatically downloads missing stock textures, so you need a matching clean installation, an installer repair option or a reinstall.
- Use an untouched matching installation. Copy the exact originals from the same FS2004 edition and update level. Do not substitute similarly named files from FSX, Prepar3D or another simulator.
- Use the original installer or distribution repair function. Availability depends on the release. A repair may replace more than the damaged textures, so preserve the existing installation first.
- Reinstall into a separate folder. This is usually safer than installing over the damaged copy because an in-place reinstall may leave added files behind. The separate clean installation can then supply the originals you need.
- Retain the damaged folder. It may contain third-party aircraft, gauges, scenery, effects or configuration files worth recovering after the stock installation works again.
Files on original installation media may be stored inside installer archives rather than as ordinary texture files. Use the installer or its repair function instead of manually extracting files unless the release documentation explicitly supports that method. If reinstalling on a newer system presents a separate problem, follow our practical steps for installing FS2004 on Windows 11.
Why did restoring the textures make no difference?
A restoration that produces no visible change usually targeted the wrong folder, the wrong FS2004 installation or only part of the replacement package.
- The shortcut starts another installation. Check the path to the active
fs9.exe, especially if you keep a clean copy alongside a modified one. - An active scenery layer supplies its own texture. A higher-priority add-on airport or regional scenery can continue displaying its local files even after you restore a stock world texture.
- Windows redirected the files. Check administrator permissions and the relevant VirtualStore location.
- Added files remain in the folder. Overwriting stock filenames does not remove extra files placed there by the mod.
- The replacement changed other file types. Some packages also modify effects or configuration files. Aircraft repaints may add or alter entries in
aircraft.cfg; restoring texture bitmaps alone will not repair a bad reference. - You restored an incomplete set. Mixing originals with another package's day, night or seasonal variants can leave the visible problem intact.
- You tested under different conditions. Select the same aircraft, location, season and time used when the fault appeared.
- The fault is not a texture replacement. A rendering problem affecting otherwise clean files may come from graphics settings, display drivers or a separate add-on rather than damaged default textures.