An "unexpected end of archive" error means the extractor reached the end of the file before the archive data was finished. In almost every case the file is incomplete: the download was interrupted, the copy was cut short, or it is one part of a multi-part set and the next part is missing. The fix is to get a complete copy, or to put every part of the set in the same folder. Your computer and your extraction software are rarely at fault.
Below is how to confirm which of these you are dealing with, how to fix each one, and what you can salvage if a complete copy is not available.
What the error actually means
Every archive format has a structure: headers that describe each file, the compressed data, and, in ZIP files, a table of contents at the very end. The extractor reads through that structure in order. When it expects more data and finds the end of the file instead, it stops and reports an unexpected end.
You may see slightly different wording depending on the program and format:
- Unexpected end of archive
- Unexpected end of data
- The archive is either in unknown format or damaged
- You need to start extraction from a previous volume
- Cannot find volume or Missing volume
- The compressed (zipped) folder is invalid (File Explorer's version for ZIPs)
They all point to the same few causes.
Cause 1: The download is incomplete
This is the cause in the large majority of cases. Browsers sometimes mark a download as finished even when the connection dropped, especially with large files, flaky Wi-Fi or a VPN that reconnects.
How to check:
- Right-click the archive and choose Properties.
- Look at Size (not Size on disk).
- Compare it with the size given on the download page, in the email or by the person who sent it.
If yours is smaller, it is incomplete. Some download pages also publish a checksum such as SHA-256. You can calculate your file's checksum in PowerShell with Get-FileHash .\filename.zip and compare the two. If they differ, the file is not the same as the original.
Fix: delete the partial file and download it again. Use a wired connection or a stable network if you can, avoid pausing and resuming, and let the browser finish before you open the file.
Cause 2: A part of a multi-part set is missing
Large archives are often split into numbered volumes, such as file.part1.rar, file.part2.rar or backup.7z.001, backup.7z.002. Each part on its own ends "unexpectedly", because the data continues in the next part.
How to check: look in the folder for the rest of the set. Check that the numbers run in sequence without a gap, that every part has the same base name, and that all parts except the last are the same size.
Fix:
- Download or copy every part into the same folder.
- Do not rename any parts. The extractor finds them by name.
- Extract from the first part only, not the last one you downloaded.
- If one part is smaller than the others and is not the last, download that part again.
Our guide to extracting multi-part RAR files explains the different naming schemes.
Cause 3: The copy or transfer was cut short
An archive copied to a USB stick that was removed too early, saved to a drive that ran out of space, or transferred by FTP in text mode instead of binary mode can all end up truncated or altered. Email systems can also mangle attachments that are close to the size limit.
Fix: go back to the original copy. If you still have it, test it. If the original is fine, copy it again, use Safely Remove Hardware before unplugging USB drives, and make sure the destination has enough space.
Cause 4: The archive was never finished
If the program that created the archive crashed, was closed or ran out of disk space part-way through, the archive is incomplete from the start. This happens with backups that run overnight and with archives created on a nearly full drive.
Fix: recreate the archive from the original files. If you are the one making archives, test each one after creating it. Our guide on how to check if a ZIP file is corrupted shows how.
How to confirm the cause with an integrity test
An archive program can test an archive without extracting it. The test reads every file, checks it against the checksum stored in the archive, and reports exactly where things go wrong. In Universal Zip, open the archive and run the integrity test. Then read the result:
| Test result | What it means | What to do |
|---|---|---|
| Unexpected end after most files pass | File is cut short | Get a complete copy |
| Asks for the next volume | A part is missing | Add the missing part to the folder |
| CRC errors in the middle, end reached normally | Data damaged, not truncated | Re-download; extract healthy files |
| Not an archive or unknown format | Wrong file or wrong extension | Check what the file really is |
| All files pass | Archive is fine | Try extracting with a current program |
Salvaging files from an incomplete archive
If you cannot get a complete copy, you may still be able to rescue part of the contents. How much depends on the format:
- RAR and TAR-based archives store each file's details just before its data, so an extractor can usually recover every file that comes before the cut-off point.
- ZIP files keep their table of contents at the end, which is the part that goes missing. File Explorer gives up entirely, but an archive program may still find and extract the files stored early in the archive.
- Solid 7Z and RAR archives compress files as one continuous stream, so damage or a missing end can affect more files than in a non-solid archive.
Open the archive in an archive program, see what it lists, and extract whatever it can to a new folder. Check every recovered file before you rely on it. Anything after the cut-off point is simply not in the file and cannot be recovered from it.
When it happens with every archive
If every archive you download or copy gives this error, look beyond the files:
- Security software that scans downloads can occasionally interrupt them. Check its history for blocked or quarantined items.
- A failing drive or USB stick can corrupt files on write. Copy the archive to a different drive and test it there.
- An old extractor may misread newer formats, such as RAR5, and report confusing errors. Use a current archive program.
For ZIP files that File Explorer rejects outright, see compressed zipped folder is invalid, which covers the Windows-specific causes. Once you have a good copy, Universal Zip extracts it from the right-click menu like any other archive.
Frequently asked questions
What does unexpected end of archive mean?
The extractor reached the end of the file before the archive data was complete, usually because the download or copy was cut short.
Can I recover files from an incomplete archive?
Sometimes files stored early in the archive can be extracted, but anything after the cut-off point is missing. Getting a complete copy is the real fix.
Does this error mean my computer is broken?
Rarely. It is almost always the archive file. If it happens with every archive from one drive, test that drive for faults.
