i install MSFS from MS Store, through all automatic there.
Just set there location on another drive(SSD) and that’s it. Everything is done by system.
It installs like microsoft app inside windows
I installed from the MS Store as well, but I picked my own install location. Looks like that would solve any path length problems for you.
all i can choose there is the place, but not the folder
That’s weird. I wonder why?
maybe i didn’t see any option, but still, should i reinstall MSFS and looking for options?
i remember that windows just ask me a drive, but not folder
so far I understood the docu, some windows system limits are disabled too with this setting.
If an application would get this feature, it must explictly support that.
@Jigsaw407 .. I also still wonder a bit about the S1… not 100% sure about FS2020 maximum path length is too small for the community folder, can you please resolve this? - #4 by graphika
. But I also own Steam version, with not have these strange MS-Store install path linking thing… ( e.g. C:\Users\xxxx\AppData\Roaming\Microsoft Flight Simulator\Packages\Community )
I would give it a shot. There should definitely be an option to define your custom install location.
There is a way to reinstall without having to download everything again:
1 Like
Wherever the folder location on your drives, it seems FS2020 code is accessing it via this long path prefix. The reason is because it is a WindowsApp and this permits the app to locate the folder with a fixed path, wherever the user decides moving it to. There is therefore the physical path (where YOU put it) and the logical path (where FS2020 finds it), both pointing to the same location.
2 Likes
it looks much easier than i thought, but i’m not ready to reinstall it for now.
i’ll keep it for the last resolve
So even though my Packages folder in the C:\Users subfolders is empty…
… and everything is located here …
I could run into the same problem myself? That’s the weirdest way to go about things. I guess that’s Microsoft logic. 
maybe somewhere in the registry there is a path to community folder, and simple change that path will solve all the problems? i didn’t find any information about that.
gone pressing ctrl+F
found nothing. LongPaths enabled doesn’t work too
seen now also that this is a old “issue” which comes sometime on top and also seen that some users tried the reg-edit already without success..
https://forums.flightsimulator.com/search?q=path%20to%20long
As said.. seems affected are more MS-Store installations..
Found button “Move” inside Microsoft apps, but still it only asks about drive, not folder. The same that it ask during the install.
Only drive option
Microsoft disabled option to choose any location but drive now. there is no way
No, ntfs also has a small path limit 260 chars from memory. Several years ago ms said it will may never be fixed. It requires changes all over the windows code base.
It is a pain in the neck.
I’m not sure if symlinks get past it, I’ve never tested it.
Are you sure?
1 Like
I installed to D:\FS2020
This was the following 109GB.
But, the install program built a new folder: D:\WpSystem\
The initial 1.06GB goes to the Windows Boot drive (usually C:)
and is not selectable.
Can you provide a screenshot?
Soon there will be screenshot but now I found information of how to move packages directory to another place. The path is located in file Usercfg.opt in localcache. Changing path and moving directory is causing now eternal loading on the black screen with blue line.
Blue line stops about 90% and stucks. 5hours nothing happened
Hello do not do that … you’re good for a complete reinstallation… 
1 Like