• Home  / 
  • Windows 10
  •  /  [Fixed] – The filename would be too long for the destination folder

[Fixed] – The filename would be too long for the destination folder

last year
The filename would be too long for the destination folder

Getting Error??

This guide will help to add 260 characters in Windows 10 for file paths. Are you getting error message “The filename would be too long for the destination folder. You can shorten the fine name and try again, or try a location that has a shorter path”, while copying file from one location to another. Then, it’s certainly because file path does not support longer names.

http://windowsitexperts.com/wpcontent/uploads/2016/09/HowtoMakeWindows10AcceptFilePathsOver260Characters.png” alt=”filename too long” width=”624″ height=”288″ />

Imagine a file name could only be as long as you want it to be. To be very honest, the up to 260 character file path since Windows 95, was way much better than the previous 8.3 character limit. 8 for the filename and 3 for the extension. Seriously? Urghhh! Here comes http://windowsitexperts.com/whatwillwindows10systemrequirements/” target=”_blank” rel=”noopener”>Windows 10, where you can, wait for it, increase the amount.

You May Also Like this Video

Limitations – The filename would be too long for the destination folder

Having said that, Windows still has some limitations imposed such as what specific characters can be used in the name of a file and overall length of paths. Unlike in earlier versions of Windows, in Windows 10 Insider Preview, it is very much possible to use Group Policy or a registry hack to eliminate the limit. Awesome. Now you’re talking!

Not every application installed is featured with this but a lot of them are under it. In order to function the 32-bit applications have to be manifested, which means simply that the developer has indicated that the application supports longer paths. Most 32-bit applications will experience no problem at all. At least you can try it out, no harm in that.

The worst case that can happen is that the app will not be able to open or save files that have been saved in locations where full path exceeds 260 character limit. Microsoft explains this feature as, “http://blogs.msmvps.com/eightforums/2016/05/29/howtoenableordisablentfslongpathsinwindows10/” target=”_blank” rel=”noopener”>Enabling NTFS long paths will allow manifested win32 applications and Windows Store applications to access paths beyond the normal 260 char limit per node. Enabling this setting will cause the long paths to be accessible within the process.”

http://windowsitexperts.com/wpcontent/uploads/2016/09/HowtoMakeWindows10AcceptFilePathsOver260.png” alt=”The filename would be too long for the destination folder” width=”624″ height=”351″ />

The anniversary update was promised to be up to date when it was released but in the latest Insider build it can be enabled using Group Policy.

Let’s see how to add 260 characters in Windows 10

1. Hit that beautiful Windows key, type gpedit.msc and press Enter.

2. Run and navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.

3. Bang and double click the Enable NTFS long paths option and enable it.

Have a version of Windows that has no access to Group Policy? Go on, leave everything behind and edit the registry instead.

1. Once again you need to hit the Windows key, type regedit and press Enter.

http://windowsitexperts.com/wpcontent/uploads/2016/09/HowtoMakeWindows10AcceptFilePathsOver.png” alt=”260 characters in Windows 10″ width=”390″ height=”622″ />

2. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\ CurrentVersion\Group Policy Objects\ {48981759-12F2-42A6-A048-028B3973495F} Machine\System\CurrentControlSet\Policies

3. Select the LongPathsEnabled key, or create it as a DWORD (32-bit) value if it does not exist.

4. Set that value to 1 and close the Registry Editor.

All the way it is really good to see the applications enabled with this kind of feature.

4 comments

Leave a comment: