You open a ZIP file and one item refuses to come out. The message says “CRC Failed” or “Data Error.” The container’s header is intact, but that one file’s data is corrupted or was altered mid-copy. This is the most common ZIP fault, and it is not the same as a container that will not open at all. A CRC error usually hits only one or two pieces. The rest can nearly always be saved. Here is what the check does, why a mistyped password can trigger it, and how to get the files that still pass.
What the CRC-32 Check Does
How the Integrity Test Works
Every file inside a ZIP carries a CRC-32 checksum in its local header and again in the central directory. CRC-32 is a 32-bit fingerprint. Extraction software recomputes it over the decompressed data and compares the result with the stored value. A match means the file is intact. A mismatch triggers an error for that specific item.
This per-file check is what separates a CRC fault from an “unexpected end of archive” error. The latter means the container itself is truncated or its central directory is missing. A CRC error means the structure is readable, but the decompressed bytes of one file do not match what the record says they should be. Causes include a bad download, a failing drive, or a copy that was interrupted mid-write.
Why You See “CRC Failed” in 7-Zip and “bad CRC” in Unzip
Same Fault, Different Wording
Different tools use different language for the same problem. 7-Zip reports a mismatch as CRC Failed for the affected file. Info-ZIP unzip reports it as bad CRC followed by the computed and expected values. WinRAR reports Checksum error and states that the file is corrupt. All three describe the same underlying issue: the decompressed data did not match the stored checksum.
The computed and expected values that unzip shows are not useful for manual repair. They are just two 32-bit numbers. What matters is that the tool names the failed file. That file is the one you need to replace or accept as damaged. The other items in the same container normally extract fine, because each file is checked independently.
Wrong Password Can Cause a CRC Error
If the container is encrypted, a CRC error can have a different cause. With legacy ZipCrypto encryption, a wrong password can slip past the quick password check and fail only at the CRC stage. A message like CRC Failed in encrypted file. Wrong password? or Data Error in encrypted file. Wrong password? does not always mean the file is damaged. It may simply mean you typed the wrong password.
Before you assume data corruption, retype the password carefully. Check for a leading space, a wrong keyboard layout, or a misspelled word. If you have a second guess, test that too. When the correct password is used and the error persists, the encrypted file’s compressed data is genuinely damaged.
Test the Archive Without Extracting
Run a Dry-Run Test First
You do not need to extract everything to find out which files are bad. Both 7-Zip and Info-ZIP unzip can test every entry without writing anything to disk. Use 7z t archive.zip or unzip -t archive.zip from a command line. The test reads each compressed entry, decompresses it in memory, recomputes the CRC-32, and compares it with the stored value. It then lists which entries failed.
This is faster than extracting and does not create partial files. It also tells you exactly which items are good, so you can extract only those. If a ZIP has ten files and only the third one fails, the test will show that the other nine passed. Extract the nine good files normally and deal with the one bad file separately.
Save the Entries That Still Pass
Extract Everything Except the Broken File
Because a CRC error usually affects only the items whose compressed data is damaged, you can recover the rest of the container. Extract everything except the broken file. If your tool stops at the first error, pull out the good files one by one or use a command that skips errors.
Keep a Partial File When You Must
For files that tolerate some damage, such as text, video, or JPEG, keep the partly extracted file. 7-Zip and WinRAR can retain a partly extracted file after a CRC error. WinRAR’s option is called Keep broken files. Enabling that option writes whatever data was decompressed before the error, which may be enough for a media player or a text editor to open it. The result will be incomplete. It is often better than nothing.
Practical Steps to Recover What You Can
- Copy the original ZIP to a new folder so you do not modify the original while testing.
- Run 7z t archive.zip or unzip -t archive.zip to list which entries fail.
- Note the names of the failed entries. If the container is encrypted, re-enter the password and test again.
- Extract the good entries normally. If your tool stops, extract each good entry individually.
- For a damaged entry that is text, video, or JPEG, enable the option to keep broken files (WinRAR’s Keep broken files or 7-Zip’s equivalent) and try to open the partial result.
- If you cannot recover the damaged entry, look for another copy of that specific file elsewhere, such as a backup or the original source.
Do not overwrite the original container until you have recovered everything you need. If you make a mistake, start over with the untouched copy.
When a CRC Error is Not the End
A CRC error is frustrating. It is rarely the end of the container. In most cases, only one or two items are affected, and the rest extract normally. The per-file CRC-32 check is there to tell you exactly which file is bad, so you can focus your recovery effort on that one item.
If the damaged entry is essential and you have no backup, try a dedicated repair tool. Online services such as zip.repair can sometimes rebuild the container’s structure or extract the undamaged entries for you. They do not fix the damaged data itself, but they can help you get the good files out of a partially broken ZIP.