I tried asking this question in the normal Microsoft Answers Community, but since it is a local policy, they said to come over here...
I saw that the Windows 10 Anniversary Update was supposed to address the limitation of long file paths and names. According to what I found, the new GPO entry of "enable NTFS long paths" was supposed to be added, but I didn't see it. Upon further research, I did find the "enable win32 long paths" option one level up in the Local Policy Editor.
Question: Was this setting supposed to address the problem? After I enabled it, rebooted the computer and confirmed that the setting was still enabled, I tried to copy a directory (via File Explorer) from a local hard drive (G:\*.*) to a server share (\\SERVER\SHARE), but it failed for the same old reason that the pathname was too long. Does this only work locally, or does it only work with specific capabilities, like PowerShell?