I’ve been wondering about FS2020 and the way it is handling paths from some time.
First and foremost, I’ve read reports of a problem where using a non ASCII character in the user account name is causing FS2020 to fail accessing the files properly. This is supposed to be transparently handled when using the UCS2 Windows API (‘W’), instead of the ANSI Windows API (‘A’).
In addition, the path you’re indicating is the absolute minimum to access every single file in the “Community” folder and is therefore already 151 characters long, out of the 260 available (MAX_PATH). This doesn’t leave much remaining characters for any sub-folder.
Both of these are making me wondering whether UWP apps aren’t supporting the extended-length path prefix, or is it just because FS2020 is using the ANSI API flavor and therefore can’t benefit from the extended-length path prefix??!
The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters).
To specify an extended-length path, use the "\?" prefix.
For example,
"\\?\D:\*very long path* ".
Maximum Path Length Limitation - Win32 apps | Microsoft Docs