Hi Bernardo.

I felt I needed to add some more info to my previous reply.

First registry location: HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0 -

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0]
"FIRSTRUN"=dword:00000001
"AppPath"="F:\\Flight Simulator X\\"
"MicrosoftAppDataComponent"=dword:00000001
"FsxCfgExtraCache"=dword:00000001
"FsxStandardXmlExtraCache"=dword:00000001
@="F:\\Flight Simulator X"
"SetupPath"="F:\\Flight Simulator X"

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0\Launch]
"F:\\Flight Simulator X\\Modules\\LVLD.dll.number removed to prevent piracy"=dword:00000001

Second registry location:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\microsoft games\flight simulator\10.0 -

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\microsoft games\flight simulator\10.0]
"LangID"=dword:00000409
"CDPath"="G:\\"
"SetupPath"="F:\\Flight Simulator X\\"
"PID"="number removed to prevent piracy"
"CurrentXPackProductCode"="{number removed to prevent piracy}"

FSX Path Fix. Now. If you used the fsx_path_fix.bat (MSDOS batch file) that is available from Captain Sim Support. This is what it has inside it:

@echo off
if exist "%CD%"\fsx.exe (
REG ADD "HKLM\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0" /v SetupPath /t REG_SZ /d "%CD%"\ /f
) ELSE (
echo Please make sure you run this file from your FSX root folder.
echo Currently the file is located in wrong folder: "%CD%"
)
@pause

The bold text part fixes (by finding fsx.exe, it verifies the location and then adds that same location to the registry) in only one part of the second registry location, HKLM (HKEY_LOCAL_MACHINE) above. It does not alter the first one. From what I can figure, some add-ons read more than just the SetupPath and so there is a conflict of locations. One is saying C:\FSX the other is saying C:\Program Files...etc. See what I mean? The free FSX registry tool from Flight 1 does the same thing. If I modify them all (after backing up of course) and then use either tool, they don't all get fixed. If you do a completely NEW installation of FSX Gold and select C:\FSX as the location to install it, they will all match up, leading to there being less likelihood that you will get errors.

The Windows registry is very complex, and although both the path fixes can be of great help, they are not perfect. There are a lot of other little bits of information throughout the registry that FSX adds to it during the installation. Most are minor, they don't care WHERE FSX is installed, they just need to know that it IS installed. Others have to know that FSX IS installed and WHERE it is installed.

Don't worry too much if you find this confusing. It is a LOT of information to try to understand fully. I am doing this is to try to show you the importance of selecting the location to install FSX Gold at the beginning. So you don't go: "OH sh*t! I forgot to select the location at the beginning. I'll just move it and use the registry fix and it will be fine." As you can see, it might NOT be fine at all.

Mark

For Captain Sim. I hope you don't mind my divulging the information inside the fsx_path_fix.bat file.