Troubleshooting
RAR CRC Error: What It Means and What to Do
A CRC error means the extracted data doesn't match the checksum stored for it when the archive was created — the bytes changed somewhere between compression and extraction.
A cyclic redundancy check (CRC) is a small numeric fingerprint calculated from a file's contents and stored alongside it in the archive. When you extract, the extractor recalculates the fingerprint from what it decompressed and compares it to the stored value. If they don't match, something changed the data, and the extractor reports a CRC error instead of silently handing you altered content.
Single file vs. whole archive
- One file fails, others extract fine: only that file's data was damaged, likely during the original compression or a partial disk error. The rest of the archive is intact.
- Every file fails, or the archive won't open at all: the damage is in shared structures (headers, the file table) rather than one file's data, which usually points to a download or transfer problem affecting the whole file.
Steps to take, in order
- 1Re-download or re-copy the fileThis resolves most CRC errors, since transfer corruption is the most common cause.
- 2Try WinRAR's repair toolRight-click the archive, or use Tools → Repair Archive inside WinRAR. This works best on archives created with a recovery record and can sometimes rebuild damaged headers even without one.
- 3Extract with 'Keep broken files' checkedThis pulls out everything that does pass its checksum, letting you recover the undamaged files even if some fail.
- 4Try a different extractorOccasionally a stricter or looser CRC implementation in another tool (see 7-Zip vs WinRAR) will extract data the original tool rejects, though this doesn't fix genuinely corrupted bytes.
Frequently asked questions
Does a CRC error mean I have a virus?
No. It's a data-integrity signal, not a security scan. It just means the bytes don't match what was recorded when the archive was made.
Can I ignore a CRC error and use the file anyway?
You can extract with 'Keep broken files', but the affected file will likely be unusable or display incorrectly since some of its data is wrong.
Why does repair work sometimes but not always?
Repair can rebuild structural information (headers, file tables) especially with a recovery record present, but it cannot recreate file content that was never captured or was overwritten.
Is a CRC error the same as 'unexpected end of archive'?
No — see [unexpected end of archive](/guides/rar-unexpected-end-of-archive) for that distinct error, which means data is missing rather than mismatched.
Related guides
- Archive Troubleshooting: Fix RAR and ZIP ErrorsMost archive problems fall into a handful of categories. Find your symptom below and jump straight to the fix.
- How to Fix a Corrupted RAR ArchiveA corrupted RAR archive can sometimes be repaired, and sometimes can't. Here's how to test one, what recovery tools actually do, and when re-downloading is the real fix.
- How RAR Recovery Records WorkA recovery record is optional redundant data added to a RAR archive when it's created, so that if the archive later becomes damaged, WinRAR can use that redundancy to repair it. It's the main defense against a [corrupted RAR file](/corrupted-rar-file).
- Unexpected End of Archive: Cause and Fix"Unexpected end of archive" means the extractor reached the end of the file it has before it reached the end the archive's own header says should exist. Almost always this is a file that is simply shorter than it should be.
- RAR Extraction Error Messages, Explained and FixedExtraction errors usually name the exact problem, once you know how to read them. Find your message below.
WinRAR is a trademark of its respective owner. RareExplorer is an independent resource and is not affiliated with or endorsed by RARLAB or win.rar GmbH. Read our editorial policy to see how this page was researched.