Updated Jul 5, 2017

Before Windows 95, Windows only allowed file names that were eight characters long, with a three character file extension–commonly known as an 8.3 filename. Windows 95 abandoned that to allow long file names, but still limited the maximum path length (which includes the full folder path and the file name) to 260 characters. That limit has been in place ever since. If you’ve ever run into this limit, most likely it was when you were trying to copy deep folder structures into other folders, such as when copying the contents of a hard drive to a folder on another drive. The Windows 10 Anniversary Update finally adds the option to abandon that maximum path length.

There is one caveat. This new setting won’t necessarily work with every application out there, but it will work with most. Specifically, any modern applications should be fine, as should all 64-bit applications. Older 32-bit applications need to be manifested in order to work, which really just means that the developer has indicated in the application’s manifest file that the application supports longer paths. Most popular 32-bit apps should experience no problem. Still, you don’t risk anything by trying the setting out. If an application doesn’t work, the only thing that will happen is that it won’t be able to open or save files that are saved in places where the full path exceeds 260 characters. //

In the Registry Editor, use the left sidebar to navigate to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

On the right, find a value named LongPathsEnabled and double-click it. If you don’t see the value listed, you’ll need to create it by right-clicking the FileSystem key, choosing New > DWORD (32-bit) Value, and then naming the new value LongPathsEnabled .

In the value’s properties window, change the value from 0 to 1 in the “Value data” box and then click OK.

You can now close Registry Editor and restart your computer (or sign out of your account and sign back on).

If you ever want to reverse the changes, just head back to the LongPathsEnabled value and set it from 1 back to 0.