sodcalculator

10 Tech How-To

Error 0x80010135 Path Too Long: Fixes

Guide 10-51695 · Updated · Step by step

Error 0x80010135, often accompanied by the message “The file name(s) would be too long for the destination folder,” occurs when Windows hits its MAX_PATH limit of 260 characters for a file path. You can fix it by shortening the path, enabling long paths in Windows 10/11, or using a tool that handles long paths automatically.

What Causes Error 0x80010135

Windows has historically limited the total length of a file path—including drive letter, folders, subfolders, and file name—to 260 characters (MAX_PATH). This limit is a legacy from older Windows versions and is still enforced by many applications, even though modern NTFS supports paths up to 32,767 characters. Error 0x80010135 appears when you try to copy, move, or extract files whose full path exceeds 260 characters.

The error is especially common when extracting ZIP archives, syncing cloud folders (like OneDrive or Dropbox), or copying project folders with deep directory structures. For example, a path like C:\Users\YourName\Documents\Projects\Website\Assets\Images\Icons\Final\2024\New\icons_final_v2.png can easily exceed the limit even if the file itself is small.

How Windows Enforces the 260-Character Limit

The limit applies to the absolute path, which includes the drive letter, colon, backslash, and all folder names. Each component (folder name or file name) can be up to 255 characters, but the total path must not exceed 260. When you copy or move files, Windows Explorer checks the destination path length and throws error 0x80010135 if it would be too long.

Some applications bypass this limit by using the Windows API with the \\?\ prefix, which tells Windows to use the long-path-aware version of the API. However, many programs—including older versions of WinRAR, 7-Zip, and even some Microsoft utilities—do not use this prefix and therefore fail.

How to Fix Error 0x80010135

Here are the most effective methods, in order of simplicity:

  1. Shorten the destination path – Move the files to a shorter path, such as directly to C:\Temp\ or D:\. Rename deeply nested folders to single characters (e.g., a, b) to reduce the total length.
  2. Enable long paths in Windows 10/11 – Open the Group Policy Editor (gpedit.msc) and navigate to Computer Configuration > Administrative Templates > System > Filesystem. Double-click Enable Win32 long paths, set it to Enabled, and restart. This allows applications that support it to use paths longer than 260 characters.
  3. Use a file manager that supports long paths – Tools like 7-Zip File Manager, FreeCommander, or Total Commander can handle long paths because they use the \\?\ prefix. You can copy or extract files using these tools instead of Windows Explorer.
  4. Extract ZIP files with a long-path-aware tool – If the error occurs when extracting an archive, use 7-Zip or WinRAR (with the option to enable long paths) instead of the built-in Windows extractor.
  5. Map a network drive or use a subst – Use subst to assign a drive letter to a deep folder, effectively shortening the path. For example, subst X: C:\Users\YourName\Documents\Projects\Website\Assets then access files via X:\.

Common Problems and Misconceptions

One common misconception is that error 0x80010135 means the file is corrupted or the drive is full. In reality, it is purely a path-length issue. Another misconception is that enabling long paths in Windows automatically fixes all applications—it does not. The application itself must be compiled with long-path awareness; otherwise, it still fails.

Another issue is that the error can appear when copying to a USB drive or network share that also has its own path length limits. Even if you enable long paths, some external devices or older network protocols (like SMB1) may still enforce the 260-character limit.

How to Avoid the Error in the Future

To prevent this error from recurring:

  • Keep folder structures shallow. Avoid nesting folders more than 3-4 levels deep.
  • Use short, meaningful names for folders and files. Avoid long descriptive names that push the path over the limit.
  • Regularly archive or clean up old projects that have deep structures.
  • If you work with code repositories, be aware that package managers (like npm) can create very deep paths; consider using a short root folder like C:\src\.
  • When creating ZIP archives, use compression tools that store relative paths, and extract to a short root folder.

Alternatives to Fixing the Error

If you cannot shorten the path and enabling long paths does not work, you have a few alternatives:

  • Use the command line – The robocopy command can copy files with long paths if you use the /256 switch to disable the path limit. For example: robocopy source dest /E /256.
  • Create a symbolic link – Use mklink /D to create a symbolic link to a deep folder, then access it via a short path.
  • Move the entire folder to a shorter root – If the folder is on a drive with a long path, move it to the root of the drive (e.g., C:\) and then access it.

Frequently Asked Questions

Does error 0x80010135 mean my file is corrupt?

No. The error is solely about the path length. Your file is fine; it’s just that the destination path is too long for Windows to handle.

Will enabling long paths in Windows break anything?

Enabling long paths is generally safe, but some older applications may behave unexpectedly because they assume paths are short. If you encounter issues, you can disable the setting again.

Can I use this error fix on Windows 7 or 8?

The Group Policy setting to enable long paths is only available in Windows 10 and 11. On older versions, you must rely on third-party tools or shorten the path.

Why does the error occur when extracting a ZIP file?

ZIP archives can contain files with very long paths. The built-in Windows extractor enforces the 260-character limit, so it fails. Using 7-Zip or WinRAR with long-path support solves this.

Is there a way to permanently remove the 260-character limit?

You can enable the long-path policy in Windows 10/11, but it only affects applications that are long-path aware. There is no system-wide way to force all applications to accept longer paths.

What is the maximum path length in Windows?

With long paths enabled, Windows can handle up to 32,767 characters, but each individual folder or file name is still limited to 255 characters.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →