Fix Path Too Long Error While Extracting Zip File
Published: May 25th, 2026 • 5 Min Read
Summary: This articleis a simple manual that explains the reasons why Windows has restrictions for long paths when extracting data and offers methods to resolve the problems through manual intervention or recovering lost files with some type of software.
Overcoming Windows Archive Extraction Blocks
There you are about to begin your latest project after downloading an archive file, and just as you’re about to extract the compressed file, up pops a message from Windows stopping you dead in your tracks. Rather than getting started, you now see the message indicating a path too long error with respect to the extraction process. This has just limited you from accessing critical information for your work, thus stopping you from being able to complete your intended tasks as either a home user or an enterprise user. While this is a common nuisance, it’s also something that can be very easily resolved.
Why Does Path Too Long Error Occur During Zip Extraction?
The default limitation of file path lengths in the Windows operating system is set to a maximum of 260 characters, which encompasses the total number of characters that may exist in the drive letter, folder hierarchy, file name, and file extension. When an archive file has a large number of nested directories added into path variables, then the extraction path length limitation will be exceeded.
The Windows operating system utility designed for extracting files does not have the ability to handle long strings when generating an extraction path. As such, it generates a specific error code that identifies the reason for a failure. Usually, an error 0x80010135 will result when attempting to extract an archive, which means users need to find ways to shorten the length of the structure or change how the Windows operating system handles long path names when using Deep Directory Paths.
Quick Pre-Implementation Checklist
Prior to making modifications to your system, perform the following simple checks to ensure a smooth process:
-
Confirm that you hold administrator rights on your computer.
-
Check free disk space available on the target drive.
-
Terminate all open program sessions that use the archive file.
-
Create a backup or duplicate of the original ZIP file before modifying the archive to help avoid any unintentional loss of data.
Step-by-Step Manual Methods to Resolve the Error
Method-1: Move the ZIP Archive to the Root Drive
- Right-click your ZIP archive and select Cut.
- Navigate directly to your local drive (e.g.,
C:\). - Paste the file there and try extracting it again to minimize the initial folder path length.
Method-2: Rename the ZIP File and Parent Folders
- Right-click the archive file and choose Rename.
- Give it a very short name (like
data.zip). - Do the same for any long parent folders to dramatically reduce the total character count.
Method-3: Enable Long Paths via Registry Editor
- Press Win + R, type
regedit, and hit Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - Locate the value named
LongPathsEnabledand double-click it. - Change the Value Data from
0to1and click OK.
Precautions to Take During Manual Fixes
Note: Making changes to the registry of a computer comes with risk; therefore, you should create a copy of your registry prior to modifying the registry. Also, take care not to remove important subdirectories when renaming files nested deep within a folder.
Limitations of Using Manual Workarounds
While manual changes may help you get around immediate obstacles, each of these methods also has considerable disadvantages:
-
Changing the registry may not always be successful when using older versions of third-party applications.
-
Repeatedly renaming directories often causes the disorganization of data and business-dependent hierarchies.
-
In the event that extracting the archive fails or is interrupted, the extracted data is likely to be corrupted, which would make using methods other than manually extracting the files impossible.
The Professional Alternative: BitRecover Tool
After you’ve tried everything from the manual workaround to multiple unsuccessful attempts to extract the information from the archive itself using other methods to recover lost ZIP files, and your data is no longer recoverable or accessible to you, you have BitRecover Zip Repair Wizard.
It automatically detects and populate the locations of your corrupted documents with the appropriate binary characters (instead of the ASCII) to ensure that your proprietary data is sortable by either logical byte position or order by their original file structure.
You can preview the recoverable files and you will be able to locate all of your restored documents at the original file location.
Watch YouTube Video: Steps to Repair Compressed (Zipped) Archive in Windows
Frequently Asked Questions
Q: What is the 260-character limit for a path in Windows?
The Windows API was architecturally designed to be backwards compatible with prior operating systems when designed. Therefore, limitations on the character length of a file path exist.
Q: Will third-party extraction software allow you to extract information with file paths exceeding the 260-character limit?
Yes; despite third-party extraction tools being unable to repair files’ corrupted file structure. Many of them, like 7-Zip, are specifically designed to better accommodate for the long character limits of file paths than Windows Explorer.
Conclusion
A limitation error for a file while trying to extract it can make your day longer, but with quick manual methods such as moving the files from one directory to another, or enabling certain registry settings, you can free up that path. Unfortunately, if your data is still locked or corrupted, using an automated tool such as BitRecover will allow you to retrieve your valued data quickly and securely.
