#2025 There are data after the end of archive Archives with Warnings:

[oakleyx]

Hello,

We just upgraded to version 16.04 and now when we unzip some files we are getting "There are data after the end of archive Archives with Warnings:"

The zip files are unzipping correctly. Should we be worried about the extra bytes appened to the file?

Our IT team is really concerned about this warning message.

Do you know what causes the extra bytes and should we be concerned?

Thanks
-Dan

[Igor Pavlov]

You can extract it in parser mode:

7z x a.zip -t#

Then look extra data in hex editor.
And try to find information about software that was used to create these archives. Probably there was some bug in that software, that was already fixed, but someone still can use old versions with bugs.

Also there is some probability that there is bug in 7-Zip. In that case I want to see more details about these archives.

[Courtel]

Hi, I've the same issue. This happen when I use the option «Extract to (FolderName)» and the archive is digitaly signed (CAB files from Wsus). If I open the archive with 7-Zip and then drag and drop the file to extract it, I don't have this message.

[Igor Pavlov]

Probably there are some unused bytes in nested archives.
It's difficult to fix it for all possible cases with embedded resources.
After "Open" you can see same error message, if you press "Info" button.

You can post the link to file.
Or attach it here, if it's small.

[Courtel]

Effectively the same message appears when I go to "Info". I have attached a file that show the error when unzipped.

[Igor Pavlov]

So there is cab and 2392 bytes after cab - maybe it's signatutre.
But 7-zip doesn't know about such signatures.
and probably there is no information in cab file about that additional signature.

What program did create that cab?
Describe all steps.

Maybe there is some another container file that contains that cab?
If so, please upload that container file.

[AmigoJack]

Couldn't this warning also tell how many bytes are left? That would help a lot: if it's only 10 bytes I don't care, but 500 KiB will make me want to inspect it.
If you do that: couldn't you also include the first 20 additional bytes in hexadecimal writing? It would help even more to see if those are all \x00 or just random linebreaks (\x0a and/or \x0d).