Helpful resources:
- How to Make Windows 10 Accept File Paths Over 260 Characters
- Naming Files, Paths, and Namespaces | Microsoft Docs
I'm still trying to formulate a good test for ensuring the long path support option has been properly enabled but below is what I've come up so far and verified working on a machine that does have this option enabled.
mkdir "testdir/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/"
This is a path that is at least 519 characters in total length with segments each of which are mostly 10 character directory names. Using the double quote ("
) seems to be required for this to work from the Windows command shell.