November 9, 201015 yr I have been reinstalling FS9 in my Windows Ultimate 64 bit machine. I have read the numerous posts here, that adviced against installing FS9 in the Program Files (x86) folder. So, I bought a 300GB velociraptor drive, called it K: drive and installed my F2004 as K:/FS9.I started installing my planes and sceneries and I have found that some of them are looking for the "Program Files (x86)" folder by default. I changed that to K:/FS9 and I got a message saying that FS9 is not found. What can I do? Juan
November 9, 201015 yr Try downloading Flight One's free registry fix here:http://www.flight1software.com/files/FS_Registry_Repair.exe Run it and point your FS9 installation to K:/FS9 "Even Ozzy's wagging his tail again. Liam who?"
November 10, 201015 yr Probably just a typo here on the forum, but shouldn't "K:/FS9" read "K:\FS9"Having said that, some installers just dont bother searching for the correct folder at all, even though its really easy for an install app to do. One reason I and some others avoid installers where possible. If developers can't write a simple installer it'd best they didnt try.Generally, I just let the addon install itself under C: and then move it. (and all references to it, of course)Dave
November 10, 201015 yr Author Charlie, thanks for your reply, I do not have any problems with the registry, FS is operating great. In my prior setup I had FS9 in the default location under Program Files (x86) so I had no problems installing commercial sceneries. Now I install FS9 in a separate drive, and most of the sceneries installers work fine, but some others are looking for FS9 under Program Files (x86) etc. When I changed the location they cannot find FS9. is this fix just a path update? does it work with addons other than Flight 1 addons?Juan
November 10, 201015 yr Author Thanks for your reply David. I do as you said, I will always try to install in a folder in the root and then move them and activate them manually in FS9, But some commercial addons do not allow for that.Juan
November 10, 201015 yr Charlie, thanks for your reply, I do not have any problems with the registry, FS is operating great.... is this fix just a path update? does it work with addons other than Flight 1 addons?FS will work correctly even with a reg entry error that results in an addon installer unable to 'find' the game.the F1 utility will work with all FS addons ... it fixes the general FS references, not ones specific to any addon.-- D. Scobie, feelThere support forum moderator: https://forum.simflight.com/forum/169-feelthere-support-forums/
November 11, 201015 yr Author I just run the F1 utility, went to install the scenery, again the default was Program Files (x86), It did not find it there, I changed the location to my K drive FS9 , and I got the same message that it could not find flight simulator. What else can I do?ThanksJuan
November 11, 201015 yr I just run the F1 utility, went to install the scenery, again the default was Program Files (x86), It did not find it there, I changed the location to my K drive FS9 , and I got the same message that it could not find flight simulator. What else can I do?ThanksJuanAre you getting a message like the attached screenshot (after you have navigated to the actual location of your FS9.exe file) when using the Registry Repair utility?The path of course may be different.Do you shut down and then reboot your machine after a "repair"?
November 11, 201015 yr Author Hi David, thanks for your reply, that is the message I get after I applied the F1 utility. Then afterwards I rebooted the PC and started again adding the scenery and I got the same message, that Flight Simulator is not found.Juan
November 11, 201015 yr ... most of the sceneries installers work fine, but some others are looking for FS9 under Program Files (x86) etc. now the question ... the scenery package(s) is?... afterwards I rebooted the PC and started again adding the scenery and I got the same message, that Flight Simulator is not found.this reads as there is a permissions issue with win7. you are adminstrator? you have confirmed full rights to access all portions of the file structure? you have turned off UAC (maybe just for the time you run the flight1 untility)?... got to LOVE win7 and VISTA. the base assumption is you, the user, are a threat to the system.-- D. Scobie, feelThere support forum moderator: https://forum.simflight.com/forum/169-feelthere-support-forums/
November 11, 201015 yr Run regedit (search box in start menu), registry editor if you don't know it.Don't change anything for now, navigate to:[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\microsoft games\flight simulator\9.0]And post a screenshot of the contents on the right side.Or post the contents of the key "EXE Path"
November 11, 201015 yr Author Thanks for your reply Scoob.The scenery in question is Aerosoft Nice Cote Dazur LFMN.This is not a permission issue, I am the administrator, UAC has always been turned off.This scenery installed perfectly without any permission or UAC issues when I installed it in the default location "Program Files (x86) etc.....Juan
November 11, 201015 yr I think the problem is something very basic here. I have my FS9 also on my separate VRap and not a single problem. Also have LFMN installed, which installed without a slightest problem...And it's not K:/FS9, but K:\FS9.You have to start looking at your registry, something's wrong there. Or completely remove FS9, clean up registry MANUALLY, and then reinstall to K:\FS9.
November 12, 201015 yr Thanks for your reply Scoob.The scenery in question is Aerosoft Nice Cote Dazur LFMN.This is not a permission issue, I am the administrator, UAC has always been turned off.This scenery installed perfectly without any permission or UAC issues when I installed it in the default location "Program Files (x86) etc.....JuanHave you consulted Aerosoft about the issue?
November 12, 201015 yr Author Last night I solved it some other way. Before I delete my prior FS9 installation I backed up my Aircraft and Scenery folders. I just went and copied both scenery and texture folders of LFMN in a new LFMN folder and activated manually, and it works. Thanks for your help.Juan
Create an account or sign in to comment