Windows 10: Long Path Enabled

Hi Team,


We have been trying to increase the long path value as per the documents from Microsoft. We can create maximum of 20 sub folders beyond that we cannot go. So could you please help me in getting this sorted out.


thanks.

Sriram Krishnamoorthy

:)

 

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?

 

Destination path too long after enable NTFS long path

Hi my name is Jay, I'm an independent advisor. I'd be happy to help with your issue.

I understand that Long Paths is already enabled in Local Group Policy, can you also do it in the registry as suggested in this article?

https://thegeekpage.com/fix-destination-path-to...

I hope this helps, please feel free to ask questions and keep me on track. I will keep working on this issue until it's resolved, thank you.

Regards,

Jay

____________________________________________________________

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product
advertised on the site before you decide to download and install it.

 

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?