Windows 10: DESPITE Enabling Long File Paths via regedit; I still get "Destination Path Too Long"

Windows 11 Home User.GPEdit doesn't work.I enabled long file paths as per the instructions here I tried both PowerShell and regedit, not that it makes a diff.I still get "Destination path too long".I have hundreds to thousands of directories that exceed 255 characters, and I need to transfer them from my old PC to my new one. I need long file paths to work.

:)

 

Destination path too long after enable NTFS long path

I have windows pro 10 education and 1903 version. I enable NFTS long path and update the group policy with this command:

Code:

[b]gpupdate /target:computer /force[/b]
But when I copy-paste folders to an external drive I still get the error [b]
Destination path too long The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.[/b]

Thanks in advance.

 

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.

 

Destination path too long after enable NTFS long path

Hi StavrosStavridis2,

Sorry to hear that. Will you be able to provide the steps that you already performed aside from modifying Long Paths in Local Group Policy and Registry? Have you somehow tried to perform some of the easier steps like finding a file that could have a very long
filename which may have caused this or something simple like renaming the root folder as describe in the article I sent? Thank you.

Regards,

Jay