Windows 10: Enable LongPath-Windows 10

Issue: We have few users who are synching files from the sharepoint to their local machine. The filepath consists of more than 260 charecters. Users are able to open the files online but are unable to open them locally as they get the following error message: Cannot open the file because the file path is more than 260 characters. Try Shortening the path or filename. The file path is 320 charecters. Shortening the path will not help in this scenario as there is a specific naming convention requirement for this department. What have you tried to troubleshoot this? We have enabled the long pa

:)

 

LongPaths for Windows 10 Enterprise not working

Raised on TechNet in case anyone was looking for the same answer:

LongPaths for Windows 10 Enterprise not working

Cheers,

J

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

LongPaths for Windows 10 Enterprise not working

Hi All,

We seem to have an issue enabling LongPaths for Windows 10 Enterprise. By issue, I mean it does not work at all. All our PC's are on Windows Server 2012 Forrest and they have the latest updates (10.0.14393 Build 14393) which means the anniversary update
is installed correctly. This feature would be amazing for our client as they have upwards of 2K files which are unreacable and when they run a search within file explorer and it picks up a file over the 260 character limit, explorer crashes and restarts.

The users are currently accessing the files from a mapped drive which is being shared from a file server with Server 2012 R2 installed.

The steps we have taken to enable the setting on our test lab:

* Enable 'LongPathsEnabled' REG DWORD 32 Bit key to 1

* Local Computer Policy --> Comp Config --> Adm Templates --> System --> Filesystem = Enable 'Enable Win32 Long Paths'

**We can see that the Local Computer Policy changes the Reg Key to 1 or 0 dependent on if the setting is enabled or disabled**

When testing we still get the same error message 'The file name is too long' and explorer crashes when it hits a file which it can see but not access. We confirmed this with mulitple searches and running ProcMon in the background.

Any help or guidance on this would be much appreciated.

Thanks,

Jamie