Have you ever tried extracting a ZIP file on your Windows 10 or 11 computer only to be met with the dreaded error message “Error 0x80010135: Path too long”? This frustrating issue often occurs when a file or folder name inside the ZIP archive exceeds the Windows maximum path limit, preventing the ZIP extraction utility from completing the operation successfully. But don’t worry — this issue has several proven workarounds that can help you safely extract your files without losing a byte of data.
Understanding Error 0x80010135: The Long Path Name Problem
The error code 0x80010135 typically happens when the extracted file or folder exceeds the Windows legacy character limit for file paths. By default, Windows Explorer supports file paths up to 260 characters. This includes all folders, subfolders, and the file name itself. When this limit is exceeded, the built-in File Explorer extraction tool fails to handle the file appropriately, triggering the error.
While Windows 10 (from version 1607) and Windows 11 include a setting to remove this limitation, it isn’t always enabled by default — especially for older systems or systems where policies are managed centrally (like in enterprise environments).
Common Signs You’re Facing Error 0x80010135
- Extraction stops midway with a popup error box.
- Error message reads “Path too long.”
- You may see a failed attempt to create folders or files during extraction.
- The ZIP archive partially extracts, leaving some files inaccessible.
Now that you understand what causes error 0x80010135, let’s walk through several easy methods to fix it.
1. Enable Long Path Support via Group Policy Editor
One of the most reliable ways to address this issue is by enabling long path support directly in Windows.
- Press Windows Key + R to open the Run dialog box.
- Type gpedit.msc and press Enter to open the Group Policy Editor.
- Navigate to:
Computer Configuration → Administrative Templates → System → Filesystem - Double-click on Enable Win32 long paths.
- Select Enabled and click OK.
Restart your computer for the changes to take effect. This method allows applications that support long paths to bypass the 260-character limit.
2. Extract Files to a Root Folder
If the file path is too long, one of the simplest solutions is to temporarily move the ZIP file to a root directory and extract it there.
- Move the ZIP file to C:\ or another drive’s root folder.
- Right-click the ZIP file and select Extract All… or use a third-party extractor.
This method shortens the path length during the extraction process, avoiding the Windows limit.
3. Use Third-Party File Extraction Tools
Built-in Windows tools often suffer from legacy constraints, but alternative extraction utilities often handle long paths more gracefully. Some popular tools include:
- 7-Zip – Free and open-source, supports long paths.
- WinRAR – Powerful archive tool that offers better control over extraction.
- PeaZip – Another free alternative with advanced extraction capabilities.
To use 7-Zip, for example:
- Download and install 7-Zip.
- Right-click your ZIP file and choose 7-Zip → Extract to “folder_name”.
These tools often bypass the character limit issue because they use more modern APIs or bypass some of the built-in Windows checks.
4. Use Command Prompt with Robocopy or xcopy
Sometimes, you can extract the files using command-line utilities that don’t enforce the same strict limitations as Windows Explorer. Tools like robocopy or xcopy can copy long file paths by using specific flags.
- Open Command Prompt as Administrator.
- Use a command like:
xcopy "C:\path\to\source" "C:\dest\path" /E /I
This method is useful when you’re trying to move or copy partially extracted content from a long path directory.
5. Modify the Windows Registry (Advanced Users)
Another way to enable long path support is through the Windows Registry Editor.
- Press Windows Key + R, type regedit, and hit Enter.
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - Find the key named LongPathsEnabled.
- Double-click and set its value to 1.
As always, be cautious when editing the registry. Backup your system or create a restore point beforehand to avoid any unintended changes.
6. Shorten Folder Names or Structure Inside the ZIP
If you have control over the ZIP archive (for example, if you created it or can recreate it), you can simplify its internal structure:
- Rename long folder names to abbreviated versions.
- Remove unnecessary nested folders before zipping.
- Flatten the folder structure where possible.
This won’t always be possible, especially when dealing with third-party ZIP archives, but it’s an effective proactive measure when creating archives yourself.
7. Use PowerShell to Unzip
PowerShell provides cmdlets that can handle ZIP extraction more flexibly than the File Explorer method.
- Open PowerShell as Administrator.
- Run the following command:
Expand-Archive -Path "C:\Path\To\File.zip" -DestinationPath "C:\ShortPath"
Make sure the destination path is as short as possible to avoid conflicts.
Pro Tips to Avoid This Error in the Future
- Always name folders and files concisely.
- Avoid unnaturally deep folder nesting.
- Enable long path support on your system proactively.
- Use reliable third-party archive programs for large projects.
Long paths are especially common in development environments, large project structures, and multi-user file sharing setups. Adopting smart folder organization practices can help you sidestep this error altogether.
Conclusion
Error 0x80010135 may seem like a roadblock, but with the right strategies, it’s a manageable problem. Whether you choose to adjust Group Policy settings, adopt advanced extraction tools, or simply restructure your folders, you’re no longer at the mercy of outdated system constraints. Embrace these techniques and give yourself one less thing to worry about when handling ZIP files on Windows.
By understanding the core cause and applying even one of the above fixes, you’ll be able to extract your archives smoothly and prevent future headaches.
