How do I install the FS9.1 update and patches for Microsoft FS2004?

To update Microsoft Flight Simulator 2004 (FS2004 or FS9), close the simulator, back up its files, restore the original 9.0 core files, and install the official FS9.1 update into the folder containing fs9.exe. Verify that version 9.1 starts correctly before reapplying executable modifications or testing third-party add-ons.

Which FS2004 patch do I need?

The official FS9.1 update is the final base-simulator patch for Microsoft Flight Simulator 2004: A Century of Flight. A standard 9.0 installation updates directly to 9.1; there is no earlier service-pack chain to install first.

Do not confuse an aircraft patch, no-CD executable or 4GB patch with the official FS2004 update. FS9.1 patches the core simulator; it does not modernise navigation data, update airports or repair every third-party add-on.

Where can I download the FS9.1 update?

We host the official updater on our archived FS9.1 installer and file-notes page. Download the package to a normal local folder and extract it before running the installer.

For readers asking dove lo posso scaricare? — “where can I download it?” — that file page is the download location. Use the package intended for FS2004, not an update for FSX or a later Microsoft Flight Simulator.

How do I install the FS9.1 update?

FS9.1 should be installed over a working, unmodified FS2004 9.0 installation before optional executable replacements.

1. Locate the installation you actually launch. Check the target in the FS2004 shortcut. The correct root folder contains fs9.exe alongside folders such as Aircraft, Modules and Scenery. This matters if more than one copy is installed.
2. Check the existing version. If the simulator already reports 9.1, do not run the official updater again. Update individual add-ons separately when their documentation requires it.
3. Close FS2004 and its utilities. Exit weather engines, traffic programmes, flight planners and any other tool that could have a simulator file open.
4. Back up the installation. If space permits, copy the complete FS2004 folder. At minimum, preserve customised aircraft, Addon Scenery, the active scenery.cfg, saved flights and the user configuration under %APPDATA%\Microsoft\FS9.
5. Restore original 9.0 core files. Replace a modified or no-CD fs9.exe with the original 9.0 file. A 4GB patch also modifies the executable and can make the official updater reject it. Other replaced core files may cause the same failure.
6. Extract the downloaded package. Do not launch the updater from inside a compressed archive or a temporary preview window.
7. Run it with appropriate permission. On a Windows installation protected by User Account Control, use the administrator option. If the installer asks for a destination, select the root folder containing the active fs9.exe; do not select the desktop, an add-on folder or the archive-extraction folder.
8. Allow the update to finish. Do not start FS2004, install scenery or copy files into the simulator directory while the updater is working.
9. Verify a clean start. Confirm version 9.1, then load a default aircraft at a default airport before restoring optional modules or testing add-ons.

A mistake we see repeatedly is patching one FS2004 directory while the desktop shortcut launches another. Check the shortcut target both before and after updating rather than relying on the folder name alone.

How can I check whether FS2004 is updated to 9.1?

Open Help > About Microsoft Flight Simulator and confirm that the displayed version begins with 9.1. You can also inspect the version details of the particular fs9.exe named in the active shortcut.

Checking both locations helps identify an old shortcut or a second installation. An executable replacement can also make file-version checks less reliable, so verify the official patched installation before adding one.

What does the FS2004 4GB patch do?

A 4GB patch marks the 32-bit fs9.exe as Large Address Aware; it is not an official FS9.1 update and does not convert FS2004 into a 64-bit simulator.

On 64-bit Windows, the flag can let FS9 use more virtual address space than the usual 2GB limit. It is most relevant when complex scenery, high-resolution textures or gauge-heavy aircraft cause out-of-memory crashes. It does not add physical RAM, guarantee access to a full 4GB or provide a general frame-rate increase.

Choose it for a documented memory problem, not as a cure for every crash or start-up failure. Its benefit is much more restricted on 32-bit Windows and may depend on operating-system configuration.

The safe order is FS9.1 first, final executable replacement second, 4GB patch last. Back up the working 9.1 executable before changing it. If you own the original media and use a replacement for legacy disc checking, consult our version-matching notes for the optional FS9.1 no-CD executable; a 9.0 replacement does not belong in a 9.1 installation.

Why will the FS2004 patch not install?

Most FS9.1 failures come from a modified core file, the wrong installation path, insufficient write permission or an updater that does not match the installed copy.

アップデートされない: the FS9.1 update will not install

If the update is not applied, match the installer’s behaviour to these common causes:

• Old file not found or file contents do not match: restore the original 9.0 fs9.exe and any other modified core files. No-CD and 4GB changes must be removed before applying FS9.1.
• FS2004 cannot be found: Windows may have an outdated installation path because the simulator folder was copied or moved manually. Do not guess at registry changes; repair or reinstall the base simulator so its location is registered correctly.
• Access denied or files are in use: close the simulator and all related utilities, then run the extracted updater with administrator permission.
• Wrong version or language: do not force an updater that reports an incompatible installation. Confirm that the package and installed copy are both for Microsoft Flight Simulator 2004 and use a compatible language edition.
• Nothing happens (“nada”): make sure the package was fully downloaded and extracted. Check whether Windows security has blocked or quarantined the known updater rather than repeatedly launching it from the archive.

The installer finishes, but FS2004 still shows 9.0

The patch was probably applied to a different FS2004 folder. Inspect the shortcut target, find the fs9.exe it launches, and compare that location with the path used by the updater.

If both paths match, check whether an old 9.0 executable was copied back after installation. Restoring a complete pre-patch backup over FS9.1 can silently produce a mixture of 9.0 and 9.1 files.

起動しない: FS2004 will not start after patching

If FS2004 will not start after the update, return it to the official patched state before investigating add-ons.

1. Check the shortcut. Confirm that it points to the updated installation and try starting that folder’s fs9.exe directly.
2. Undo later executable changes. Restore the backed-up official 9.1 executable if a no-CD or 4GB modification was applied immediately before the failure.
3. Remove third-party modules temporarily. Move recently added DLL files out of Modules, then test again. Older utility modules can fail before the main FS2004 window appears.
4. Regenerate the configuration. Rename fs9.cfg under %APPDATA%\Microsoft\FS9 rather than deleting it. FS2004 creates a fresh file on the next start, although graphics, control and preference settings will need to be restored.
5. Test only default content. Start with a default aircraft and airport before reintroducing modules, scenery and aircraft in small batches.

Some modern Windows installations block the legacy disc-checking component used by the original release. If the simulator specifically fails at the disc check, that is separate from the FS9.1 patch itself; any replacement executable must still match version 9.1.

Will FS9.1 remove my aircraft and scenery?

The official update normally leaves the Aircraft and Addon Scenery folders in place, but it can replace core simulator files. A backup protects customised configuration and makes it easier to separate patch changes from older add-on changes.

Do not copy an entire 9.0 backup over the patched installation. Restore only the aircraft, scenery and configuration files you need, using our folder-by-folder FS2004 add-on instructions where the package lacks clear directions.

If the original core files cannot be recovered, the dependable repair order is to back up add-ons, remove or rename the remaining modified installation folder, reinstall FS2004 from the original media, launch it once, close it, apply FS9.1, verify a default flight and then reinstall add-ons in small batches. Test between batches so the first incompatible component is easy to identify.