Error 0x80010135 "Path too long" appears when you extract a ZIP in File Explorer and at least one file inside would end up with a full path longer than Windows' traditional limit of 260 characters. The quickest fix is to shorten the path: rename the ZIP to a short name and extract it to a short folder such as C:\x. If that is not enough, extract only the deep sub-folder you need, or turn on long path support in Windows, keeping in mind that File Explorer may still struggle.
Here is why it happens and every practical way around it, starting with the quickest.
Why the path gets too long
A file's full path includes everything from the drive letter to the file name. When File Explorer extracts a ZIP, it builds that path from three pieces:
- The folder you are extracting into, such as
C:\Users\YourName\Downloads\ - A new folder named after the ZIP, such as
Client-Project-Final-Deliverables-2026-v3\ - The folder structure inside the ZIP, which may already be deep, such as
Design\Exports\Web\High-resolution\Homepage-hero-variations\, plus the file name
Add those together and 260 characters goes quickly. Your user name and a OneDrive-synced Documents or Desktop folder add even more, because those paths start with something like C:\Users\YourName\OneDrive - Company Name\Documents\ before anything from the ZIP is added.
The archive itself was probably fine where it was made. It may have been created on a Mac or Linux machine, or on a Windows PC with long path support enabled, where the long paths were not a problem. Windows itself can store longer paths, but many programs, including parts of File Explorer, still enforce the old limit.
Fix 1: Shorten the destination and the ZIP name
This solves most cases in under a minute.
- Create a short folder at the root of a drive, for example
C:\x. - Move the ZIP into it.
- Rename the ZIP to something short, such as
p.zip, because File Explorer uses the ZIP's name for the extraction folder. - Right-click it, choose Extract All, and make sure the destination shown is
C:\x\p, not a long default.
Going from C:\Users\YourName\Downloads\Client-Project-Final-Deliverables-2026-v3\ to C:\x\p\ saves about 70 characters, which is often all you need. After extracting, you can move individual sub-folders to wherever you want them, as long as the final paths stay under the limit.
Fix 2: Extract only the part you need
If you do not need the whole archive, skip the deep folders altogether. Open the ZIP, navigate into the sub-folder you actually want, and drag that folder (or just the files in it) to a short location. Because the dragged folder starts fresh at the destination, the long chain of parent folders is left behind.
This works in File Explorer, but an archive program makes it easier with large archives. Universal Zip lets you browse any archive like a normal folder, search by name to find the file you need, and drag out just that item without extracting everything else.
Fix 3: Map a drive letter to a deep folder
If you must extract into a long location, for example a project folder on a network share, you can shorten it with the subst command, which makes a folder appear as its own drive letter:
- Open Command Prompt.
- Run
subst X: "C:\Users\YourName\Documents\Clients\Big Client\2026 Projects" - Extract the ZIP to
X:\. The files land in the real folder, but the path Windows sees during extraction is much shorter. - Remove the mapping afterwards with
subst X: /d.
Be aware that the files still live at the long real path. Some programs will struggle to open them there later, for the same reason extraction failed.
Fix 4: Enable long path support in Windows
Windows 10 version 1607 and later, and Windows 11, can lift the 260-character limit for programs that are written to support it.
Windows Pro, Enterprise and Education: Group Policy
- Press Windows+R, type
gpedit.mscand press Enter. - Go to Computer Configuration → Administrative Templates → System → Filesystem.
- Open Enable Win32 long paths, set it to Enabled and click OK.
- Restart the PC.
Any edition: Registry
- Press Windows+R, type
regeditand press Enter. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. - Double-click
LongPathsEnabled(create it as a DWORD (32-bit) value if missing) and set it to1. - Restart the PC.
This setting only helps programs that declare long path support. File Explorer has historically not fully supported long paths, so the built-in zip extractor may still fail after the change. Treat this as a helpful extra rather than a guaranteed fix, and back up the registry before editing it.
Fix 5: Shorten the folders inside the archive
If you created the ZIP, or can ask the sender to recreate it, the permanent fix is a flatter structure:
- Remove unnecessary nesting, such as a folder that only contains another folder.
- Shorten long folder names (
High-resolution-exports-for-websitecan beWeb-hires). - Archive from a level closer to the files, rather than including several parent folders.
This also helps anyone else who receives the archive.
Which fix to try first
| Situation | Best fix |
|---|---|
| You need everything, anywhere is fine | Fix 1: short folder and short ZIP name |
| You only need some files | Fix 2: extract just that sub-folder |
| Files must go into a specific long folder | Fix 3: subst drive letter |
| You hit this error often | Fix 4 plus Fix 1 |
| You control the archive | Fix 5: flatten and rename |
Related errors
Path problems sometimes show up under other names. "The destination file could not be created" or "Windows cannot complete the extraction" can have the same cause, as can failures on specific files when extracting archives made on a Mac or Linux PC, which may also contain characters Windows does not allow in names. Our guide to Windows cannot complete the extraction covers those cases. If you are extracting a whole folder of archives and a few fail, see extracting multiple ZIP files at once for how to handle failures in a batch. Universal Zip's batch extract can send every archive in a folder to its own sub-folder in one run, so pointing it at a short destination such as C:\x avoids the problem for the whole set.
Frequently asked questions
What causes error 0x80010135?
A file inside the ZIP would end up with a full path longer than Windows' traditional 260 character limit once it is extracted to your chosen folder.
What is the quickest fix?
Extract to a very short folder such as C:\x, and give the ZIP a short name, so the total path length drops below the limit.
Does enabling long paths fix it?
Not always. The LongPathsEnabled setting helps programs that support long paths, but File Explorer's zip tool may still fail.
