Zip Files Won't Extract On Windows? Fix - 0x80070057

You are trying to extract a zip file, but Windows stops you with error 0x80070057, claiming the parameter is incorrect. This usually happens because the file structure inside your zip is too deep, hitting the 260-character limit Windows enforces on file paths.

Why this happens

Windows imposes a 260-character limit on file paths, which causes extraction errors when folders are nested too deeply or file names are too long. Alternatively, the zip file itself may have been corrupted during your initial download.

What you'll need

You will need administrative access to your computer to modify the registry and the ability to download fresh files if the archive is corrupted.

Steps

1. 01
   Create a new folder directly on your C: drive with a very short name, such as C:/Temp, and try extracting your zip contents into that location to bypass character limits.
2. 02
   If the error persists, press the Windows key + R, type regedit and hit Enter to open the Registry Editor.
3. 03
   Navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/FileSystem using the folders in the left-hand sidebar.
4. 04
   In the right-hand panel, find LongPathsEnabled, double-click it, change the Value data from 0 to 1, and click OK.
5. 05
   Restart your computer to apply the registry change, then attempt to extract your files again.
6. 06
   If the extraction still fails on a single specific file, delete the zip file and download it again from the source, as the archive itself is likely corrupted.

Still not working?

If you are still hitting the error on one specific file after these steps, check the file name for special characters that might be unsupported by the file system. If the problem persists across different zip files, check your drive for errors using a disk repair tool or ensure your user profile has full read/write permissions for the destination folder.

Frequently asked questions

Does error 0x80070057 mean my files are lost?

Usually, no. It generally means Windows is having trouble writing the file because the path is too long or the download is incomplete.

Is it safe to change LongPathsEnabled in the registry?

Yes, this is an officially supported Windows setting that simply removes the 260-character legacy limit.