sodcalculator

10 Tech How-To

Fix 0x80010135 Zip Extraction Error in Windows 11

Guide 10-49729 · Updated · Step by step

The 0x80010135 error appears when Windows 11 cannot extract a ZIP file, often due to a path that is too long, a corrupted archive, or a lack of permissions. This guide walks you through the most effective fixes, from simple workarounds to deeper system adjustments, so you can get your files out quickly.

What You’ll Need

  • Administrator access to your Windows 11 PC (to change system settings and run commands).
  • The ZIP file that is failing (keep it in its current location for now).
  • A stable internet connection (for optional Windows updates and third-party tools).

Step-by-Step

  1. Try extracting to a different folder. Right-click the ZIP file, choose Extract All…, and in the dialog, change the destination to a simple path like C:\temp (create it if needed). Click Extract. If this works, the problem was the original destination path being too long.
  2. Move the ZIP file to a shorter path. Copy the ZIP to a folder with a short name, such as C:\zip, and try extracting from there. This avoids the Windows MAX_PATH limit (260 characters) that often triggers error 0x80010135.
  3. Run the extraction as an administrator. Right-click the ZIP file, select Show more options (if needed), then click Extract All…. Before clicking Extract, hold Ctrl+Shift and click Extract – this launches the process with elevated privileges. If you prefer, you can right-click the destination folder and choose Properties > Security > Edit to grant your user full control, then try again.
  4. Use the Command Prompt to extract. Open Start, type cmd, right-click Command Prompt and select Run as administrator. Then run:
    tar -xf "C:\path\to\file.zip" -C "C:\destination"
    Replace the paths with your actual ones. The built-in tar command often bypasses the File Explorer extraction bug.
  5. Check for file name or path length issues. If the ZIP contains files with very long names, Windows Explorer can fail. Extract using a third-party tool like 7-Zip or WinRAR (both free) – they handle long paths better. After installing, right-click the ZIP and choose Extract Here or Extract to folder.
  6. Enable long paths in Windows (optional). Open Group Policy Editor (type gpedit.msc in Start). Navigate to Computer Configuration > Administrative Templates > System > Filesystem. Double-click Enable Win32 long paths, set it to Enabled, and restart your PC. (If you have Windows 11 Home, you may need to use the Registry Editor instead: navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, create a DWORD named LongPathsEnabled and set it to 1.)
  7. Run the System File Checker. Open Command Prompt as administrator and run:
    sfc /scannow
    This repairs corrupted system files that could affect extraction. After it finishes, restart and try again.
  8. Update Windows. Go to Settings > Windows Update and click Check for updates. Install any pending updates, especially cumulative ones, then restart and retry.

Common Mistakes

  • Extracting to the same folder as the ZIP. If the ZIP is in a deep path, extracting there inherits the long path problem. Always choose a short destination.
  • Ignoring the destination path length. Even if the ZIP is in a short path, the extracted files may have long names that exceed the limit. Use a tool that supports long paths.
  • Not running as administrator when permissions are the issue. If the destination folder is protected, extraction fails. Try a folder like C:\temp first.
  • Skipping the command-line method. Many users don’t realize tar is built into Windows 11 and works reliably for ZIP files.

Tips

  • Use a dedicated extraction tool. 7-Zip and WinRAR are free, reliable, and handle long paths and corrupted archives better than File Explorer.
  • Check the ZIP file integrity. If the archive is corrupted, try re-downloading it or ask the sender to re-zip it. You can also test with tar -tf file.zip to list contents without extracting.
  • Keep your system updated. Microsoft has fixed several extraction bugs in cumulative updates, so keeping Windows 11 current reduces the chance of this error.

Troubleshooting

If the error persists after trying the steps above:

  • Try a different ZIP file. If other ZIPs extract fine, the problem is specific to that file – it may be corrupted or created with an unsupported compression method.
  • Rename the ZIP file to a shorter name. Sometimes the ZIP’s own name contributes to the path length. Rename it to something like file.zip and try again.
  • Disable third-party antivirus temporarily. Some security software can interfere with file extraction. Pause your antivirus and retry (remember to re-enable it).
  • Check if the destination drive is full. If you’re extracting to a drive with insufficient space, you’ll get errors. Check free space and clean up if needed.
  • Use the Windows Disk Cleanup. Run cleanmgr to free up temporary files, which can sometimes resolve extraction issues.
  • If nothing works, use a live Linux USB. Boot from a Linux USB drive and extract the ZIP there – this bypasses Windows entirely. This is a last resort but almost always works.

Frequently Asked Questions

What exactly causes error 0x80010135?

It’s most often caused by a file path that exceeds Windows’ 260-character limit, but it can also be triggered by corrupted archives, insufficient permissions, or a bug in File Explorer.

Will enabling long paths fix the error permanently?

It can, but not always. If the error is due to a long path, enabling long paths in Group Policy or Registry will resolve it. If it’s due to corruption, you’ll need to repair the archive.

Can I use PowerShell to extract ZIP files instead?

Yes. Open PowerShell as administrator and run: Expand-Archive -Path 'C:\file.zip' -DestinationPath 'C:\destination' -Force. This often works when File Explorer fails.

Why does the error only happen with some ZIP files?

Different ZIP files have different internal structures. Some may contain files with very long names, or they may be compressed using methods that Windows Explorer doesn’t fully support. Third-party tools handle these better.

Is it safe to use third-party extraction tools?

Yes, reputable tools like 7-Zip and WinRAR are safe and widely used. Always download from official websites to avoid malware.

Will I lose data if I force extraction?

No, extraction doesn’t delete the original ZIP file. If extraction fails, your data is still safe in the archive. You can try different methods without risk.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →