Just attempted W090n40 scenery installation on AMD-8 laptop, which previously was only run using Terrasync and had an empty scenery file.
Scenery downloaded and program installed it in C:\Users\{name}\Documents\FlightGear\Scenery.
Program also automatically created following path in "additional scenery locations":
C:/Users/{name}/Documents/FlightGear/Scenery.
In other words, Flightgear 2018.1.1 installed the scenery in a 64 bit file, but created a 32 bit
path in "additional scenery add-ons".
Needless to say the scenery couldn't be accessed.
Somewhat different experience on my Intel I3 ( latest) machine, Scenery downloaded, but when I tried to use the install feature, FlightGear 2018.1.1
would only display several of about 15 files resident in my download file; and the resident scenery file did not display. So it could not be selected.
{both machines running current versions of WIN 10. Thought both current on updates, but perhaps not. Have no other explanation.)
Maybe it didn't like a 32 bit scenery file from the gitgo?
Guess that leaves a lot of wandering about with automatic scenery download on to complete the 090w40n scenery area, as I have only recorded
15 of about 90 sub-files using TerraSync, so far.
P.S. When tried scenery installation on old Celeron machine, got couldn't find file message;
whereupon program crashed, despite presence of downloaded file.