Windows 10: Long Paths

Greetings, I have a problem with long paths in Windows 11 Pro When I try to move a file or folder from SharePoint to OneDrive, I edited LongPathsEnable in Registry and GPedit, but I got no result... After that, I downloaded Directory Opus like File Explorer and the issue's done! So my problem's in File Explorer not in Windows or System! So, How can I fix that If I Can't change my Explorer? my version 22H2 for File Explorer Thanks, Microsoft team.

:)

 

Unable to rename folder or file in a long path folder (updated)

Hi Greg,

Thanks for suggesting Feedback Hub.

On the other hand, in my first post I posted step 1,2,3. Your links contains the same, but no more.

The issue is in File Explorer, that means I need solution in File Explorer, not in PowerShell.

To be more precise the issue is: I can't create new folder in a long path folder. Just now: I solved it half: I can copy a folder to a long path folder. That's fine but I cannot rename folder or file in a long path folder.

Regards

 

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

 

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?