tar.gz file, but that makes no difference in this case). tar (possibly itself compressed into something like a. However, I imagine those work primarily on a per-compressed-file basis, and from the looks of it, that archive should contain two files: a.

There is a remote possibility that you might be able to use the test/repair functionality of a packer (such as WinRAR, WinZip, 7Zip, or something else I don't really know off the top of my head what's available these days) to repair the archive. That should be on the order of a few hundred bytes to a kilobyte you are six orders of magnitude off in terms of file size compared to what the catalog indicates for contents of the archive. md5 file appears rather odd, there is no reasonable way a correct archive which contains a single file with no data in it can balloon to over a gigabyte. That is indicated by the only file listed by WinRAR being reported as having a size of 0 bytes, whereas the archive itself is over a gigabyte in size.Īside from the fact that a 0 byte size for a. Specifically, the catalog (which lists the contents of the zip file, and is stored at the end of the file) seems to be corrupted.

Unexpected end of archive winrar fix