hazy hull
My install issues were of an entirely different nature, and I outline this issue and the solution. I have purchased an entirely new machine requiring a complete install of MSFS, on Windows 11. What I didn't notice was that the installer chose a different path in which to install the official folder, meaning that the subsequent fly by wire and a330 installers didn't place their files in the same place. The MSFS path was
c:\users\myname\appdata\roaming\MicrosoftFlightSimulator\Packages\Official\Steam.fscontent\Official\Steam, which couldn't be seen in the install page as the box showing this path is not big enough unless you click on it to verify. It meant that the default community folder was in the same .FS content directory. My saved community folder from the previous install was in the correct place, but none off the aircraft were showing up in the simulator. Not having had issues on the older former machine I used, I hadn't checked, so allowed the so-called default to proceed. This meant of course that the FBW and the Headwind installer placed the new airframes where they would normally go, unaware of the original install path. It wasn't until I turned on the SDK in the simulator, and found the incorrect path, I realised the issue. So I moved all the official content and adjusted the path in the UserCfg.opt file in the MicrosoftFlightSimulator directory in the same path, that everything became stable. So the official folder should c:\users\myname\appdata\roaming\MicrosoftFlightSimulator\Packages\Official\Steam\ and the community folder c:\users\myname\appdata\roaming\MicrosoftFlightSimulator\Packages\Community. Incidentally the SDK is very useful to find the virtual directories, and you only need to turn it on briefly to check.
By the way, it was 12 hours in my life I shan't get back, it takes a while to move so much content, even on an nvme.
rare crown