is it better to let it default to program files or to have it install to C:? and are there any special problems with having a custom location?

Only issue with having FS in other locations is the speed of the drive you use and the latency of any connecting cables, USB hubs etc, plus the fact that you have to select the FS location when using add-on installers which automatically find the default FS location.I have had FS on the x86 portion of C, the normal portion of C and other external and internal drives over the years. It really makes no difference to its operational stability as far as I have found, so it is more a choice based on drive size and convenience for you which will determine where best to install it.Some have advocated not putting it in the default location for a number of reasons (mostly drive fragmentation), but mine is in the default C drive 86 location now, and I have no issues at all with it being there, although I do stay on top of keeping my PC running well.Al

is it better to let it default to program files or to have it install to C:? and are there any special problems with having a custom location?

If you're running as an Admin with UAC off, I'd stick FSX in the default location... "Program Files".That's how I'm setup.However, if you're not running as Admin, I'd put FSX 'outside' of Program Files.Why?Because a lot of 3rd party FS programs need to write to the FSX folder, and Vista/Win 7 will "block" anything being written to the "Program Files" folder if you're "not" running with Admin rights.UAC can sometimes be an issue, too.This is a problem I stumble across with some of my users from time to time.