Fix Windows Error 0x80070057 - The Parameter Is Incorrect

You are trying to extract a file and Windows is hitting you with error 0x80070057, telling you the parameter is incorrect. This usually happens because your file path is too long for Windows to handle or the archive itself is corrupted during the download process.

Why this happens

Windows imposes a 260-character limit on file paths, meaning deep folder structures cause extraction failures. If shortening the path doesn't work, the zip file itself likely suffered a data drop during your initial download.

Steps

1. 01
   Create a new folder directly on your C:/ drive with a very short name, like C:/Extract. Try extracting your zip file into this new, short location to see if the error clears.
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 and find the LongPathsEnabled entry in the right-hand panel.
4. 04
   Double-click LongPathsEnabled, change the value from 0 to 1, click OK, and restart your computer to apply the change.
5. 05
   If you still receive the error after those steps, delete the original zip file entirely and re-download it from the source to ensure you have a clean, uncorrupted copy.

Still not working?

If you are still hitting the error on one specific file even after re-downloading, that file may be inherently incompatible with your current Windows user permissions. Try moving the archive to a secondary drive if you have one, or check if the source provider offers an alternative extraction tool like 7-Zip, which often handles complex path structures better than the built-in Windows tool.

Frequently asked questions

Will enabling long paths in the registry break Windows?

No, it is a safe, officially supported setting that simply removes the 260-character path limit imposed by legacy Windows constraints.

Does this error mean my files are lost or damaged?

Usually no, the files are just failing to move because the operating system cannot process the long file path name. Once the path is shortened or the registry is updated, the files should extract normally.

Why does this error only happen with some files and not others?

This is almost always due to the specific naming conventions used by the creator of the zip archive; if they nested folders deeply or used very long file names, they inevitably exceed the default Windows character limit.