FSX Deluxe reinstall fails with error 1700 and 1630 after working initially

George,

Those two codes usually point to Windows Installer getting itself into a bad state for that product (either a corrupted install database/cache, or a “half-uninstalled” FSX entry that keeps tripping the next install). Since it did install and run initially, I’d focus on cleaning up the existing MSI/installer traces and then reinstalling in the most “vanilla” way possible.

Step-by-step cleanup + reinstall (FSX Deluxe)

1) Remove any leftover FSX folder(s)
After uninstalling, check and rename/delete leftover folders (they can confuse repairs/reinstalls):

• The FSX install folder you originally chose (often C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\)
• Your FSX config/save folder (don’t delete blindly if you want to keep files—rename it first):
  C:\Users\<YourUser>\AppData\Roaming\Microsoft\FSX\

2) Make sure Windows isn’t still “holding” an FSX install
Go to Windows “Apps & features” / “Programs and Features” and confirm everything FSX-related is gone (FSX, Acceleration if you had it, SDK entries, etc.). If there’s an entry that won’t uninstall, that’s often the root of 1700/1630.

3) Reboot (important)
Don’t skip this—Windows Installer changes often don’t fully clear until a restart.

4) Copy the DVDs to a local folder and run setup from the hard drive
Optical read hiccups can produce weird MSI failures (and it’s very common on newer PCs).

• Create something like C:\FSX_DVD1\
• Copy the entire DVD1 contents to that folder
• Right-click setup.exe and choose Run as administrator

5) Install outside “Program Files (x86)”
On modern Windows, the old FSX installer + permissions/UAC can cause headaches later. I typically use something simple like:
C:\FSX\

6) Temporarily disable 3rd-party antivirus “real time” scanning
Just for the install. Turn it back on after.

If it still fails: what I need from you
The exact fix depends on where in the installer it breaks. Can you reply with:

• Your Windows version (Windows 10/11, and if you know it, 64-bit)
• At what point does it fail (right when you start setup, during “publishing product information,” near the end, etc.)?
• The full text of the 1700/1630 message(s) (a screenshot is fine), and whether it’s 1700 first or 1630 first
• Are you installing from original discs, or a downloaded installer?
• Did you ever install SP1/SP2 or Acceleration on this machine before it stopped launching?

Once I have that, I can tell you whether we’re dealing with a broken uninstall entry that needs to be removed before the MSI will cooperate, or if it’s dying due to media/read/permissions.