Windows 10: Long pathname support on Windows 10 Pro 64-bit OS

I submitted this issue:

I want to open and save files with long paths with Office 365 Word and Windows 10 v 2400 Pro 64+bit computer. Does Windows 10 pro support long file names?

I've change LongPathsEnabled to true, I've verified the change with RegEdit and rebooted.

But long file paths still don't work. I've used long file paths years ago and am a developer. Do i need to do something else to get long file paths to work? The answers I've gotten are to use a 3rd party tool, Not a solution. or to shorten the directory names in the path to get the length below 260 characters, not a solution. I want and need long pathnames to work.


My solution was

after changing LongPathsEnabled, and rebooting I used fsutil and ren to rename a Word file aaa.docx to a long filename with a deep path. The entire path length of the file was greater than 256 characters. Then I tried to open the file with Word. Word navigated and opened the file without a problem. When I tried to edit the file and resave it, I had to enable editing on the file first. After enabling editing on that file, Word can navigate to and open files with long paths. To save a file with Word with a long filename, I get a "you can't save here please choose another location" error. So I've simple started to save the files to C:\temp and then use Windows Explorer to move them to the deep long pathname directory.


Hope this helps others with the same problem.

:)

 

Long pathname support on Windows 10 Pro 64-bit OS

I need to open and save to long pathnames on my Windows 10 Pro 64-bit OS using Word from Office 365. I have enabled LongPaths Enabled using the Group Policy Editor and checked the change using Regedit. I have rebooted my system but long pathnames still
don't work. What do I need to do to enable Long Pathnames?

 

Long path names on Windows 10 Pro 64-bit version 2400

I need to open and save to long pathnames on my Windows 10 Pro 64-bit OS using Word from Office 365. I have enabled LongPathsEnabled using the Group Policy Editor and checked the change using Regedit. I have rebooted my system but long pathnames still
don't work. What do I need to do to enable Long Pathnames? Some suggest a workaround using 3rd party produces. I've used long pathnames before. We are missing something here. Microsoft, it is time to get involved! I've read that application, in order to use
long pathnames, need something in their manifests.

 

Long path names on Windows 10 Pro 64-bit version 2400

This is not a Windows Explorer error! I'm using an up-to-date Windows 10 Pro 64-bit version 2400 and Office 365 on NTFS volumes!

I've changed the LongPathsEnabled registry key with the group policy editor and checked the change with RegEdit per the documentation. I've rebooted for the change to take effect.

The responses I've gotten are: 1) shorten the pathnames or 2) use a 3rd party product. Neither of these solutions reflect well on Microsoft.

There may be another change to either Windows 10 Pro or to Office 365 to enable long pathnames.

It takes barely 5 minutes to change LongPathsEnabled, reboot and test to determine that this change does not enable long pathnames with Office 365 Word. It is not complicated. I think we, as a community, need to pull together and escalate this. If the change
is simple, let's get it on the web. But the responses I see on a search of solutions for this problem are not solutions but work arounds that don't solve the fundamental problem.

I am a Windows developer. These are Microsoft products I am paying for. I've used long file names in the past.