Simulator Installs Under Windows 10
Posted: Thu Oct 10, 2019 5:23 am
Windows 10 security is different then older Windows operating systems. This requires that flight
simulators, including Microsoft's own group, should be installed "outside the default" installation
path of the program. The default path is C:\\Program Files (X86)
Without a clear understanding of how to configure directory permissions in Windows 10, installing
anything that you, as a user, need access to becomes important.
I am running FSX_SE under windows 10 and have the simulator program installed in a solid state drive
which is outside the default installation path for the program. I have a stable platform that runs
well and works.
This does not rid the simulator of all the problems that the older design has, but at least the
simulator runs and I can get at the files that I need to. I will get OOM errors because of the 8
bit design and memory limitations under certain conditions, but they are known.
The bottom line, Simulator installations on Windows 10 will work if they are done in a way
that gets around the built-in security in Windows 10. Admin privileges will not defeat the directory
permissions logic built into windows 10 like it did in the older operating systems, in the default
path.
Next time you install on Windows 10, install the simulator on a path other then the default, and
drop the security on the simulator master directory to wide open. Give it every permission you
can, so that everything else can have access to it. This will go along way towards giving you a
stable install.
simulators, including Microsoft's own group, should be installed "outside the default" installation
path of the program. The default path is C:\\Program Files (X86)
Without a clear understanding of how to configure directory permissions in Windows 10, installing
anything that you, as a user, need access to becomes important.
I am running FSX_SE under windows 10 and have the simulator program installed in a solid state drive
which is outside the default installation path for the program. I have a stable platform that runs
well and works.
This does not rid the simulator of all the problems that the older design has, but at least the
simulator runs and I can get at the files that I need to. I will get OOM errors because of the 8
bit design and memory limitations under certain conditions, but they are known.
The bottom line, Simulator installations on Windows 10 will work if they are done in a way
that gets around the built-in security in Windows 10. Admin privileges will not defeat the directory
permissions logic built into windows 10 like it did in the older operating systems, in the default
path.
Next time you install on Windows 10, install the simulator on a path other then the default, and
drop the security on the simulator master directory to wide open. Give it every permission you
can, so that everything else can have access to it. This will go along way towards giving you a
stable install.