How do I update FSX and which service packs do I need?
To update FSX, identify your edition first. Boxed FSX Standard or Deluxe without Acceleration needs Service Pack 1 followed by Service Pack 2. A boxed Acceleration installation uses Acceleration in place of standalone SP2. FSX: Steam Edition updates through Steam and must not be given the boxed service packs.
Which FSX update path should I use?
The correct update path depends on whether you have boxed FSX, the Acceleration expansion, or FSX: Steam Edition; Standard versus Deluxe does not change the basic service-pack order.
| FSX edition | Correct update order | Do not install |
|---|---|---|
| Boxed Standard or Deluxe without Acceleration | Base FSX, SP1, then SP2 | SP2 before SP1 |
| Boxed FSX with Acceleration, including Gold | Base FSX, SP1, then Acceleration | Standalone SP2 after Acceleration |
| FSX: Steam Edition | Updates supplied through Steam | Boxed SP1, SP2 or Acceleration patches |
For an unpatched boxed installation, start with our SP1 package and installation guidance. If you are not installing Acceleration, follow it with the standalone SP2 package and prerequisite notes.
Acceleration includes a later FSX core as well as additional aircraft, scenery and missions. It replaces standalone SP2 in the recommended installation sequence, but it is not identical to SP2: an add-on that specifically requires Acceleration may not work with SP2 alone.
There is no official SP3 for boxed FSX. SDK service packs are only needed by people using the Deluxe SDK to develop add-ons, and the SDK version must match the installed simulator. Random replacement executables and DLL files advertised as general FSX updates are not substitutes for the official patches.
How do I install the FSX service packs in the correct order?
A clean core installation patched before adding aircraft, scenery or utilities gives the fewest problems.
- Identify the edition. Confirm whether FSX came from boxed media, includes Acceleration, or is installed through Steam. Do not decide from the installation folder alone.
- Back up modified files. Save your configuration, scenery library data and any default aircraft or scenery files you have changed. Service packs normally preserve settings, but a repair or reinstall may not.
- Run boxed FSX once. Complete installation and activation, start the simulator, load a flight, close it normally and restart Windows if the installer requests it.
- Install SP1. Close FSX and run the SP1 installer with administrative permission. Start FSX once after the update so it can complete its configuration.
- Choose the final branch. Install standalone SP2 if you are keeping Standard or Deluxe without Acceleration. If you own Acceleration, install that after SP1 and omit standalone SP2. Some Gold media handles prerequisites during setup; allow its installer to do so rather than adding SP2 afterwards.
- Test before restoring add-ons. Load a default aircraft at a default airport. Confirm that the simulator starts and flies before reinstalling modules, gauges, AI traffic or scenery.
FSX: Steam Edition needs none of those manual steps. Let Steam finish pending downloads; if core files appear damaged, use Steam's Verify integrity of game files command. Back up modified default files first because verification can replace them.
How can I check which FSX patch is installed?
The FSX build number identifies the update level of a boxed installation.
Press Alt if the menu bar is hidden, open the Help menu and view the About information. The principal boxed builds are:
10.0.60905.0— original unpatched FSX10.0.61355.0— Service Pack 110.0.61472.0— Service Pack 210.0.61637.0— Acceleration
Acceleration branding and its extra content provide another clear check. For Steam Edition, let Steam manage the installed build rather than comparing it with boxed version numbers.
What should I do if an FSX patch fails or an add-on stops working?
Most FSX update failures come from using the wrong installer, applying patches out of order, or patching core files that an add-on has already altered.
- “FSX is not installed” or “product not found”: make sure the patch matches boxed FSX rather than Steam Edition, start the base simulator once, and check that the installed language matches the package. A damaged installation or missing registry entry may require a repair.
- SP2 refuses to install: verify that SP1 completed successfully. SP2 expects the SP1-level boxed installation and should not be applied to Acceleration or Steam Edition.
- The installer rolls back or reports changed files: restore original FSX files, remove the add-on that replaced them, or repair the base simulator. On a heavily modified installation, reinstalling FSX and patching it before restoring add-ons is usually cleaner.
- An aircraft or utility fails after patching: check whether it targets SP2, Acceleration or Steam Edition. These editions have different executable, SimConnect and registry expectations; our guide to boxed and Steam Edition add-on compatibility explains the practical differences.
- A suggested fix replaces system DLLs: do not treat files such as
simconnect.dll,uiautomationcore.dllor a downloadedfsx.exeas universal updates. Use such fixes only for a diagnosed problem and keep the original files.