Forum Discussion
Why did 7-Zip fix my 0x80010135 zip extraction error?
Before I installed 7-Zip, every time I tried to extract a .zip file using Windows' built-in extractor, I'd get Error 0x80010135. After installing 7-Zip, the error just stopped happening. No more issues.
But that got me wondering—doesn't Windows 11 come with native support for extracting .zip files? It always has. So why was it failing in the first place? And did installing 7-Zip actually fix the error, or did it just replace the extractor entirely?
I'm genuinely curious about the technical side of this. If 7-Zip actually fixed it, why would installing a third-party app resolve what should've been a native Windows function? Anyone know what's going on under the hood?
1 Reply
The screenshot identifies the decisive detail: Explorer reports 0x80010135, “Path too long,” while extracting a nested JavaScript archive. Windows has native ZIP support, but its extractor and the destination path still have path-length constraints. Installing 7-Zip did not necessarily repair Explorer; 7-Zip uses its own extraction engine and may handle the names differently. Extract the archive with Explorer to a short destination such as C:\Temp. If that works, shorten the archive name, destination folder, or nested folder names before moving the result. Enabling Win32 long paths is not a fix because an application must also declare long-path support, and some shell operations remain constrained. Do not rename files inside the archive unless the project permits it, because imports or build scripts may depend on those paths. If extraction still fails at C:\Temp, download the archive and test its integrity. Keep 7-Zip as an extractor, not evidence that Windows was repaired.
