When open the archive (attached) that is created by the built-in "Compressed to.." context menu feature in Windows 11, 7-zip said "not implemented" and failed to update the filename.
7-Zip doesn't implement renaming for such files, because descriptor is complicated about additional optional headers after the end of data. We don't know what size of these additional optional headers, and we don't want to corrupt the archive during renaming.
Please create another zip archive with non-empty file (non-zero size). And try to rename that file.
What exact version of Windows 11 do you use?
Does it always create zip file with Host OS = Unix and Descriptor in Characteristics?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Shouldn't Windows write FAT instead of UNIX?! *nix permissions in Windows are screwed, literally - very often all files have executable permission and stuff like that, posing potential problems, or at least annoyance to *nix users of there archives.
Windows in not Unix and should not impostor it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
that file uses descriptor in file headers.
7-Zip doesn't implement renaming for such files, because
descriptor
is complicated about additional optional headers after the end of data. We don't know what size of these additional optional headers, and we don't want to corrupt the archive during renaming.Please create another zip archive with non-empty file (non-zero size). And try to rename that file.
What exact version of Windows 11 do you use?
Does it always create zip file with
Host OS = Unix
andDescriptor
inCharacteristics
?Even non-empty file would cause the same issue:
And yes, it looks like it always has "Host OS = Unix and Descriptor in Characteristics".
I use: Windows 11 Version 24H2 (OS Build 26100.2894)
Windows 10 has context menu option
Send to / Compressed (zipped) folder
And that command creates usual zip with
Host OS: FAT
items.Is there
Send to / Compressed (zipped) folder
option in Windows 11?Just tried that -- yes it also produces the problematic files just as "compress to". Win10's is fine as you noted.
Probably Windows 11 now use
libarchive
code.libarchive
archive writes Unix type:3
- is unix type.and
libarchive
probably always write descriptor, because they don't want to move back in written output stream to set crc field in header:Does anybody know when Windows had switched to libarchive for zip archive creation feature?
Last edit: Igor Pavlov 2025-01-23
Search does.
Since May 2023:
You can ask them on their gh.
Shouldn't Windows write FAT instead of UNIX?! *nix permissions in Windows are screwed, literally - very often all files have executable permission and stuff like that, posing potential problems, or at least annoyance to *nix users of there archives.
Windows in not Unix and should not impostor it.
Now I suppose it's possible to implement renaming feature for such zip files with descriptor.
So I'll look that feature for implementing in future.
Is that accordant with zip specification?