Registry issues

[tango zulu papa]

hi guys, I am very disappointed that Steam would release this game without solving the registry issues that seem to plague a lot of people, me included. I am not a guy who is confident digging in to registries on my computer. Why is there not a patch from Steam to solve this issue for us noobs? When I pay full price for a Steam program, I expect a product that will work without issues. Come on Steam, I expected better. Any easy help would be appreciated.

[RoY]

Registry issues? and why are you blaming steam? Steam didn't release the game. I don't read every post here but see most of them and I have not hear of any registry issues that are caused by FSX or steam. Most likely your system is to blame. It better to first find the root cause before aimlessly pointing fingers and making yourself look a fool. I understand your frustrated but you have provided zero information about how you come to the conclusion that this is somehow the fault of steam or FSX.

[chelmo]

Registry issues almost invariably arise because FSX:SE has detected a previous installation of the boxed version. I take it that is the case here?

[tango zulu papa]

Thanks RoY, thanks for nothing. As mentioned, I am not that computer literate and do not really know what a registry is or what it does. I am not the only one with this issue, just read the threads. Next time if you have nothing positive to add to a post, shut your pie hole.

Uncle Adolf, that is probably the case, I thought I had removed everything from the boxed version, but obviously not. I am loooking for an easy way to fix this problem without diking around in the registry.

[mikeytwc]

pretty easy to fix, ill look and see if i can find the solution.
your offhanded remarks were unneeded tho, as we all here are here to help
gimme a few and ill look for the registry fix(available from flight1 i believe)
give this a try and lemme know how you fare, ok

http://www.flight1software.com/files/FS_Registry_Repair.exe

[Dr.StrangeSpock]

The guy was very unclear in relating his * "Issues". Good thing that fellow read his mind. People come into the forums all frustrated and Steeming about bugs and blow off Steem. Not helpful for finding a solution to Problems. It is a tricky problem ..I did a Reg Edit I found pointing to Steam FSX for any MS FSX standard loctations but it is not fully recognized by installers. That old Registry Repair Tool did nothing for me and my FSX-SE folder and fsx_se.cfg. It is only fixing old FSX locations moved around.

http://steamcommunity.com/app/314160/discussions/2/620712999980333060/

This is my post on what I fixed in Registry.. but ..as i say, still not acceptable to some installers of purchased stuff and free stuff.





*(I like to call them PROBLEMS..but that word is "scary" now since we all know PROBLEMS can NEVER be Solved.. butt issues can be debated! The issue is TISSUE I say ..USE IT on your nose and if you do not have a bidet!)

[Dr.StrangeSpock]

Because of study at http://www.orbxsystems.com/ in their Forum, which is very up on issues in FSX:

I FINALLY fixed my FSX/FSX-SE registry Problems. Copied below from Nick who knows the game very well:

FSX & FSX-SE REGISTRY BUG FIX:

"Unless every trace of FSX is eliminated from the Windows Registry,
or it is being installed on a freshly installed operating system,
FSX Steam will install in "Co-existence" mode
This means that it will create external folders named FSX-SE rather than
FSX.
In this case, although the FTX software may install correctly, neither the
installer nor FTX Central will be able to locate the scenery.cfg file.
If you encounter this error message, the following is a fix which will work
whether there are traces of FSX remaining or not.
----------------------------------------------------------------------------------------------------------------------------
If you have already installed any products or scenery, before you start,
back up the contents of your
C:\ProgramData\Microsoft\FSX-SE and
C:\Users\Your name\AppData\Roaming\Microsoft\FSX-SE
folders to another location.

Once the fix is applied, the back ups can be copied into the new
C:\ProgramData\Microsoft\FSX and
C:\Users\Your name\AppData\Roaming\Microsoft\FSX
folders that will be created the next time that FSX Steam is run.
----------------------------------------------------------------------------------------------------------------------------
The registry editor is not complex but must be used with care.
It is highly unlikely that problems will be encountered with this simple edit.
To open the Registry Editor, select Search from your Windows menu and type in
regedit which will find regedit.exe. Click on this to run the Registry Editor.

Navigate to

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

where you will see a Registry Key named Co-existence.
You will see that its value is 1.
Right click on the Co-existence key and select Modify... and change the value to 0 (zero).
Close the Registry Editor.

You can then go to

C:\ProgramData\Microsoft\
C:\Users\Your name\AppData\Roaming\Microsoft\
C:\Users\Your name\AppData\Local\Microsoft\

and in each case delete the FSX-SE folder.
If you see an FSX folder, delete that also.

Then restart FSX-SE and new folders named FSX will be created.
Once you have done this, the file structure will match what
the installers and FTX Central expect to find for FSX and they will
work correctly.

Credit for the registry fix to Steve Waite at the Avsim forum.
I have tried it and it works for me exactly as I have written.
As I have both versions on my PC, I have also found that
the process is entirely reversible"


I also had to rename my fsx-se.cfg, fsx-se.txt and backup .cfg to fsx.cfg etc to fsx.cfg, fsx.txt, fsx.cfg.backup.

Now the installers and addons work without having do search and destroy all old FSX entries in registry.

ALSO, there is an .exe program called: FSXRegUtility.exe...it is version 1.21 from TweaksFS.

I used it prior to the procedure above. You just download .zip, extract to a folder in your FSX collection, run the .exe. No need to extract the other .zip there. You get a utility that says Get Path and Set Path. On Get Path click Get FSX Path. Drop down list is Registry items in LOCAL MACHINE and CURRENT USER. You probably have one of the two pointing to OLD FSX. Go to Set Path for LOCAL MACHINE, Browse for your STEAM FSX folder, and CHECK Option -Current User: Add to Current User ...Box .. click Set FSX path and key reg point to areas are fixed. I had Current User still on OldFSX.

This little utility did not do the Fix copied above but straighten THAT out.

It SHOULD be a SIMPLE fix to Add a couple extra fixes to this UTILITY to do all the fixes above with a few more lines and boxes and Steam should get um to do it.

[Dr.StrangeSpock]

I reinstalled all my ADDONS and STEAM FSX now is seen by them all as NORMAL...no more FSX-SE files and folders. GREAT!

Maybe not needed to reinstall addons....but just in case it was needed.

[CaffinatedPanda]

Originally posted by RON ASHETON-STOOGES:

I FINALLY fixed my FSX/FSX-SE registry issues with a post copied here:

FSX & FSX-SE REGISTRY BUG FIX:

Unless every trace of FSX is eliminated from the Windows Registry,
or it is being installed on a freshly installed operating system,
FSX Steam will install in "Co-existence" mode
This means that it will create external folders named FSX-SE rather than
FSX.
In this case, although the FTX software may install correctly, neither the
installer nor FTX Central will be able to locate the scenery.cfg file.
If you encounter this error message, the following is a fix which will work
whether there are traces of FSX remaining or not.
----------------------------------------------------------------------------------------------------------------------------
If you have already installed any products or scenery, before you start,
back up the contents of your
C:\ProgramData\Microsoft\FSX-SE and
C:\Users\Your name\AppData\Roaming\Microsoft\FSX-SE
folders to another location.

Once the fix is applied, the back ups can be copied into the new
C:\ProgramData\Microsoft\FSX and
C:\Users\Your name\AppData\Roaming\Microsoft\FSX
folders that will be created the next time that FSX Steam is run.
----------------------------------------------------------------------------------------------------------------------------
The registry editor is not complex but must be used with care.
It is highly unlikely that problems will be encountered with this simple edit.
To open the Registry Editor, select Search from your Windows menu and type in
regedit which will find regedit.exe. Click on this to run the Registry Editor.

Navigate to

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

where you will see a Registry Key named Co-existence.
You will see that its value is 1.
Right click on the Co-existence key and select Modify... and change the value to 0 (zero).
Close the Registry Editor.

You can then go to

C:\ProgramData\Microsoft\
C:\Users\Your name\AppData\Roaming\Microsoft\
C:\Users\Your name\AppData\Local\Microsoft\

and in each case delete the FSX-SE folder.
If you see an FSX folder, delete that also.

Then restart FSX-SE and new folders named FSX will be created.
Once you have done this, the file structure will match what
the installers and FTX Central expect to find for FSX and they will
work correctly.

Credit for the registry fix to Steve Waite at the Avsim forum.
I have tried it and it works for me exactly as I have written.
As I have both versions on my PC, I have also found that
the process is entirely reversible


I also had to rename my fsx-se.cfg, fsx-se.txt and backup .cfg to fsx.cfg etc.

Now the installers and addons work without having do search and destroy all old FSX entries in registry.

This topic needs to be pinned or stickied or whatever Steam calls it in it's forums.

I did something similar to this, then ran the 'Verify files' option in Steam. So glad I did cause my folders now have the 'FSX' designation now. All of my aircraft/scenery add-on's work so much better.

[Dr.StrangeSpock]

Thanks, I think that little 1 to 0 change in ONE registry setting would have been nice to know about ....? months ago for me. I am scared of "Verify Files" with all my custom addons and did not do it in case it erases all the settings and addons.

After getting STEAM FSX with my OLD FSX LONG DORMANT as unplayable to my standards I invested $1300 in Software & an SSD, Editors's Keys FSX custom auxilary Keyboard about my Z-Board, because it ran much better and is in Steam.

These thousands of Addons you can get free or buy cannot deal with the FSX-SE labeled folders and files whence you uninstall the OLD FSX 10.

Methinks all these Old FSX disk players should go Steam Version Eventually for it's better coding and convienience ...and they are going to jump into a MESS like I did.

BUT!!!! I am sure others are terrified that noobs with enter and SCREW up their Registry and Complain! So doubt it will be. One can easily Export their entire registry or the One setting area or Create a Restore Point in System Protection prior to entering the Registry of course.

It would be Keen if it was included as an automatic fix as some .exe available from Steam for those who Uninstalled Old FSX disk versions. I uninstalled 3 of them as all a waste compared to Steam version.

Get your Windows 10 Upgrade while free for a year too.... I have a 350 MB exported Registry with 340 games installed and it went SMOOTH!

[Dr.StrangeSpock]

I added this data to the bottom of my first post by Edit and make sure that is done too:

"ALSO, flyawaysimulation.com pointed me to a quick .exe program called: FSXRegUtility.exe...it is version 1.21 from TweaksFS.

I used it prior to the procedure above. You just download .zip, extract to a folder in your FSX collection of saved software, run the .exe. No need to extract the other .zip there.
You get a utility that says Get Path and Set Path. On Get Path click Get FSX Path. Drop down list is Registry items in LOCAL MACHINE and CURRENT USER. You probably have one of the two pointing to OLD FSX. Go to Set Path for LOCAL MACHINE, Browse for your STEAM FSX folder, and CHECK Option -Current User: Add to Current User ...Box .. click Set FSX path and key reg point to areas are fixed. I had Current User still on OldFSX.

This little utility did not do the Fix copied above but straighten THAT out.

It SHOULD be a SIMPLE fix to Add a couple extra fixes to this UTILITY to do all the fixes above with a few more lines and boxes and Steam should get um to do it."

[Rogen]

Windows also has other methods to work around the issue.

For instance I have both an FSX and FSX-SE configuration folder that both refer to each other and where updateing a config file in the FSX folder also updates the same file in FSX-SE and vice versa.

It's known as Junction Points and has been a part of the Windows NTFS file system for many many years.

Check out post #3 in the below link if you'd like to see how Junction Points can be put to use.

http://steamcommunity.com/app/314160/discussions/2/530646080866138384/

Cheers Tony M

[Jeff]

Originally posted by Yerphuct:

Thanks RoY, thanks for nothing. As mentioned, I am not that computer literate and do not really know what a registry is or what it does. I am not the only one with this issue, just read the threads. Next time if you have nothing positive to add to a post, shut your pie hole.

Uncle Adolf, that is probably the case, I thought I had removed everything from the boxed version, but obviously not. I am loooking for an easy way to fix this problem without diking around in the registry.

You dont have too be so rude people are here too help you if you have left overs from the boxed set use Revo uninstaller and take left overs out and start fresh with the steam version you can get Revo from Cnet.

[Sparkplug]

Wow if your gonna play on a computer at least learn how to play on it. If at first you don't succeed then skydiving is probably not for you. LOL