You download a ZIP file, double-click to open it, and when you try to extract its contents, Windows displays the message: Error 0x80010135: Route too longThe most frustrating thing is that the file seems fine and there's no apparent problem with the computer. So, what is error 0x80010135 when extracting a ZIP file and how do I fix it?
What does error 0x80010135 mean when extracting a ZIP file?
Let's start by reviewing what error 0x80010135 means when extracting a ZIP file. This error appears when Windows encounters a file path too long During the extraction of a compressed file. To recap, a path is the address that indicates where a file is located within the system. It includes the storage drive, folders, and the file name itself.
Let's take an example. Extracting a document in C:\Archivos\Informe.pdf than to do it within a structure like C:\Users\Usuario\Downloads\Proyecto\Documentación\Final\Informes\2026\Revisiones\Informe_final.pdfIn the second case, the path takes up many more characterswhich poses a problem in some cases.
When a ZIP file contains dozens of nested folders and long filenamesIt is possible that some elements may exceed the limits supported by the extraction tool. In the case of Windows, File Explorer includes its own decompression mechanism with a maximum path length of 260 characters (MAX_PATH).
So, when the full path of the compressed file exceeds that limit, the system refuses to write to the disk and throws error code 0x80010135 when extracting a ZIP file. How do you fix it? The good news is that you don't need to be a computer expert to fix it. Below, we show you how. more effective solutions: from the simplest to the most profound.
Error 0x80010135 when extracting a ZIP file: how to resolve excessively long paths
Before modifying system settings, let's look at the quickest way to resolve error 0x80010135 when extracting a ZIP file. The first thing you can try is Move the compressed file to a location with a shorter pathIt's a mistake to extract files directly to the desktop or a deeply nested downloads folder. What's best?
Try creating a temporary folder with the shortest possible name in the root directory of drive C (for example, C:\Zips). Then, Copy the ZIP file that is causing the problem there and perform the decompression.This can significantly reduce the base path, freeing up space for the internal filenames of the compressed package.
Another good idea is shorten the name of the compressed fileBy default, Windows' built-in decompression mechanism creates a folder with the same name as the compressed file. You can rename it to a shorter form, such as... 1.zip o tem.zip before extracting it. And once the process is finished, rename the resulting folder back to the original name.
Definitive solution: Enable long route support in Windows
Another way to resolve error 0x80010135 when extracting a ZIP file is to enable long path support in Windows. This workaround comes with Windows 10/11, but it has a catch:It works better for third-party programs than for File Explorer itself.Anyway, you've got nothing to lose by trying it, because if it works, it'll be a permanent solution.
- Press Win + R, type
regeditand press Enter. - Navigate to route:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - In the right panel, look for
LongPathsEnabledIf it doesn't exist, right-click in the blank space, select New – DWORD (32-bit) Value and name itLongPathsEnabled. - Double-click on it and change the value from 0 to 1.
- Restart your computer for the adjustment to take effect.
With this adjustment, The theoretical limit of the system can reach 32767 charactersHowever, it's worth noting that the traditional interface used by File Explorer may still tend to behave according to the old 260-character standard. So, you might still encounter problems when trying to extract files using the right-click menu.
Error 0x80010135 when extracting a ZIP file: Use a third-party decompressor
There's nothing you can do: Windows File Explorer is very strict about the 260-character limit. So, if none of the above works and you're still seeing error 0x80010135 when extracting a ZIP file, the best thing to do is resort to professional decompression softwareThis is the most practical solution and the one that solves the problem 100%.
Alternatives? 7-Zip o WinRAR These are the preferred method. These tools use their own decompression engines and do not depend on the native Windows system. When using them, right-click on the compressed file and select "Extract to…", or use the 7-Zip graphical interface. Typically, These applications can handle paths exceeding 260 characters without problems..
Error 0x80010135: Resolves the problem of excessively long routes
Indeed, resolving error 0x80010135 when extracting a ZIP file is possible, especially if you install a third-party program like 7-Zip. However, while the decompression might be successful, keep encountering mistakesPerhaps some files cannot be opened, or you see the message "The path is too long" when trying to access them in File Explorer. What's going on?
This means that the destination route is actually too deep. In these particular cases, you have to manually rename the parent folders level by levelYou need to shorten the file names (change "Project Documents" to "Docs", for example) to shorten the overall path. This way, File Explorer will be able to recognize and work with these files normally.
And if the problems persist, perhaps it's because the ZIP file is corruptedTo verify, try downloading it again from the original source. Or, if you're using 7-Zip, you can right-click on the file, open its menu, and look for the option to test the compressed file. The application will check its integrity and tell you if it finds any errors.
In short, the priority is: move to C:\ and shorten the name; if that doesn't work, modify the registry or, better yet, switch to 7-Zip. one of its alternativesDon't spend too much time struggling with the built-in decompression mechanism. Use a third-party tool This is usually the fastest way to resolve this error.
Index