Yeah, I'd suggest the MS Store because it takes one extra layer of complication out the way, vs. Steam.
However, I will respectfully contradict Tom's advice and suggest that, during the Install process where it asks you where you want to store the main files, that you do NOT take the default folder, but instead create a custom folder such as "C:\FlightSim" and install there, for a multitude of reasons.
Advantages of installing the data files in a custom folder:
- It's just easier to navigate to vs the insanely long default folder location, saving you having to rely on a pinned folder bookmark just to find the darn thing.
- Less chance of long filename issues if you haven't done the OS setting to remove file path limitations.
- There's a bug still not fixed that sometimes will re-download the entire 100GB plus set of data files when there's a sim update. It only hits a small portion of the audience and is more likely to happen if you participate in betas, but why risk it when installing in a custom folder stops it from happening?
Advantages of accepting the default folder location instead of using a custom folder:
- You don't have to think of a folder name
- Like 3 fewer clicks when you're installing
- Really, that's it.
I mean...
C:\FlightSim
C:\Users"YourUsername"\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
Which seems like something you want to be intimately familiar with every time you go to use the Community folder?
I know Tom hasn't had issues with the default folder, and he's Windows-savvy enough to pin the file folder in Explorer so he doesn't have to deal with MS's horrible GUID-packed filename, but lots of people have run into the issues above. So make your life easier and pick a custom folder!