How to Fix Windows ZIP Extraction Errors

Windows ZIP extraction errors come down to a small number of causes, and the wording of the error tells you which one you are dealing with before you change a single setting. A truncated download, an archive that Windows blocked for safety, a destination path that is too long, a drive with no room left, and a genuinely damaged file each throw a different message. This guide starts from the exact error text on your screen, works out the cause behind it, and gives you the fix that matches, including the archive tools that already ship with Windows 10 and 11.

What each ZIP error message means

Windows and 7-Zip both speak plainly when an archive refuses to open, and the wording points at the cause. Match what you saw against the table below before changing anything.

If the same archive fails the same way on two different computers, the archive is the problem. If it fails on one machine only, the fault sits on that machine.

The download stopped before the archive finished

This is the cause I meet most often. A browser writes what it receives and renames the file once the transfer completes, so a transfer that dies halfway leaves a .zip with a correct name and a truncated body. Windows then reports corruption or an empty folder because the file was never a valid archive.

1. Open the download page and note the file size printed next to the link.
2. Right click the .zip in Downloads, choose Properties, and read the size on the General tab. A smaller number than the page shows means the transfer was cut short.
3. Delete the broken file and download it again. If a browser download manager or extension handled the transfer, disable it for this file and let the browser download it natively, or use a client that verifies the final size.
4. If the site publishes a checksum, compare it. Run certutil -hashfile C:\Users\YourName\Downloads\archive.zip SHA256 in Command Prompt and match the output with the value on the page.

A truncated download on a shaky connection is often a one-off, and the second attempt succeeds. On a link that drops regularly, a resumable client picks up where it stopped.

Windows blocked the file before you opened it

Files that arrive over the internet carry an alternate data stream called Zone.Identifier, and Windows marks them as coming from another computer. The blocked archive then fails in a confusing way, sometimes with Windows cannot find the path and sometimes with nothing more than a refusal to open.

1. Right click the .zip and choose Properties. At the bottom of the General tab there is a checkbox labelled Unblock with a note about the file coming from another computer. Tick it, choose Apply, and extract as normal.
2. Or open PowerShell in the folder holding the archive and run Unblock-File -Path .\archive.zip. That clears the zone mark without touching the file contents.
3. Working with a folder of downloads? Right click the folder, choose Properties, and tick Unblock there.

The destination path is too long for Windows

Many Windows file operations still stop at the 260 character limit, and the built-in extractor is one of them. A deeply nested folder plus a long archive name plus long file names inside it crosses that line easily, and Explorer reports Windows cannot find the path or Invalid argument even though the folder is plainly there.

1. Extract to a short path such as C:\Temp instead of a Desktop folder or a deep project directory. Create it first with mkdir C:\Temp.
2. Use an extractor that handles long paths. 7-Zip reads and writes well past 260 characters without help.
3. Windows can accept longer paths through the LongPathsEnabled policy, but the extractor has to support it too.

The drive does not have enough free space

Compression ratios mean the extracted copy is usually bigger than the archive, and text and media files can expand several times over. Windows checks the free space on the destination volume and refuses with There is not enough space on the drive to extract this file when the result will not fit.

• Check free space on the drive you are extracting to, not the drive that holds the archive. Extracting to a second volume solves it outright.
• Leave headroom above the uncompressed size, because Windows needs room for temporary files during the operation.
• List the contents with 7z l archive.zip to see the uncompressed size of every entry first.

If the space you are hunting for is on your system drive, how to find large files taking up disk space covers the hidden files that eat the most room.

Your security software removed the contents

Microsoft Defender and other antivirus scanners inspect what is inside an archive, not just the .zip file itself. When Defender detects something, it quarantines the payload or blocks the extraction, and the files appear to be missing even though the archive opens without complaint on another machine.

1. Open Windows Security > Virus and threat protection > Protection history and look for entries naming the archive or the file inside it.
2. Read the detection name before restoring anything. Restoring a detection puts the file straight back where your scanner will find it again.
3. If it was a false positive on a file you trust, add an exclusion for that folder under Manage settings > Exclusions in Windows Security, then restore the item.

Do not switch Defender off to make extraction work. A blocked archive is a security decision, and the answer is to read the detection.

Nested archives and locked files

Two situations look like corruption but are not. Some downloads arrive as a zip inside a zip, where the outer archive holds one large .zip and nothing else, so extracting it gives you a single file. Separately, a program that previews archives or a cloud sync client can hold an open handle and make extraction fail with The file is in use.

1. Open the outer archive and extract the inner one as well. Check the contents in 7-Zip before you conclude that a file is empty.
2. Close Explorer windows previewing the archive, pause OneDrive or Google Drive sync for the folder, and wait for an active antivirus scan to finish.
3. Extracted batches often arrive with unhelpful names such as image (1). How to batch rename files in Windows tidies that up in a few steps.

Extract it with a different tool

Three extractors ship with Windows, and each one fails in a different place. When Explorer refuses an archive, one of the alternatives usually gets the files out.

• 7-Zip is the most forgiving. It reports which entry failed, extracts the entries that pass its checksum, and handles long paths. Right click the archive and choose 7-Zip > Extract to.
• tar ships with Windows 10 version 1803 and Windows 11. Open Command Prompt in the archive folder and run tar -xf archive.zip -C C:\Extracted, creating that folder first.
• Expand-Archive is the PowerShell cmdlet. Run Expand-Archive -Path .\archive.zip -DestinationPath C:\Extracted. It throws a clear error on a damaged archive.

When every archive fails with a CRC error

A CRC error means the bytes of an entry do not match the checksum recorded in the archive. For one file that is a strong signal about that download. When every archive on the machine fails the same way, the file is not the common factor, so the tool or the drive is the suspect.

1. Test a known good archive. Compress a folder in Explorer to a ZIP file, then extract it. If that fails, the problem is on this machine.
2. Extract the same archive on a second computer. If it works there, the fault is in the software or the drive on the first machine.
3. Try a second archiver. If 7-Zip reports checksum failures and tar extracts the same file cleanly, trust tar and treat the 7-Zip installation as damaged.
4. Check the drive holding the archive. Read errors from a failing disk look like corruption, and how to check SSD and HDD health in Windows shows how to read the SMART data.

In my experience, a CRC error on a single archive is a bad download, and a CRC error on every archive is a driver, a filter, or a dying disk. If the archive lives on a removable drive that has started misbehaving, work through how to fix a USB drive that is not showing up before you blame the file.

Frequently asked questions

Why does Windows say the compressed (zipped) folder is empty?

The file on disk holds no usable archive data. The download was cut short and left a zero byte or partial file, the browser wrote a placeholder before the transfer started, or the archive genuinely contains no items. Compare the size on the download page with the size shown in File Explorer, then download the file again.

Why does 7-Zip show a CRC error when Windows extracts the same file?

Windows Explorer is lenient. When it meets a damaged entry it usually skips it and extracts the rest in silence. 7-Zip checks the checksum of every entry and reports each mismatch, so it surfaces damage that Explorer hides. Use 7-Zip to find which files are damaged, then re-download the archive and compare the results.

Can I extract a zip on Windows 11 without installing extra software?

Yes. Windows 10 version 1803 and Windows 11 include bsdtar, which reads zip files. Run tar -xf archive.zip -C C:\Extracted from a Command Prompt or PowerShell window in the folder holding the archive, or use the Expand-Archive cmdlet in PowerShell. Both tools are already on the machine.

Is it safe to force extraction from a corrupted archive?

Usually, with care. 7-Zip extracts the entries that pass its checksum and reports the ones that do not, so a partial extraction is normal on a damaged archive. Do not run an executable that came out of a damaged archive, and do not treat recovered files as trustworthy until a scan passes. A fresh download is the safer route.

What to remember

• Read the error text first. Each message narrows the cause to a download, a block, a path, or the drive.
• Compare the downloaded file size with the size on the download page before you open anything.
• Unblock the file from Properties when Windows refuses to open it.
• Extract to a short path such as C:\Temp when you hit a path error or an invalid argument message.
• A CRC error on one archive means a bad download. A CRC error on every archive means the tool or the drive.

Open the archive with 7-Zip and run its test command first. It tells you within seconds whether the file is damaged, and that answer decides whether you download the archive again or repair the machine.