fsx-se FSX Steam Edition creates "FSX-SE" folders instead of "FSX"

[barrel_owl 304]

For the sake of accuracy, shouldn't that be HKEY_CURRENT_USER and not HKEY_USERS?

 

regards,

Joe

 

Hi N69JBravo,

actually I have both:

 

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

 

HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator

HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

 

In both cases, the value for the key "Co-Existence" at the "Flight Simulator - Steam Edition" level is set to "0", which makes FSX Steam Edition to install properly in standalone mode, which was the goal of my initial help request. Now, the problem I am currently facing is that there are two pair of keys under "CURRENT_USER" and "USERS", as you can see yourself. Although all of them are set to the correct simulator path ("C:\Program Files (x86)\Steam\steamapps\common\FSX"), FSUIPC 'gets mad' because it detects both and assumes that the first is FSX classic. I guess I have to carefully delete one of these keys, but I would need some support from Steve, Pete or you, if you think you know the correct step.

 

Thank you anyway for your input.

[jandjfrench 3]

Hi Jim Barrett,

I wasn't familiar with who claimed what.  My skepticism was based on having been burned too many times when people have stated their suppositions as fact.  I made it very clear that that my perception was a guess and I was attempting to check this out personally.  I just re-read my post and if you kind of skip over the "guess" part it does come off as being offensive.  This was never my intention.

Jim F.

[barrel_owl 304]

OK I finally got rid of all double entries in the registry and reinstalled FSX Steam smoothly in standalone mode without further hiccups.

The installation of FSUIPC and Ezdok was also successful. I've also just installed FTX Global. FTX Central is pointing to "scenery.cfg" in the correct folder.

 

Thank you very much to all of you for your support and insights.

[JRBarrett 3,034]

Hi Jim Barrett,

I wasn't familiar with who claimed what. My skepticism was based on having been burned too many times when people have stated their suppositions as fact. I made it very clear that that my perception was a guess and I was attempting to check this out personally. I just re-read my post and if you kind of skip over the "guess" part it does come off as being offensive. This was never my intention.

Jim F.

Not a problem. In any case, it appears the OP has successfully cleaned his registry and has gotten SE to install in true FSX mode

[barrel_owl 304]

Not a problem. In any case, it appears the OP has successfully cleaned his registry and has gotten SE to install in true FSX mode

 

Yes, despite all work it required and the frustration I felt at some point, I must admit I really learned lots of things.

Here are two basic hints for those who want to switch from FSX boxed to FSX Steam without reformatting the disk:

 

1. As said, make sure that the key "Co-Existence" in the node "HKEY_USERS\...\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition" is set to "0" and not to "1". This will make FSX Steam to install in FSX mode (single installation).

2. Before installing FSX Steam, it is essential to remove each and every entry in the Registry related to any previous FSX-MS and FSX-SE installation. Search for "Flight Simulator" or "Steam edition" to make sure you find all keys, in particular in the node "Wow6432Node". Remove all occurrences. If you leave an entry, you can have FSX Steam installing in single mode by setting the "Co-Existence" key to "0", but you will have problems later handling addons like FSUIPC or Ezdok, among the others. Such tools look at the registry when you install them. If they find two items in the Registry, they will assume that FSX boxed is installed in parallel mode along with FSX Steam on your system, no matter if it is not and no matter if the duplicate key is pointing to the correct FSX Steam folder. Therefore, they will act accordingly searching for "FSX-SE" folders on your system, which obviously results in an installaton error.

[SteveW 1,792]

"HKEY_USERS\...\Software"

 

You have to find your base hive so that the setting is changed in all HKEY_CURRENT_USER hives.

 

If you think that Pete Dowson and Father Bill (N4GIX) - who are both recognized experts in FSX programming are "blowing smoke"

I wasn't familiar with who claimed what.

Actually I was providing the answers at the time of the comment, and you knew that. I felt it unnecessary for you to be rude, or make any comments on a technical basis, since you had absolutely no idea what you were talking about, and had tested nothing for yourself anyway.

[Dougal 165]

I know this thread is old, but I'd just like to thank all the contributors, as I was having a lot of issues getting it right.

[skysurfer 76]

Good day all. 

I am a bit late here but I have to ask for advice.

 

I have absolutely new built system (W10 Pro, FSX-SE). Boxed version has never been installed, however after installation I found two folders in App data/Roaming: FSX and FSX-SE. As far as I know it should be only FSX folder. I read here that for clean Steam install FSX-SE folder should not be created, but I have it for some reason.

 

Thx  

[Pete Dowson 558]

OK I finally got rid of all double entries in the registry and reinstalled FSX Steam smoothly in standalone mode without further hiccups.

I thought I knew all this stuff, and went through all the steps --

 

Uninstalling FSX and FSX-SE using "Programs and Features" in the control panel

Deleting everything in the registry mentioning Flight Simulator, Dovetail, everything there I could find.

Deleting all of the FSX and FSX-SE folders in ProgramData Microsoft folders, and AppData Local and Roaming Microsoft folders

Deleting the Flight Simulator X Files and the equivalent Steam Edition files.

 

Yet when I get Steam to re-install, and I run FSX from there, it STILL creates the separate FSX-SE folders and Registry entries! It STILL thinks there's an MS FSX installed. Why? What the **** can it be detecting?

 

I spent a whole day on this. Having now finished with FSX-MS I just thought I'd like to tidy my main flying PC up, but I'm in more of a mess now than when I started!

 

Can anyone say what I might have missed, please?

 

Pete

[barrel_owl 304]

Hi Pete,

I only see three possible explanations:
 

1) you failed to completely remove each and every entry from the registry. Make sure all these entries are "clean":

 

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition
HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator
HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight simulator\10.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\DovetailGames\FSX
HKEY_USERS\....\Software\Wow6432Node\Microsoft\Flight simulator\10.0
HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Flight simulator\10.0

 

2) You left the "Co-Existence" value under

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

on "1". Make sure it is set to "0".

 

3) You still have some old addon pointing to a ghost simulator folder.

 

I even wrote a guide (in Italian, sorry) on another forum about how to install FSX Steam on the same disk without formatting. It worked for everyone, it must work for you too.
Let me know.

[Mike777 163]

 

 

I spent a whole day on this. Having now finished with FSX-MS I just thought I'd like to tidy my main flying PC up, but I'm in more of a mess now than when I started!

 

Hi, Pete

 

Thanks for all your service to the flightsimming community!

 

In another thread it appears that the PMDG 777 and/or the PMDG NGX may be creating an FSX-SE folder in Documents, even when only FSX-SE is installed.  So if you have recently reinstalled one of them, perhaps the installer is creating these folders as well.  This may be a problem with any addon that is designed to work with FSX-SE.

 

Mike

[Pete Dowson 558]

1) you failed to completely remove each and every entry from the registry. Make sure all these entries are "clean":

 

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator

  Check, did that

 

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

  Check, did that

 

HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator

HKEY_USERS\.....\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

   No such entries in HKEY_USERS (same as on my Development PC which has no FSX, only FSX-SE, since I reinstalled Windows)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight simulator\10.0

   Check, did that

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\DovetailGames\FSX

   Ah .. searched for "Dovetail" not "DovetailGames". I'll take a look now ...

 

HKEY_USERS\....\Software\Wow6432Node\Microsoft\Flight simulator\10.0

   As above, not entries in HKEY_USERS

HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Flight simulator\10.0

   Check, did that

 

2) You left the "Co-Existence" value under

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition

on "1". Make sure it is set to "0".

   No, I did change it to 0 earlier in my attempts, but it got deleted later as part of one of the deletions you list above (of course)

 

 

 

3) You still have some old addon pointing to a ghost simulator folder.

 

I'm not wanting to reinstall everything, so there are addons pointing to subfolders which were under the main FSX folder, and the folders are still there for continued use. But surely these won't look like FS folders. Anyone can innocently have "E:\FSX" as a folder wherein he places stuff relating to FSX -- FSX could be anywhere else.  I have backup folders containing a complete copy of all the folders from FSX. I always have had. These are not pointed to by anything as Flight Simulator folders.

 

 

In another thread it appears that the PMDG 777 and/or the PMDG NGX may be creating an FSX-SE folder in Documents, even when only FSX-SE is installed.  So if you have recently reinstalled one of them, perhaps the installer is creating these folders as well.  This may be a problem with any addon that is designed to work with FSX-SE.

 

No, I don't use anything PMDG. Thanks anyway.

 

I'm just trying it all again. Waiting for Steam to finish re-downloading, so I'll go and relax for a bit and try later.

 

Thanks,

Pete

[barrel_owl 304]

Pete,

the best thing to do then is to perform a search within the whole registry for "Flight", "FSX", "Dovetail" and/or "Steam" until you find the culprit.

If "Co-Existence" is set to "0", then there must be some "hidden" entry in the registry that makes FSX Steam to assume there is another previous FSX version installed and, as a result, to set "Co-Existence" to "1", which basically makes FSX Steam install itself in parallel and create "FSX-SE" folders.

Don't launch the installer as long as you find the culprit.

[Mike777 163]

 

 

I even wrote a guide (in Italian, sorry) on another forum about how to install FSX Steam on the same disk without formatting. It worked for everyone, it must work for you too.

 

Hi, Barrel_Owl,

 

Thanks for this extremely useful guide.

 

Mike

[Pete Dowson 558]

 

I'm just trying it all again. Waiting for Steam to finish re-downloading, so I'll go and relax for a bit and try later.

 

 

Okay. It was okay when I did it all again. I'm back up with FSX-SE as FSX and with all my stuff installed. Phew! It takes me a good week, full time, to start from scratch so this is a mighty relief.

 

Next job, to tackle P3D3.2! I'm putting them side-by-side at present, with equal add-ons as far as possible, before deciding which to use for my actual cockpit flying. Up to now FSX-SE has won all the comparisons, but I've not really tried it against P3D3 yet ...

 

Pete