Extra bytes written when set to zip64 #417

Open
opened 2026-01-29 22:11:36 +00:00 by claunia · 0 comments
Owner

Originally created by @brecollog on GitHub (Oct 13, 2020).

I have seen various flavors of this issue, some event claim this issue is fixed but I have downloaded the most recent version of sharpcompress and the issue is still there. When writing out a large file, i.e. >2GB, and using the zip64 flag set to true, extra bytes get written in the header that cause issues when decompression. Very repeatable. Create a single file entry > 2GB and add it to the archive and save. If you have 7zip you can right click on the archive and select 'test archive' and you will get the error.

Does anyone have a fix as to how to combat this issue? My apologies if I have missed how this has been addressed.

Originally created by @brecollog on GitHub (Oct 13, 2020). I have seen various flavors of this issue, some event claim this issue is fixed but I have downloaded the most recent version of sharpcompress and the issue is still there. When writing out a large file, i.e. >2GB, and using the zip64 flag set to true, extra bytes get written in the header that cause issues when decompression. Very repeatable. Create a single file entry > 2GB and add it to the archive and save. If you have 7zip you can right click on the archive and select 'test archive' and you will get the error. Does anyone have a fix as to how to combat this issue? My apologies if I have missed how this has been addressed.
claunia added the bugup for grabs labels 2026-01-29 22:11:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#417