exceeding max_path (path length > 260 characters)

[Start Me Up]

Hello,

as you are probably aware, Windows has problems with long paths (total length > 260 characters).

---

In old Windows versions there is the "\\?\"-trick, which helps in a few situations:

Quote

The "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send ... it straight to the file system. For example, if the file system supports large paths and file names, you can exceed the MAX_PATH limits that are otherwise enforced by the Windows APIs.

... it turns off automatic expansion of the path string ... but not all file I/O APIs support "\\?\" ... Unicode APIs should be used ...

---

Starting with Windows 10, it is possible to allow specific applications to use longer paths.

According to the documentation, Microsoft modified specific functions of the API to allow using longer paths for specific applications in Windows 10. So the list of functions is rather interesting. And here it is:

• CopyFileW
• CopyFile2
• CopyFileExW
• CreateDirectoryW
• CreateDirectoryExW
• CreateFileW
• CreateFile2
• CreateHardLinkW
• CreateSymbolicLinkW
• DeleteFileW
• FindFirstFileNameW
• FindFirstFileW
• FindFirstFileExW
• FindFirstStreamW
• FindNextFileNameW
• FindNextFileW
• FindNextStreamW
• GetCompressedFileSizeW
• GetCurrentDirectoryW
• GetFileAttributesW
• GetFileAttributesExW
• GetFinalPathNameByHandleW
• SetFileAttributesW
• GetFullPathNameW
• GetLongPathNameW
• MoveFileW
• MoveFileExW
• MoveFileWithProgressW
• RemoveDirectoryW
• ReplaceFileW
• SearchPathW
• SetCurrentDirectoryW

---

Is anyone aware of any pioneer work that has been done to improve the situation with Windows versions older than Windows 10?

Edited 3 hours ago by Start Me Up