How to remove the old FSX before installing FSX-SE

Before you start with the installation of FSX-SE it is our recommendation to uninstall the previous FSX version. FSX is dead! Be happy with Steam! Read the easy way to remove your previous FSX installation.

  1. The easy way:
    1. Go to Start/Program and Features/ and select the previous FSX installation in Uninstall or change a program.
    2. Uninstall FSX and when you have FSX+SP2 installed, it will return with FSX-SP1. Check the version number.
    3. Now, uninstall again FSX; it will no longer be in the list of Programs and Features.
    4. Clean your registry with CCleaner or another registry cleaner and repeat the cleaning until there are  zero faults.
    5. The remaining folders in the still existing FSX installation folder contains important stuff that you added previously (FSUIPC Key, aircraft, add-on scenery, a.s.o.).
    6. Rename you rinstallation folder and move it to your backup location. You will need it later on.
    7. Reboot the system and ceck if all the previous registrations are gone in the registry; therefore use the TweakFSX Registry tool as mentioned HERE. Try to find the previous FSX path. If there’s nothing found, you’re clean and then install FSX-SE else you need to go into the registry manualy and delete the remaining registry entry as indicated in the tool. You will read the registry key as HKEY_LOCAL_MACHINE_SOFTWAREMicrosoft…and the installation path of y0ur previous installationtweakfs01
    8. How to get into the registry? In Windows 8 just type regedit @Start and hit ENTER
    9.  Only delete the registry entries shown here, when uninstalling boxed version of FSX.
      Once FSX:SE is then installed, this entry will be present again – so don’t delete it after the installation of FSX-SE! …
      Only delete it just 
      before you do a clean install of FSX-SEregedit02


How To Install FSX-Steam Edition

fsx-se-01Hello Captains, in this and coming articles we will inform you with tips and tricks about FSE-SE. Many thanks to our crew member Piejo who shared his early experiences with FSX-SE.

  1. How To Install FSX-SE as
    1. a Single Sim Setup (FSX-SE only) or
    2. a Dual Sim Setup (FSX + FSX-SE on one machine)
  2. What you should know:
    1. about Installers
      1. If you are not familiar with the requirements for a succesful deployment of your simulator, please read the related articles in our FSX-SE pages. When you have already FSX on board, you have 2 choices: either remove FSX from your PC and install FSX-SE as a Single Sim Setup (1.A. ) or install FSX-SE next to the already existing FSX installation (1.B. Dual Sim Setup).
        Note: You cannot run both sims the same time on one machine !

        1. with Single Sim Setup: FSX-SE will install as a normal FSX installation, using the standard registry path, folder and file names. No issues.
        2. with Dual Sim Setup: FSX-SE is fully separated from FSX and after installation you can use both sims. FSX is not effected. But…
          FSX-SE has its own registry values which results at the same time in a disadvantage for 3rd party FSX-Add-on-installers since they natively refer to the registry location of FSX and not to FSX_SE
          A 3rd party add-on that needs to use the fsx.cfg must have another reference since in Dual Sim Setup this file is called fsx-se.cfg (!)
        3. Based on the fact that FSX-SE will further develop, manufacturers from aircraft, sceneries and other add-ons will phase out FSX development and focus on this new market. This brings us to the recommendation: create a Single Sim Setup.
    2. about Registry issues
      1. If you need to adapt your registry path for any reason, this article and this article  will show you how to manage.
      2. the registry paths for FSX are named as HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft Games/flight simulator/10.0
        HKEY_CURRENT_USER/SOFTWARE/Wow6432Node/Microsoft/Microsoft Games/flight simulator/10.0
      3. the registry path for FSX-SE is named as HKEY_LOCAL_MACHINE/SOFTWARE/Dovetail/Games/FSX
    3. about Add-ons made for FSX
      1. FSX-Add-ons that use FSUIPC: you need an updated version of FSUIPC4 4.3939 or later which can be retrieved HERE.
      2. FSX-Add-ons like non stock aircraft and non-stock sceneries: will work without issues; beware of any installation registry issues (see 2.A.c.)
      3. FSX-Add-ons that use SimConnect:
        -with a Single Sim Setup: you should install the FSX SimConnect runtime libraries that can be found in the SDK folder in the FSX-SE installation. There you will read the legacy interface installers (.msi files).
        -with a Dual Sim Setup: without installing FSX SimConnect runtime libraries (that can be found in the SDK folder in the FSX-SE installation) none of the FSX Add-ons using the previous simconnect version of FSX-SP1-SP2-Acc_pack will work.
      4. FSX-Add-ons that use customized .DLL modules to access directly FSX memory locations: most of this type of existing .dll’s  don’t support FSX-SE and in that case will FSE-SE cause to crash.
      5. Add-ons that use customized .gau modules to access directly FSX memory locations: most of the existing .dll’s  don’t support FSX-SE and in that case will FSE-SE cause to crash.
      6. Our Recommendations:
        Remove the old FSX installation and start with FSX-SE.
        Read further @ 3.A.

  3.  Installation of a Single Sim Setup FSX-SE: (clean install)
    1. The advantage of this option is that FSX-SE, at installation, places a number of important files (fsx.cfg file,  DLL.XML, the Controls folder, the Shaders folders, the scenery.cfg file and other files which are being placed outside the FSX-SE root), in folders which have the same name as previously in FSX. Therefore FSX-Addons can more easily be installed in FSX-SE. These are the folder names:
      C:/Program Files (x86)/Steam/SteamApps/common/FSX) <- DEFAULT PATH C:/ProgramData/Microsoft/FSX
      C:/Users/<username>/Documents/Flight Simulator X Files
    2. Note for choosing a different installation path/disk
      1. Go to Steam – Settings – Downloads
      2. Below Content Libraries select Steam Library Folders which opens a window where you could create or select a (new) Library folder (even at a separate drive)
      3. Setup the appropriate folder  OR drive and folder where you want Steam to be installed.
    3. Install FSX-SE from STEAM
      1. Refer to par. 3.B. as to where you want it installed.
      2. Run the Sim once and reboot your PC. Continue with:
      3. Installing SimConnect library: Browse to  C:(Program Files (x86))Steam/SteamApps/common/FSX/SDK/Core Utilities Kit/SimConnect SDKlib and run the SimConnect.msi installer by double clicking.
      4. Installing SimConnect Legacy Interface: Browse to C:(Program Files (x86))Steam/SteamApps/common/FSX/SDK/Core Utilities Kit/SimConnect SDK/LegacyInterfaces/ and run the SimConnect.msi installer in each of the three sub-folders by right clicking omn the .msi file.
      5. Installing FSUIPC4: if your add-ons need it, download and install the latest version of FSUIPC4 4.939 or later.
      6. Done! Almost all installers for the FSX-Add-ons should revert to FSX-SE’s location, e.g. all add-on scenery should install into the (correct) scenery.cfg location. FSX addons that use both the new Steam Simconnect and the older Simconnect versions should work ok.

  4. Installation of a Dual Sim Setup FSX-SE (don’t do this!)
    If you did not follow our recommendation for the installation of a Single Sim Setup we will guide you through the installation steps to go.

    1. Install FSX:SE from STEAM then
      1. Refer to par. 3.B. as to where you want it to be installed.
      2. Run the Sim once and reboot your PC. Continue with:
      3. Installing SimConnect library: Browse to  C:(Program Files (x86))SteamSteamAppscommonFSXSDKCore Utilities KitSimConnect SDKlib and run the SimConnect.msi installer by double clicking.
      4. Installing SimConnect Legacy Interface: Browse to C:(Program Files (x86))SteamSteamAppscommonFSXSDKCore Utilities KitSimConnect SDKLegacyInterfaces, and run the SimConnect.msi installer in each of the three sub-folders by double clicking.
      5. Which folders result after installation of FSX-SE?
        After installation your PC will contain the following folders c.q. files:
        For FSX (those files already existed)
        C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X C:ProgramDataMicrosoftFSX C:Users<yourname>AppDataLocalMicrosoftFSX C:Users<yourname>AppDataRoamingMicrosoftFSX C:Users<yourname>DocumentsFlight Simulator X Files
        Registry keys:
        – HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Gamesflight simulator10.0
        – HKEY_CURRENT_USERSOFTWARE(Wow6432Node)MicrosoftMicrosoft Gamesflight simulator10.0
        For FSX-SE
        C:Program Files (x86)SteamSteamAppscommonFSX <- DEFAULT PATH
        C:ProgramDataMicrosoftFSX-SE   (scenery config file) C:Users<yourname>AppDataLocalMicrosoftFSX-SE   (shaders) C:Users<yourname>AppDataRoamingMicrosoftFSX-SE (FSX-SE.cfg, (fall-back)scenery.cfg, controls.cfg, DLL.XML).
        C:Users<yourname>DocumentsFlight Simulator X – Steam Edition Files
        Registry key (64bit o/s shown)
      6. Install Addons in FSX-SE
        In order to achieve that FSX addons will be installed correctly in FSX-SE, you have to do the following:
        – Download and install FSUIPC4 4.393 or later, if your addons need it.
        – Download TweakFS/FSRegUtil.

        Note: TweakFS Registry Utility has a small bug where the first time you use it and select the ‘Search Reg’ button, it will launch the Windows Registry Editor, but will not search for the FSX entry.   If this happens, simply close the Windows Reg Editor window (that has popped up) and go back to TweakFS Reg Utility and press the ‘Search Reg’ button again – it will work the second time, and will launch the registry and find your FSX entry.tweakfs01

        -You will need this since a FSX-installer of an add-on needs to know where FSX-SE is installed.
        -Save this utility program in your download folder and run it as Administrator, right clicking the exe file.
        – Now -before you run the add-on installer- Get the FSX path. (Tab Get Path, then press Get FSX Path)
        . In the sample below you see that FSX is installed directly on the D: drive. Now, you are going to change that path to where FSX-Se is installed.

        • Select “Set Path” tab and select your FSX-SE installation directory. Then select “Set FSX Path”.tweakfs02
        • After, check the “Add to Current User” checkbox and click “Set FSX Path” again.  In the sample below you see that FSX-SE is also installed on the D: drive.
        • Through this action an installer of an addon made for FSX can see that the addon must be installed in the folder and sub-folders where FSX-SE is installed.
        • However, you are not ready yet, because, during the execution of the add-on installer, there are also FSX-SE files in the folders mentioned above, which by a number of addons have to be adapted during their installation. These (3) folder names are:
          (namely the FSX-Steam scenery config file)
          (namely the FSX-Steam shaders)
          (namely the config file, the scenery config file, the Controls folders, and the XML config file for FSX-Steam).
        • In order to achieve that an installer of a FSX add-on can also correctly effect the necessary changes in the files in those folders, you need to temporarily change the names of the above mentioned  3 :: folders, otherwise the changes are not written (!)
        • So, if you also have a stock FSX installed too, this involves firstly to temporarily renaming the ‘FSX’ folder within the above file paths to something like ‘FSXbackup’.
        • Rename C:ProgramDataMicrosoftFSX into C:ProgramDataMicrosoftFSXtemp
        • Rename C:UsersyournameAppDataLocalMicrosoftFSX into
        •  Rename C:UsersyournameAppDataRoamingMicrosoftFSX into
        • Then simply change the ‘FSX-SE’ folder within the above file paths, to ‘FSX’. Now when you run any addon installer for FSX, the FSX Steam folders will be properly adapted.
        • Rename C:ProgramDataMicrosoftFSX-SE into C:ProgramDataMicrosoftFSX
        • Rename C:UsersyournameAppDataLocalMicrosoftFSX-SE into
        •  Rename C:UsersyournameAppDataRoamingMicrosoftFSX-SE into
        • It is essential that you change the names of these folders back to their original ‘FSX’ and ‘FSX-SE’ names, once you’ve finished installing scenery and before launching either FSX or FSX-SE ! 
        • Moreover, if you later on want to install an FSX-addon in FSX (not FSX-SE), do not forget to change the path back to FSX again from FSX-SE with the help of the TWEAKFS FSX REGISTRY UTILITY!
        • Of course going forward, these steps should eventually become redundant; once native FSX-SE addons are released via Steam (or even 3rd parties). They will have then native abilities to point to the correct Scenery.cfg files, and similarly, eventually it’s hoped that DTG / Steam will update FSX-SE to remove all Registry confusions between the sims.  What we really need until that time is a ‘switch’ that automatically changes all file paths (sim installation, fsx.cfg, scenery.cfg) according to which sim we want to install an add-on in to.

Flight Simulator X Gold Edition [en]

fsx-version1Flight Simulator X Gold Edition or Deluxe Edition:
The FSX Gold Edition contains three DVD’s and the last DVD (blue / gray) is the Expansion Acceleration Pack.
Disc 1 and Disc 2 are the same as in the Deluxe Edition.
Installing Acceleration is processed after disc 1 and disc 2 are installed.
A “clean install” of FSX Deluxe; this is the order of installation.

Install FSX by default on another disc then where the OS resides: e.g. D:/FSX

1. After installation of disc 1 and disc 2
Version number is 10.0.60905.0 (You can check this after you’re booted, from the Help)
Size: 13.0 GB (13.993.566.208 B) being 41964 files in 1358 directories.
If you want to install Acceleration as well, do it WITHOUT the Service Packs SP1 and SP2! Skip steps 2 and 3. Continue with step 4.
Our FSE Standard Configuration is FSX +SP1+SP2

2. Install SP1 (file name: fsx_sp1_ENU 208.0 Mb)

After installing, the version number increased to 10.0.61355 fsx_sp1.20070510-2038
OS: W7, Vista of XP_SP2
Size: 13,0 gB (13.975.834.624 B)  being 42016 files in 1358 folders.

3. Install SP2 (file name fsx_sp2_ENU 166 Mb)
After installing the version number increased to 10.0.61472 fsx_sp2.20071210-2023
Size: 13.2 GB ( B) being 42355 files in 1371 directories.
SP2 detects whether you have a standard version or a the Deluxe version and installs the proper files needed.

Use this set up as a default installation: FSX + SP1 + SP2

fsx64Since FSX is a 32 bits application and probably you run FSX on a 64 bits machine (W7-64 or W8-64) the fsx.exe executable will handle no more then 2 GB address space in the virtual memory. Therefore this file must be patched to let them use 4GB of virtual memory on x64 platforms.  READ HERE.

4. Installing FSX X
On the X DVD the Service Packs 1 and 2 are included; The version number is 10.0.61637.0

5. Downgrading of FSX X
When you want to remove FSX Acceleration X, the version number is set back to 61355 (read above).

Important note: in order to be able to multi-play in a Local network you MUST install SP2 to a version of 61472.
After removing FSX-X you are missing the additional airplanes. See the list on Wikipedia

IMPORTANT NOTE: the SP2 update does not contain the code that can control the airplanes in FSX-X. Therefore it is not done to copy/paste those airplanes folders from other sources into the ../Simobjects/Airplanes folder. The Aircraft supplied with FSX X only run with the acceleration pack. In community flying in a local area network or via WAN (INTERNET) sometimes FSX will crash when the versions  used by other captains are not equal or an aircraft is used that is developed for FSX X. Remember that there are 3 different versions of fsx.exe
So check the version you are running now in the root of FSX: »
either d:/FSX or
C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/.
Find the fsx.exe file, right click and select Properties

Downgrade FSX-X naar FSX-SP1-SP2.

Flight Simulator X  Gold Edition of  Deluxe Edition:
in de FSX Gold Edition vind je 3 DVD’s; de laatste DVD (blauw/grijs) is Acceleration Expension Pack.

Disc 1 en disc 2 zijn gelijk aan de Deluxe Edition.

Het installeren van Acceleration doe je nadat disc1 en 2 zijn geinstalleerd.

Een ‘clean install’ van FSX Deluxe levert dit in volgorde van installatie op:
1. Na installatie van disc 1 en 2
Versienummer is 10.0.60905.0 (Dit kan je controleren nadat je opgestart bent via de Help)
Grootte: 13,0 Gb (13.993.566.208 B) zijnde 41964 bestanden in 1358 mappen.

Wanneer je Accelereation wilt installeren doe dat dan ZONDER de servicepacks sp1 en sp2! Sla stap 2 en 3 over.

2. SP1 installeren (bestandsnaam: fsx_sp1_ENU 208.0 Mb)
Na installeren is het versienummer verhoogd naar 10.0.61355 fsx_sp1.20070510-2038
OS: W7, Vista of XP_SP2
Grootte: 13,0 gB (13.975.834.624 B) zijnde 42016 bestanden in 1358 mappen.

3. SP2 installeren (bestandsnaam fsx_sp2_ENU 166 Mb)
Na installeren is het versienummer verhoogd naar 10.0.61472 fsx_sp2.20071210-2023
Grootte: 13,2 Gb ( B) zijnde 42355 bestanden in 1371 mappen.
SP2 detecteert of je een Standard versie of een Deluxe versie hebt en installeert dan naar behoren die bestanden die nodig zijn.

4. Installeren van FSX-X
Op de DVD FSX-X zitten de servicepacks 1 en 2.
Het versienummer is dan 10.0.61637.0

Onze FSE  standaard is vastgesteld op FSX + SP1 + SP2
De reden is dat er (3rd party) aircrafts zijn die wel draaien op versie 61637 maar niet op 61472. In multiplay kan dit mogelijk aanleiding zijn tot errors omdat er dus FSX-X aircrafts worden aangeroepen door een SP2 versie. Om deze situatie te ondervangen is deze downgrade van belang.

5. Downgraden van FSX-X
Wanneer er een downgrade plaatsvindt van FSX-X door Acceleration te verwijderen, wordt het versienummer teruggezet op 60905 of 61355. Dit is afhankelijk hoe de software eerder geinstalleerd is geweest.
Let dus op wat de uitkomst is na het de-installeren.
60905 is FSX zonder servicepacks
61355 is FSX met SP1
61472 is FSX met SP2
Je hebt SP2 nodig om LOCAL  te kunnen netwerken .

Dit kan je tegenkomen bij de de-installatie:

1.Ga naar Configuratiescherm/software. Daar zie je het programma Microsoft FlightSimulator FSX-Acceleration staan.

2.   Klik hierop en kies voor verwijderen!!! Wees niet ongerust: alleen Acceleration wordt nu gede-installeerd. FSX blijft gewoon bestaan. Laat dit proces helemaal afronden.

3.   Start FSX op en nu zie je dat de sceneries opnieuw worden geladen. Controleer even of FSX nu gewoon goed draait door een default vluchtje te maken.

4.   Sluit FSX af en reboot je PC. (afsluiten en opnieuw opstarten)
4a. Het kan zijn dat er een error optreed en dat FSX niet start. Geen nood, gewoon doorgaan met 5.  Controleer in het configuratiescherm/software welke versie van FSX er nu staat: 60905 of 61355

5.   Installeer nu FSX-SP1 opnieuw. Dit is om er zeker van te zijn dat SP1 volledig (her)geïnstalleerd is. SP1 is te downloaden op onze Server;

6.   Start FSX op en nu zie je dat opnieuw de sceneries opnieuw worden geladen. Controleer even of FSX nu gewoon goed draait door een default vluchtje te maken.

7.   Sluit FSX af en reboot je PC. (afsluiten en opnieuw opstarten)
Controleer het versienummer; als het versienummer 61355 luidt, installeer dan SP2. Is het een lagere versie, dan moet alsnog SP1 gedraaid worden.

8.   Installeer nu FSX-SP2.  SP2 is te downloaden op onze Server

9.   Start FSX op en nu zie je dat weer opnieuw de sceneries opnieuw worden geladen. Controleer even of FSX nu gewoon goed draait.

Om local network te kunnen multiplayen MOET er SP2 geinstalleerd zijn en komt de versie op 61472. Controleer dit in het configuratiescherm/software

Wat je mist zijn dan de extra aircrafts gemerkt als NO in het lijstje op Wikipedia

Tot slot: in de update van SP2 zit niet de code die de aircrafts van FSX-X kan aansturen. Die aircrafts moet je dus niet als folder kopieren naar de Airplanes folder met de gedachte deze op SP2 te kunnen gebruiken. Wellicht kan het eerste resultaat bevredigend lijken als single user, maar in multiplay kan dit problemen veroorzaken.

En nog deze:
vergeet niet de databasemanager van FSCommander te refreshen…