Resolving the “Path Too Long” Error When Extracting Zip Files in Windows 10
As Windows users, we’ve all encountered our fair share of errors and warnings. One of the more common issues that can pop up when working with archives is the cryptic "Error 0x80010135: Path too long" message. This frustrating error blocks you from unzipping files and folders, potentially causing data loss.
In this post, we’ll explore the "path too long" error in depth. We’ll look at what causes it, who experiences it, and most importantly – how to fix it for good. By the end, you’ll understand why it happens and have actionable solutions to resolve it yourself. Let’s get started!
What Triggers the “Path Too Long” Error in Windows 10?
The "path too long" error occurs when attempting to extract a zipped file whose path exceeds the 260 character limit set by the Windows API (application programming interface).
Why does Windows 7 have a long path error?
This problem occurs because of an issue in how Windows handles the long-path errors. To resolve this issue for Windows 8.1, Windows Server 2012 R2, Windows 8, andWindows Server 2012, install the update rollup. To resolve this issue for Windows 7 and Windows Server 2008 R2, install the hotfix that is described in this article.
How to fix path too long error Windows 10?
The easiest way to fix Windows’ “Path Too Long” error is by renaming your ZIP file. If your ZIP file has a lengthy name, shortening the name will allow you to bypass the above error. Renaming your file doesn’t change the contents within. Open a File Explorer window and find your ZIP file. Right-click your file and choose Rename.
The API acts as the interface between Windows processes and the core operating system. Part of its job is enforcing the maximum path restriction. This prevents instability from extremely long file names or folder structures .
You’re most likely to encounter error 0x80010135 when:
- Extracting archives containing very long file names
- Unzipping folders with deeply nested subdirectory structures
- Working in folders that already have long paths
However, this isn’t the only potential cause. Malware infections, corrupt system files, and faulty software installations can also trigger it . Upgrading from older Windows versions to Windows 10 may surface the issue too.
Overall, the underlying problem is the 260 character path limit. As long as a file or folder path stays under this length, you likely won’t see this error.
Who is Most Affected by the “Path Too Long” Problem?
The "path too long" error mostly affects power users working with large archives. For example:
- Developersunpacking repositories with extensive folder hierarchies and verbose naming conventions.
- Digital artistsextracting asset packs containing tons of multimedia files.
- IT professionalsdeploying software bundles and disk images.
However, regular users aren’t immune. Anyone transferring zipped folders from old machines or unzipping archives from unknown sources might encounter it.
How do I fix 0x80010135 error in 7-zip?
Bring up the directory in which your browser downloaded the 7-ZIP setup file. Double-click on the 7z2300-x64.exe file. Click on Install within the 7-Zip setup window. Open the 7-Zip archive extraction software. Select the ZIP archive for which the 0x80010135 error occurs in 7-ZIP.
How do I enable long paths in Windows 10?
1. Hit the Windows key, type gpedit.msc and press Enter. 2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem 3. Double click the “Enable long paths Win32” option and enable it. 4. Reboot. Was this reply helpful? I can find the above option in my system and I enabled it.
Thankfully, this issue isn’t entirely unsolvable. Windows 10 provides a few helpful workarounds.
4 Ways to Fix the “Path Too Long” Error in Windows 10
If you come across error 0x80010135 while decompressing a zip file, don’t panic. Here are some reliable troubleshooting methods.
1. Extract Into the Root Folder
When choosing an extraction location, pick a folder closer to the root directory. This shortens the overall file path substantially.
On the extract pop-up window, click "Browse" and select a top-level folder like your C: drive. The deep nesting gets eliminated, circumventing the path limit.
2. Enable Long Path Support in the Registry
You can entirely remove the 260 character restriction with a quick registry edit.
First, open the Registry Editor by pressing Windows + R and entering "regedit". Navigate toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
Right click the FileSystem key and make a new DWORD value namedLongPathsEnabled, setting it to 1.
This tweak lets you work with arbitrarily long paths. But use it with caution, as it may impact stability.
Why is my file path longer than 260 characters?
The file path is longer than 260 characters . Your Windows system does not support file path with name longer than 260 characters. This error mainly occurs due to Long named file paths. when you use Explorer or WinZip to extract files it may throw an error which says a file path that exceeds the maximum character limit.
How long should a file name & full path be?
Windows has a default limit on the length of the filename & full path. Since the file is “way down in the path”, you might need to make Windows accept path\filename greater than 260 characters to access the file, or you might need to refer to the path by an alias as an Environment Variable.
What causes error 0x8001013?
Once exceeded, you will encounter the error 0x8001013. In addition, incorrect or incomplete installation of the software can leave invalid entries, triggering the path too long error. Other factors like improper system shutdown, accidental deletion, and virus attack are also responsible for the error.
Why is my archive 0x80010135 path too long?
If you ever encounter an error while using an archive that says error 0x80010135 path too long, you don’t need to panic. It is easy to solve the error that may appear due to files with long path names. Simply renaming the archive to a short name or enabling the support for long file paths in your computer should solve the issue.
3. Use a Third-Party Zip Tool
Programs like 7-Zip and WinRAR aren’t limited by the Windows path length. They’ll extract zipped files regardless of nesting depth or name length.
Download and install your preferred tool. Then right click your zipped folder and pick "Extract Here", choosing the new extractor. Enjoy unlimited path freedom!
4. Rename the Archive Contents
If you can view the zip file contents before extracting, shorten any excessively long names. This reduces the total path length.
Look for verbose filenames, redundant file numbering schemes, and deeply nested folders to target. But be careful not to distort critical folder structures.
With these solutions, you should be prepared to tackle error 0x80010135 head on. No more path length woes holding you back.
Prevent “Path Too Long” Errors by Planning Ahead
While the fixes above resolve existing issues, a bit of forethought can prevent them entirely. Here are some best practices:
- Extract zipped files directly into your main storage drives whenever possible.
- If organizing archives, use concise naming schemes without repetition.
- Enable long path support before working extensively with deep hierarchies.
- Periodically review folder structures and prune unnecessary nesting.
A little care goes a long way. But should issues arise anyway, this guide has you covered. Never let the "path too long" error stand in your way again!
How do I fix a zip file error?
Try renaming the zip file to a shortest name and extract again. Thanks Mathi_C – This fixed the error for me. On closer inspection of the .zip file I was trying to extract, it contained several parent/child folders and obviously was increasing the path of the file that was erroring to an unacceptable level. Was this reply helpful?
Are file path names too long in Windows 10 Pro?
All Microsoft MS operating systems have had problems with file path names that are ‘too long’ for years. However, they seem to be worse in Windows 10 Pro. I have a number of files – produced in Windows 8.1 – that I cannot move, copy or rename, as follows:
What does 0x80010135 mean?
Reduce the Length of the ZIP’s File Name Error 0x80010135 usually occurs because the path for the extracted folder exceeds Windows’ 260-character limit. That’s why the error message says the path is too long, and this issue will more likely arise for ZIP archives with long file names.
The Takeaway
Error 0x80010135 strikes when extracting archives with paths surpassing Windows 10’s 260 character limit. IT professionals, developers, and power users encounter it most frequently. Thankfully, solutions exist like extracting to root folders, enabling long path support, using alternative zip tools, and shortening names. With proper preparation, you can sidestep the problem entirely and work seamlessly.
We all face hiccups when working with zipped files. But by understanding the causes and applying these fixes, you can conquer the cryptic "path too long" error. Our Windows will be frustration-free once more!
