Feature Request: LongPath Support
Since the Anniversary update of Windows 10 the option to enable OS support for full paths larger than 260 characters was added:
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
While this enables the OS to support such paths (and makes the OS handle their resolution when used in applications), it seems that the feature needs to additionally somehow be enabled on a per-application basis to allow for each app to make use of long paths.
I will admit that instructions for how to achieve this are conspicuously sparse, but for .NET based applications at least it may have to be enabled within the manifest of the application:
https://blogs.msdn.microsoft.com/jeremykuhne/2016/07/30/net-4-6-2-and-long-paths-on-windows-10/
Launchbox (not sure about BB but I can only assume it is also affected) currently does not have this support enabled as I ran into an issue using paths longer than 260 characters within LB even though LongPathsEnabled is set to 1 in my registry. This issue, and my rationale for this feature, are briefly described in the following forum post.
Comments (3)
-
-
reporter @Andrew Johns
Thanks, but also make sure you click “Vote for this issue” over by the vote count.
-
Thanks for the reminder - I found the vote link and voted
- Log in to comment
Upvote from me on this one.