Yes. I can even understand if you have concerns about this. The strange - or funny - thing is, that it is not absolutely clear, why at some installations it works absolutely normally and why on soem it does not. Even the most knowledegeable gurus have not (as far as I have seen) come up with an absolutely satisfactory explanation of this behaviour.pmesmer wrote:to lostsoul____ Thanks for all your input. This is really strange because I have several A2 aircraft and I have always installed them using the default installation without any problems. All my other aircraft have been installed the same way. I guess I'll have to go back to "square one" and give all of this some serious thought. Thanks again____ Pete Mesmer
Fact is in any case that since Windows Vista (where UAC was introduced for home systems) the directory "\programs (x86)" is designed to hold 64-bit executables only and whenever possible no data. There have been data paths created such as "\program data" or any other path that you may design on your own. The mentioned "\programs (x86)" folder is "equipped" with special access rights. Don't ask me about details here as I'm not able to provide any Nevertheless after having done many trial-and-error installations in the past I am convinced that the easiest way to overcome any such problems or mishaps is to install FSX (or in case you use Prepar3D) into its own, separate path, even better onto a separate HD or SSD. That way I never again experienced any such such oddities anymore for the last 6 or so years.