You can enable enable Long Path Support in Windows 10. Starting in version 1607 ‘Anniversary Update’, the 260 character limitation for NTFS path length issue is resolved. That path length limitation has been present on Windows since very first versions.
By default Windows 10 has a maximum file path length of 260 characters. All Windows file systems have the concept of files and folders to access stored data. Path is a string value indicating where this data is stored. However, there is a 260 character limit for paths imposed by Windows, which includes a drive letter, a colon, a separating backslash, and a null terminator. This limitation is not for the NTFS file system, but for the legacy APIs that are used to access data. There are also workarounds, such as accessing Unicode (or “wide”) versions of Windows API functions, and prefixing the path with \\?\.
At the end-user level, some users may have experienced an issue in the past where File Explorer will not allow access to a file or folder if the path is longer than 260 characters. Thinking about one of Windows’ long-term concerns, Microsoft has finally added a feature that will ultimately address the long-term 260 character limitation issue.
This tutorial will show you how to enable the Long Path support for NTFS in Windows 10.
Enable Long Path Support in Windows 10
- Open command prompt as Administrator.
- Type
reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1and hit Enter. - Restart Windows 10.
- You have enabled the Long Path support in File Explorer.
From now File Explorer will be able to handle paths longer than 260 characters. Keep in mind that the change won’t affect all apps. While File Explorer comes with full support for long paths on NTFS, other apps may have issues unless their developers inlcude support for it.
If your Windows 10 include the gpedit.msc tool, you can use it instead. It is only available in Pro, Education and Enterprise versions of the operating system.
Enable Long Paths for File Explorer in Group Policy
- Press Win + R keys together on your keyboard and type:
gpedit.msc. Hit Enter.
- Expand the left panel to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem.
- Double click option Enable Win32 long paths in the right panel.
- Restart Windows 10.
I did the config and it stil does not work
🙁
This article is wrong!!
Unfortunately, the MFTNEXT Team did not try it out themselves.
It only enables long path for the file system, but not for file explorer.
The GPO path is “Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem” not “… > Explorer”
File explorer does not support longer paths, it is a legacy support thing.
I tried it as well. It probably has enabled long file path support in the file system, but not in Windows File Explorer. Unfortunately, if File Explorer cannot even support it, then it does not work for most Windows users!
This worked for me.
1) Enable long filename support.
2) Reboot
3) Start Command Prompt (CMD)
4) CD to the directory with the long filename
5) DIR /X some-long-path*.* <= just the first few letters to see the filename
6) del "\\?\C:\some-long-path.doc"
7) FILE GONE! Be careful! File is deleted directly and doesn't go to Recycle Bin.
Not administrator. Step 1 fails for me.