Many Windows 11 and Windows 10 users occasionally experience ZIP-related issues. An example of such an annoying problem is the 0x80010135 ZIP extraction error. This error usually appears when users try to extract files from a ZIP archive and a message like this appears: “An unexpected error prevents you from copying the file. Error 0x80010135: path too long.” Fortunately, several proven methods can help solve this problem. Below is a comprehensive guide on how to fix the 0x80010135 ZIP extraction error in Windows 11/10.
Understanding the 0x80010135 error
Before diving into the solutions, it is essential to understand what this error typically means. The 0x80010135 error essentially stems from a limitation in the length of the Windows file path. By default, Windows uses the MAX_PATH variable that limits paths to 260 characters, including the directory directories and file name. If the ZIP file you are trying to extract contains files with paths longer than this threshold, you will likely encounter the error 0x80010135.
Methods to fix the 0x80010135 error
Here are several effective solutions that can help solve this extraction problem:
1. Extract the ZIP file to the root folder
One of the simplest solutions is to extract the ZIP file to a location closer to the root of the drive, such as C:\. The idea here is to shorten the file path so that it doesn’t exceed the character limit.
Steps:
- Move your ZIP file to C:\ or D:\
- Right-click on the ZIP file
- Select Unpack everything…
- Set the extraction destination to C:\
2. Enable long file paths in Windows
Windows 10 and 11 support long file paths, but the feature is not always enabled by default, especially on older systems or educational/business devices with group policies.
Enable long file paths:
- Press Win + R and type
gpedit.mscto open the Local Group Policy Editor - Navigate to:
Computer configuration → Administrative templates → System → File system - Double click Enable Win32 long paths
- Set it up Enabled and click OK
Remark: This method only works on Windows Pro, Enterprise and Education. If you are using Windows Home, continue with the registration method below.
3. Change the registry to allow long paths
If you are using Windows Home or if Group Policy is not available, you can achieve the same result through the Registry Editor.
Steps:
- Press Win + R and type
regeditand then press Enter - Navigate to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - Look for a value with the name
LongPathsEnabled - If it is not there, right click → New → DWORD value (32-bit). and name it
LongPathsEnabled - Double click on it and set the value to 1
- Restart your computer
4. Use a third-party file archiver
If the integrated Windows zip utility doesn’t work, consider using alternative extraction tools. These can often handle long journeys more efficiently.
Popular options include:
How to use 7-Zip:
- Download and install 7 zipper
- Right-click on the ZIP file
- Select 7-Zip → Extract Files…
- Choose a root folder (e.g. C:\Unpacked)

5. Rename and shorten folder/file names in the ZIP
If there are only a few files causing the problem due to their long names, try renaming them. You can do this partially without extracting:
Steps:
- Open the ZIP archive with 7-Zip or WinRAR
- Browse long paths and rename them to shorter names
- Then unpack normally
6. Use command line extraction via PowerShell
This method bypasses some limitations of Windows Explorer when extracting ZIP files.
Steps:
- Press Win + X → Select Windows terminal (administrator)
- Run the following command:
Expand-Archive -LiteralPath "C:\YourZipFile.zip" -DestinationPath "C:\TargetFolder"
You may need to replace the path with your own ZIP file and extract the location.
Prevention tips
To avoid the 0x80010135 error in the future, consider applying the following practices:
- Avoid nesting too many subfolders in your ZIP archives
- Use shorter folder and file names when compressing and extracting files
- Enable and check long path support regularly if you reinstall or reset Windows
Conclusion
The 0x80010135 ZIP extraction error may seem frustrating at first, but with the right approach it is completely manageable. Mostly it comes down to Windows default path length limitations. By understanding and applying the solutions above (from enabling long paths to using third-party tools), users can continue working with compressed files without any further problems.

Frequently asked questions
What causes the 0x80010135 error on Windows?
The error usually occurs due to file paths that exceed the Windows limit of 260 characters. It can also be caused by problematic ZIP archives or permission issues.
Can I fix this error without downloading third-party tools?
Yes. You can fix the error using built-in methods like extract to the root folder or enabling long path support via registry or group policy.
Is it safe to edit the Windows registry to fix this?
Yes, as long as you follow the steps carefully. Always make a backup of your registry before making any changes to avoid unintended consequences.
Does enabling long path support affect other applications?
It improves compatibility with modern apps and does not negatively impact Windows itself. However, some older applications may still not support long paths properly.
Is there a maximum limit even after long paths are enabled?
Yes, the absolute maximum is increased to 32,767 charactersalthough very few workflows approach this level. There may still be practical limitations of certain apps or libraries.
Where should we steer?
Your WordPress deals and discounts?
Subscribe to our newsletter and receive your first deal straight to your email inbox.
#Fix #0x80010135 #ZIP #Extraction #Error #Windows #Newsify


