Error 0x80010135 in ZIP and 7-Zip: how to overcome excessively long paths

If you are trying to unzip a ZIP file in Windows and you see the message “error 0x80010135: route too long” Or, if you see the "Path too long" error, you're not alone. This mistake is very common when working with large compressed files, installers, or backups with many nested folders.

The good thing is that, although the warning is scary, in most cases There is nothing wrong with the ZIP file itselfThe problem usually lies in how Windows handles paths and the historical 260-character limit (MAX_PATH). In this guide, you'll see why this happens and how to prevent it. Tricks What are the fastest and most advanced solutions you have to forget about the error even when using 7-Zip, WinRAR, WinZip or the File Explorer itself?

What is error 0x80010135 and why does it mention "path too long"?

When you see the code 0x80010135 when extracting a ZIP fileWindows is telling you that the full path to one of the files exceeds what the system can handle by default. This path includes the drive (C:\), all folders, subfolders, and the file name itself.

In classic Windows (Win32 API), the maximum path length is 260 charactersIf the sum of the ZIP file, the ZIP file name, and the compressed internal folders exceeds this limit, the extraction process will stop and an error message will appear, both in Explorer and in tools like WinZip or some versions of 7-Zip.

This limit is inherited from the time of MS-DOS and the early versions of WindowsThis was back when file systems and applications were designed to work with very short paths. The value is known as MAX_PATH and is still present even in Windows 10 and later. Windows 11 for compatibility with older programs.

Microsoft maintains this cap because Many older Win32 applications do not support long pathsForcing them to work with more than 260 characters can lead to serious errors, buffer overflows, or unexpected failures. Therefore, although Modern file systems like NTFS allow very long pathsWindows comes with the restriction enabled by default.

This functionality has been available since Windows 10 and continues in Windows 11, but It does not come activated by defaultYou can do it in two ways: through the Group Policy Editor (Pro, Enterprise editions…) or directly from the registry (also valid for Home).

Most common causes of error due to excessively long routes

The code 0x80010135 is usually related to the length of the route, but there are several factors which can be combined and trigger it. Understanding them will help you choose the right solution for your situation.

One of the most frequent reasons is that The file or folder names inside the ZIP file are excessively longIf the ZIP file is also saved in a deep path (for example, inside many subfolders of the Desktop or Documents folder), the total character count skyrockets.

It also has a big influence on highly nested folder structureDevelopment projects, backups, or complex installations often create directories like C:\Users\Name\Documents\Project\Backup\2026\Client\… and so on ad infinitum. Each level adds characters and brings the limit closer.

In some cases, the following come into play special characters or Unicode. Although NTFS And while modern systems support Unicode, certain applications and compression tools do not handle some symbols, accents, or characters from other alphabets well when the path is already very close to the limit.

In addition to the MAX_PATH limitation itself, one must take into account the file system restrictions used: FAT32For example, it is more limited than NTFS, and if the ZIP file is on an old USB drive or a disk formatted in FAT32, it is easier to run into problems.

Finally, it should be considered that the error can also occur if the The ZIP file is damaged, if there is one. malware or if the compressor installation is corruptedIt's not the norm, but it's worth keeping in mind if everything still fails after shortening routes.

Quick fixes: what to try before messing with Windows settings

Before you start editing the registry or group policies, you can try a series of Simple tricks that usually solve the problem in secondsespecially if it's just a one-off ZIP file.

Change the name of the ZIP file to a very short one.

One direct way to reduce the route length is shorten the name of the ZIP file itself as much as possibleKeep in mind that, by default, when extracting, Windows usually creates a folder with the same name as the ZIP file, so you're adding the name twice.

To do this, open File Explorer, locate the ZIP file, right-click on it, and click on RenamePut something as simple as possible, for example 1.zip o temp.zip, and confirms.

By drastically reducing the characters in the ZIP file name and the destination folder, The total cost of the route decreases, and often the error disappears.It's a simple but very effective fix for specific cases.

Move the ZIP file to the root of the disk (C:\, D:\, etc.)

The other quick technique consists of Copy the ZIP file to a folder very close to the root of the disk or use SUBST to shorten pathsFor example, directly to C:\temp or even C:\, and extract it there.

If the ZIP file is in a path like C:\Users\YourUsername\Desktop\Projects\Client\2026\Installers\ZIPs\, each subfolder adds a significant number of characters. However, if you move it to C:\Temp, it all at once. A lot of intermediate levels are eliminated.

The steps are simple: copy or move the ZIP file to C:\temp (create the folder if it doesn't exist), rename it to a short name if you wish, and try extracting it again. If everything goes well, you can then... move the already unzipped folder to the location you want using File Explorer.

Restart your PC and repeat the extraction process.

Although it sounds basic, sometimes that's enough. Restart your computer and try again.If the error occurred after a crash, an incomplete update, or a temporary failure of the compression tool, a restart will clear any stuck processes and blockages.

Enable long path support in Windows

If you regularly work with projects, backups, or very deep structures, you'll be interested in going a step further and Enable long paths in WindowsThis increases the 260-character limit and greatly reduces the chances of seeing error 0x80010135.

This functionality has been available since Windows 10 and continues in Windows 11, but It does not come activated by defaultYou can do it in two ways: through the Group Policy Editor (Pro, Enterprise editions…) or directly from the registry (also valid for Home).

Enable long paths using the Group Policy Editor (Windows Pro)

If you're using a professional edition of Windows, you can easily activate this option from the settings. local group directives, originally designed for system administrators but accessible to any advanced user.

First, open the editor: press Win + R, writes gpedit.msc and press Enter. The Local Group Policy window will open, with a tree of options in the left pane.

Next, navigate to the route Computer configuration > Administrative templates > System > File systemIn the right panel, look for the entry called “Enable long Win32 paths”.

Double-click on that policy, select the option “Enabled”Apply the changes and close the editor. Then restart your computer. From that moment on, The rigid 260-character limit disappears for applications that support long pathsAnd many ZIP files that previously caused problems will now be extracted without issues.

Enable LongPathsEnabled in the registry (all editions, including Home)

If you have Windows Home or simply prefer not to touch the policies, you can achieve the same thing by editing a specific value in the Windows' registerHowever, it's advisable to proceed with caution here and, if possible, make a backup of the registry beforehand.

To open the editor, press Win + R, writes regedit and accept. Once inside, in the left panel navigate to the key HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > FileSystem.

On the right side, a DWORD value should appear called LongPathsEnabledIf it exists, double-click on it and change "Value data" from 0 to 1. If it does not exist, create it yourself as a "DWORD (32-bit) Value" with that name and also assign it the value 1.

Close the Registry Editor and restart your PC. From that moment on, Windows will have Extended route support enabledJust like with group policy. That doesn't mean all programs will use them, but modern applications that are already prepared (including much copying, backup, etc. software) will be able to handle paths much longer than 260 characters.

Use alternative programs to circumvent the limitation

Even if you enable long routes, the system itself File explorer and some older compression programs They can still cause problems. That's why, in many cases, it's more practical to use specialized tools that are specifically designed to work with huge routes.

7-Zip, WinRAR and other extractors

A first option is use an alternative compressor to the built-in Windows tool7-Zip and WinRAR are two classic programs that, in general, handle long paths better than the system's basic decompressor.

With 7-Zip, for example, you can download the Windows x64 version from its official website, install it, and then open the ZIP file directly with the program. Once inside, you select the file or folder, click "Extract," choose the shortest possible path (such as C:\temp), and click OK. 7-Zip is usually more permissive that the Explorer when reconstructing long internal routes.

With WinRAR, something similar happens: you open the file, locate the folder with impossible names, rename it from within the file itself using F2, and when it has a shorter name, you proceed to extract the contents.

Long Path Fixer: to reach inaccessible folders

When the problem isn't just the ZIP file, but you already have it on your disk folders that cannot be opened, moved, or deleted Because of long routes, a very practical utility is Long Path Fixer.

This free program lets you navigate to directories that Windows Explorer can't handle because the path exceeds MAX_PATH. From its interface you can copy, move, rename or delete the problematic file or folder, even if the path is tens of thousands of characters long.

Its biggest advantage is that it acts as a kind of "bridge" to these routes, without forcing you to delve into directives or the registry. Its main limitation is that It only lets you work with one directory at a time.So, with large volumes of folders, the process can be somewhat cumbersome.

Long Path Tool and other commercial solutions

Another tool designed for these cases is the Long Path Tool, which works on both Windows and macOS. Linux y It allows batch processing of many long-path files: delete, copy, move, bulk rename, etc.

The application has a free version, sufficient to solve many "Route too long" or "Origin/Destination route too long" problems, although Full features require a paid licenseIt can be a good investment if you manage large volumes of data with deep structures.

Path Length Checker: for analyzing and locating conflicting paths

If you suspect that paths on a disk or in a folder are approaching or exceeding the limit, Path Length Checker lets you List all files starting from a root directory and view the length of their paths.

You can use it with a graphical interface (by running PathLengthChecker.exe and clicking on Get Path Lengths) or from the command line. commandsThis makes it very powerful for administrators or advanced users. Although it hasn't been updated in a while, It works flawlessly on Windows 10 and 11.

Its less user-friendly aspect is that it offers quite a few options and is only available in English, which might be somewhat intimidating for novice users. On the other hand, it's one of the most comprehensive solutions for auditing long routes.

Copying files with long paths using ROBOCOPY

One of the points where the limitation of routes is most noticeable is at copy large amounts of files and foldersThe File Explorer may interrupt the copy when it encounters a path that is too long, leaving the operation unfinished.

In those situations, it's very useful to use the command line with ROBOCOPY, a robust copy tool included in Windows that allows you to automate and retry operations without constant manual interaction.

To use it, open the Symbol of the system (CMD) as administrator by searching for “cmd” in the Start menu and choosing “Run as administrator”. From there, you can launch a command like: robocopy source destination /E o robocopy source destination /S.

Parameter /E It copies all subfolders, including empty ones, while /S It only copies subfolders that contain files. ROBOCOPY is designed for handle large and complex copies, automatically retrying if it finds errors, and it usually tolerates paths close to the limit better than the graphical Explorer.

Other tricks for dealing with excessively named directories and files

In addition to all of the above, there are some additional tricks which sometimes allow you to regain control over files and folders with endless names without having to touch too many settings.

A first trick is Rename the main folder to something very shortIf you have, for example, C:\Users\YourUsername\Desktop\Extremely long projects\Folder with a kilometer-long name\…, change that parent folder to “X” or something similar. This will shorten the path of everything within it.

You can also rename the problematic file itself to something minimal. Sometimes, just removing a few characters from the name or even temporarily delete the extension (for example, changing from file_very_long.zip to a) is enough to be able to copy it to a shorter directory, and then there you restore its correct name.

Another option, if you don't want to change anything in your main Windows installation, is use a virtual machine with Windows 10/11 ProEnable long paths in the VM and mount the disk containing the files from there. Once inside the VM, you can move, rename, or restructure the conflicting folders without affecting the main machine's configuration.

And if you're still stuck, you can always resort to booting a Linux system in Live mode (Ubuntu, Mint…) from a USB drive. Linux supports much longer paths and can read NTFS, FAT32, or exFAT partitions; therefore, you can access the Windows disk, locate the inaccessible directory, and copy or delete it from there.

How other operating systems handle long routes

Although Windows suffers the most from the 260-character limit, It is not the only system with limitsSimply put, Linux and macOS have been more generous and flexible in this regard for some time now.

In Linux, modern file systems such as ext4 or XFS allow paths of up to 4096 charactersTherefore, it's very rare for a typical user to encounter this limitation. Furthermore, most console tools are designed to work seamlessly with very long paths.

On macOS, the current file system, APFSIt allows filenames of up to approximately 255 characters, but full paths can reach around 1024 characters, well above the standard Windows limit. And all this without needing to activate anything special.

That's why, when Windows refuses to touch a certain overly long directory, it often boot a Linux Live or use a Mac It is sufficient to access, manipulate or clean those routes without major dramas.

Programs that cause the most problems with long routes

Even if you enable LongPathsEnabled or use tricks, there are certain applications that They continue to be burdened by the 260-character limit because they were designed many years ago or have never been updated to use the new APIs.

The first on the list is usually himself Windows File ExplorerIt is relatively common to see messages such as "file name is too long" or "file cannot be accessed" when trying to copy, move, or delete very deep folders.

They also tend to fail legacy applications, especially enterprise software or internal tools that haven't been maintained for years. The general rule is that many programs created before 2016 don't account for long routes and simply crash when they encounter them.

Cloud services such as OneDrive or Dropbox They can also complain if they detect excessive paths. Sometimes they stop synchronization only in the conflicting folders, other times in the entire tree. Google Drive is usually more tolerant, but it's not without its flaws either.

Even certain backup tools and apps multimedia editing can refuse to process files if they cannot properly access the full pathTherefore, if you work with deep structures, it is advisable to both enable long paths in Windows and use updated software prepared for those scenarios.

Beyond ZIP: Length limit in the PATH variable

In addition to normal file paths, Windows also applies limits to the PATH variable, which is the list of directories where the system looks for executables when you type a command in CMD or PowerShell.

If you add too many paths or some of them are very long, the PATH variable can easily approach 260 characters and you'll start to see strange behavior: commands that stop working, programs that can't be found, etc.

A simple way to eliminate this limit, if you don't want to complicate things too much, is to take advantage of the Python installerAt the end of the installation wizard, there is usually an option to "Remove the Windows PATH length limit".

If you have administrator privileges, simply click that button, accept the elevation, and let the installer make the necessary changes. After that, The PATH will be able to exceed the classic limit and the tools that need it will function with greater freedom.

What to do if the ZIP file is damaged or inaccessible

Not all 0x80010135 errors are solely due to route length. Sometimes, the Is ZIP really corrupt or is it? storage has problems (damaged sector, sudden disconnection, etc.).

If you've already tried shortening paths, using 7-Zip, and enabling LongPathsEnabled, and you still can't extract the file, You can use ZIP file repair tools such as EaseUS Fixo Document Repair or other specialized solutions.

These types of programs are responsible for analyzing the compressed file, rebuild its internal structure and recover, as far as possible, the documents it contains. They usually allow batch repairs and previewing of the recovered content before saving it.

Furthermore, if you suspect that the failure may be related to malware or corrupted system entriesIt's a good idea to run a full scan with Windows Defender or with your trusted antivirus, and even check system files with tools like SFC (System File Checker).

Does it make sense to use such long names and paths?

Beyond the technical limitations, it's worth considering whether it's really a good idea. Create kilometer-long routes to organize your filesIn very specific professional environments it may make some sense, but in everyday life it usually complicates more than it helps.

If each folder is named with a complete phrase like "Files of the first term natural science work of Professor D. Santiago", navigating through the Explorer eventually becomes an ordeal: You can't see the full names; you need to widen the columns. and the search becomes slower.

In these cases, it's best to opt for a hierarchical structure: for example, a folder called "Assignments," within which is "Natural Sciences," then "1st Term," and within that, "Santiago," "Manuel," "José Luis," etc. You'll make more clicks, but You will gain clarity, you will avoid very long routes and you'll work faster on a daily basis.

In general, the shorter and more meaningful the file and folder names are, You'll have fewer chances of encountering error 0x80010135 And your workflow will be more agile, both locally and with cloud services or backups.

The dreaded "Error extracting from paths too long in 7-Zip" message is primarily a consequence of an outdated compatibility limitation in Windows and poorly designed folder structures. By combining shorter filenames, shallower paths, tools like 7-Zip or Robocopy, and, if needed, enabling long path support in your system, you can extract virtually any ZIP file and move and copy your data. without blockages and forget about these kinds of frustrating mistakes once and for all.