Jump to content

ORBX FTX FSX SE install issues


Recommended Posts

Hi all an before you all say it yes i've searched the forums, i've ran TweakFS's registary repair. I've got the latest installer from Flight Sim store an still no matter what I do I get the Radial button 1 error there is no traces left on my PC from my boxed version of FSX ive  uninstalled it from add an remove programs to the point of it no longer being there. i've deleted all files assosaited with it an i've cleaned the registry.


 


any further ideas i'm running windows 10 64bit


Link to comment
Share on other sites

Welcome.


 


The radio button error is telling you that there is no registry entry


for the simulator that you are trying to install into, in your case,


FSX.


 


The TweakFS FSX Registry Utility will indeed write the correct


registry entry in.


 


In this case, FSX SE is installed into G:\FSX Steam\steamapps\common\FSX,


yours may not be the same but the target needs to finish with \FSX.


Set the boxes as I have highlighted in red and click on Set FSX Path.


 


Untitled.jpg


 


Once you have done this, the installers will find the location you entered.


 


You need also to check that FSX SE is not running in coexistence mode.


 


To do this, visit


 


C:\ProgramData\Microsoft


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


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


 


and check that there are no folders named FSX-SE.


 


If you find only FSX folders, all is well.


Link to comment
Share on other sites

  • 3 weeks later...

I had a similar problem but the TweakFS reg utility was able to fix it. The reg entry was correct in the HKEY_CURRENT_USER , but was wrong in HKEY_LOCAL_MACHINE.  I am guessing what caused this problem is I created two new login credentials, one with standard user privileged and a new Admin name that I use now. I did not delete the original log in name but I was using that at the time I installed the steam version and I also installed the box version I got off of eBay  under that log in name. So just a guess that maybe this was what caused the issue. I'm too lazy to recreate the scenario and log in with the other account to see but I bet that's what caused it.


Link to comment
Share on other sites

  • 4 weeks later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...