Windows 10: Long Path Enabled Does not Work

Dear Team, I want to enable long path in Windows 10. Because I created several subfolders and want to rename the PDF or other files within it exceeding 260 characters. I tried to troubleshoot by using recommendations from Microsoft like put script in PowerShare and "LongPathEnabled" 1 in "Registry". But it did not work. Can you, please, help me?

:)

 

Enable Win32 long paths GPO not working

Hmm, bad news I'm afraid. In this thread I see replies from
apparently well-informed people claiming that even though Windows 10 is ready for long paths, Windows Explorer is not. It is suggested that a 3rd party fileviewer "One Commander" does support long paths.

 

Is it risky to enable long file paths on Windows 10?

Windows 10 has an option to allow for longer file paths (background). Is it risky to enable this option?

I ask because I've heard mixed comments about how there can be bugs related to long file names.

From a recent (2016-07-30) MSDN blog post:

• A comment:
  
  
• The response:
  
  

Another question on SuperUser (2016-08-17) seems to suggest that there're known issues.

Question: Does enabling long file paths increase the risk of file loss or corruption on Windows 10?

 

GPO: enable win32 long paths

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 GPO.

Question: Was this 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 file (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?