How do I fix FSX installer error 1603?

FSX installer error 1603 is a generic Windows Installer “fatal error”, not one specific Flight Simulator X fault. Restart Windows, remove any partial FSX installation, clear temporary files, check free space and destination permissions, then run boxed Setup.exe as administrator—or verify Steam Edition’s files and retry the prerequisite that actually failed.

What does FSX error 1603 mean?

Error 1603 means Windows Installer rolled back the installation because one of its actions failed. The code alone does not identify whether the cause was an existing FSX installation, damaged media, an inaccessible folder, security software or a failed prerequisite.

A mistake we see constantly is repeatedly running the installer without checking where it stops. If it fails at the same file or percentage each time, that detail is usually more useful than 1603 itself.

Which FSX installer is actually failing?

The correct repair depends on whether 1603 comes from boxed FSX, FSX: Steam Edition or a separate add-on.

How do I fix error 1603 in boxed FSX?

For boxed Flight Simulator X, a clean installer state and a writable local destination solve the most common 1603 failures.

1. Restart Windows. This clears a pending installation, locked file or unfinished Windows update. Do not run another installer before retrying FSX.
2. Remove a partial FSX installation. Open Installed apps or Programs and Features and uninstall Microsoft Flight Simulator X and Acceleration entries left by the failed attempt. Restart afterwards. If an old FSX folder remains, back up any add-ons and rename the folder rather than deleting registry entries manually.
3. Clear the temporary folder. Press Windows key+R, enter %TEMP%, and delete the files Windows allows you to remove. Skip anything reported as in use. Check free space on the Windows drive as well as the FSX destination because the installer extracts files to the temporary directory.
4. Check the destination. Install to a local drive, not a mapped network drive, substituted drive, compressed folder or encrypted folder. For a custom FSX directory, confirm through Properties and Security that SYSTEM and the Administrators group have full control. Do not grant Everyone full control or change permissions across the whole system drive.
5. Run the correct launcher. Right-click the boxed edition’s Setup.exe and select Run as administrator. Do not bypass it by opening an MSI file buried inside the installation media; the launcher may need to install prerequisites and pass FSX-specific properties.
6. Check security blocks. If the log reports access denied, allow the installer through Controlled folder access or other endpoint protection. Re-enable normal protection immediately after testing rather than leaving it disabled.
7. Complete the installation in order. Install base FSX and launch it once before adding Acceleration or service packs. Our explanation of the correct boxed FSX service-pack order covers which updates apply; boxed patches must not be installed over Steam Edition.

If setup always stops while reading the same CAB or source file, test whether Windows can copy the DVD’s contents without a read error. A dirty, damaged or incomplete source commonly produces Error 1335 alongside 1603; use our disc and CAB-file troubleshooting steps in that case.

How do I fix error 1603 in FSX: Steam Edition?

Steam Edition does not use the original boxed FSX installer, so boxed-disc cleanup and service-pack procedures are the wrong fixes.

1. Verify the installation. Open FSX’s properties in Steam, select Installed Files and verify the game files. Back up deliberate modifications to original FSX files first because verification can restore the official copies.
2. Identify the failed package. If 1603 appears during first-time setup, note the prerequisite named in the window. The failing installer may be a runtime component rather than FSX itself.
3. Repair only that prerequisite. Check Installed apps for the named component and use its repair option when one is offered, restart Windows, then let Steam retry it. Do not remove every Microsoft runtime package; different applications can require different releases side by side.
4. Check the Steam library folder. A library on an inaccessible, compressed or permission-damaged drive can produce the same fatal error. Confirm that your Windows account and SYSTEM can write to that library.

If 1603 is displayed by an add-on installer, confirm that it has detected the actual Steam Edition root directory. Verifying FSX will not repair a separate aircraft or scenery installer.

How do I find the real cause in the installer log?

The Windows Installer log normally reveals the failed file, folder, prerequisite or custom action hidden behind error 1603.

1. Reproduce the error once. Note the exact time and any file or component shown immediately before setup rolls back.
2. Open the temporary directory. Press Windows key+R, enter %TEMP%, and sort the files by date modified. Open the newest installation logs created at the failure time.
3. Search for the failure marker. Look for Return value 3 and inspect roughly 20–30 lines above the first relevant occurrence. Entries written later may describe the rollback rather than the original fault.
4. Check Event Viewer if no log is obvious. Under Windows Logs and Application, look for an MsiInstaller event stamped at the failure time.

• Access denied or Error 5 points to destination, temporary-folder or security permissions.
• Another installation is in progress means a restart or completion of the other installer is required.
• Already installed or another version points to an existing FSX or prerequisite registration.
• Cabinet, CRC or read errors indicate damaged installation media or an incomplete source.
• Custom action failed identifies a prerequisite or script that needs separate attention. If the installer reports 1722, follow our FSX custom-action repair procedure.

If setup fails before Windows Installer starts and reports InstallShield 1607 instead, that is a different setup-engine problem covered by our InstallShield initialisation fixes.

What if FSX error 1603 keeps returning?

If other MSI-based applications also fail, repair Windows Installer and Windows system files; if only FSX fails, return to the FSX log and installation source instead.

1. Check the Windows Installer service. Run services.msc and make sure Windows Installer is not Disabled. It is normal for the service to remain stopped until an MSI package needs it.
2. Re-register Windows Installer. From an administrator Command Prompt, run msiexec /unregister followed by msiexec /regserver, then restart Windows.
3. Repair Windows files. On Windows 10 or 11, run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow from an administrator terminal. Let each command finish before restarting.
4. Test a new local administrator account. If FSX installs there, the original Windows profile has damaged temporary-folder or installer permissions.

Do not delete C:\Windows\Installer, use a registry cleaner or apply blanket permission changes to Program Files. Those shortcuts can break uninstallers and updates for unrelated software while leaving the actual 1603 cause untouched.