Quick answer
Your ZIP is not corrupt—the full folder path is simply longer than 260 characters. Copy the ZIP to C:\z, rename it to a.zip, and extract into C:\z. If internal subfolders alone exceed 260 characters, extract with Karuzip or 7-Zip (or use View contents to extract only the files you need) rather than File Explorer's Extract All wizard.
Seeing a generic error instead of Path Too Long? Check our Error 0x80004005 guide or Windows 11 ZIP troubleshooting checklist.
1Why Windows 11 hits the 260-character limit during ZIP extraction
Although NTFS supports file paths up to 32,767 characters, legacy Win32 APIs—and many File Explorer shell operations—still default to MAX_PATH (260 characters: drive letter, colon, backslash, 256 characters of path, and a terminating null). When you run Extract All on a ZIP sitting inside your Downloads or OneDrive folder, Windows adds three layers together:
| Path layer | Typical example | Characters used |
|---|---|---|
| Base folder prefix | C:\Users\AlexSmith\OneDrive - Contoso Ltd\Downloads\ | 52 chars |
| Auto-created ZIP folder | 2026-Q4-Client-Project-Deliverables-Final-Export\ | 49 chars |
| Internal ZIP subfolders + filename | assets\localized\templates\...\quarterly-summary-revised.xlsx | 170+ chars |
Once the total crosses 260 characters, File Explorer stops with Destination Path Too Long or Error 0x80010135: Path too long, often leaving a half-extracted folder behind.
2Fix 1: Extract in a short root folder (no admin rights needed)
This reversible fix works on every Windows 11 PC, including managed work laptops where Registry and Group Policy are locked.
- Create a short folder at the drive rootOpen
C:\(or another local drive) and create a folder namedz(path:C:\z). - Copy the ZIP there and shorten its nameCopy the archive to
C:\zand rename the copy toa.zip. Keep your original archive untouched in Downloads. - Extract directly into C:\zExtract the archive into
C:\z\out. Moving out ofOneDriveorDownloadsimmediately frees 50 to 100 characters of path budget. - Shorten deeply nested folder names before moving files backIf you plan to move the extracted files back into OneDrive or SharePoint, rename overly verbose subfolders first so sync clients and Office apps can open them cleanly.
3Fix 2: Use a long-path-aware extractor or selective extraction
If the internal path inside the ZIP is already close to or over 260 characters—common with JavaScript node_modules trees, build artifacts, or exported web archives—shortening the root folder alone may not be enough for File Explorer.
- Extract with Karuzip or 7-ZipKaruzip bundles 7-Zip 25.01, which uses Windows extended-length path APIs (
\\?\) when writing deep trees to NTFS. Right-click the ZIP and choose Karuzip > Extract to folder intoC:\z\out. - Or extract only the files you actually needOpen the ZIP with View contents in Karuzip, locate the specific PDF, spreadsheet, or folder you want, and extract only those selected items. See how to view and extract selected files.
4Fix 3: Enable Win32 Long Paths (LongPathsEnabled) on Windows 11
Microsoft documents an opt-in system setting for Windows 10 (1607+) and Windows 11 that removes the 260-character MAX_PATH limit for Win32 applications that declare longPathAware in their manifest.
Option A: Registry Editor (Windows 11 Home & Pro)
- Open Registry Editor as administratorPress
Win + R, typeregedit, and approve the User Account Control prompt. - Navigate to the FileSystem keyGo to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. - Set LongPathsEnabled to 1Double-click the DWORD value
LongPathsEnabled, change its Value data from0to1, click OK, and restart Windows 11.
Option B: Group Policy (Windows 11 Pro / Enterprise)
Run gpedit.msc, navigate to Computer Configuration > Administrative Templates > System > Filesystem, set Enable Win32 long paths to Enabled, and restart Windows.
LongPathsEnabled = 1, File Explorer itself and several desktop apps (including Microsoft Excel, which enforces a 218-character path limit for workbooks) may still refuse to open or move files deeper than 260 characters. Keep extracted project folders short whenever possible.5Verification scope and boundaries
The Registry path, Group Policy location, and longPathAware application requirement in this guide are verified against Microsoft Learn's official Maximum Path Length Limitation documentation and Microsoft Support's OneDrive path-length reference. Karuzip 3.0.0 uses bundled 7-Zip 25.01 on 64-bit Windows 11 and Windows 10.
Extracting a deep tree to disk does not guarantee that older downstream software or cloud sync clients will accept paths longer than their own internal limits. If you must share archives with Windows users, avoid nesting long folder names before compressing.
Extract deep ZIP trees or selected files with Karuzip 3.0.0
- Preview contents and extract only needed files
- Bundles 7-Zip 25.01 engine with clean Windows 11 UI
- Free, ad-free, and no app telemetry
Karuzip runs on Windows 10 / 11. Open this page on a Windows PC to download it.
Frequently asked questions
What causes Error 0x80010135 Path too long when extracting a ZIP?
- Answer
Error 0x80010135 (Path too long) appears when the combined character count of the destination folder path plus every subfolder and filename inside the ZIP exceeds the legacy Win32 MAX_PATH limit of 260 characters used by Windows File Explorer.
What is the quickest fix without editing the Windows Registry?
- Answer
Copy the ZIP to a short root directory such as C:\z, shorten the ZIP filename if needed, and extract into C:\z. Moving out of C:\Users\YourName\OneDrive\Downloads immediately reclaims 50 to 100 characters of path budget.
Does enabling LongPathsEnabled fix File Explorer completely?
- Answer
Not for every application. Setting LongPathsEnabled to 1 lifts the 260-character limit for Win32 apps that declare longPathAware in their manifest, after a restart. However, parts of File Explorer and some desktop programs such as Microsoft Excel still enforce shorter path limits.
Can Karuzip extract only the files I need from a deeply nested ZIP?
- Answer
Yes. Open the archive with View contents in Karuzip, select only the specific documents or folders you need, and extract them to a short local directory instead of unpacking an entire deeply nested tree.
Why do OneDrive and SharePoint folders trigger path-too-long ZIP errors so often?
- Answer
Synced OneDrive and SharePoint folders add long organization, site, and library names to the local path prefix. Microsoft also documents a 400-character decoded URL path limit for OneDrive and SharePoint, so extracting deeply nested ZIPs directly inside a synced folder frequently exceeds both File Explorer and sync limits.
Official references
- Microsoft Learn: Maximum Path Length Limitation — Win32 MAX_PATH (260 characters), LongPathsEnabled registry key, and longPathAware manifest requirement (checked November 22, 2026).
- Microsoft Support: File path length limits in OneDrive and SharePoint — cloud sync and File Explorer path-length limits (checked November 22, 2026).
- 7-Zip FAQ — archive extraction and Windows path handling notes (checked November 22, 2026).