Windows Extraction Tool Issues

Hi,
I recently encountered a zip folder, which contains 6 PNG images.
When extracting the files, by right-clicking the zip folder and using the Windows Extraction Tool.
The file are not present, and the extracted folder is empty/void of content.
However, when I use 7zip or some other file extraction tool.
The files are clearly there, within the zip folder and are easily extracted.
This is the file info as seen in 7zip.


Would anyone know what might be going on here?
Below is the zip folder in question.

It does the same exact for me. Windows built in zip does not show the files nor extract them. 7zip works, they show up in the archive and extract properly.

No clue why that is happening

Access Denied said:

It does the same exact for me. Windows built in zip does not show the files nor extract them. 7zip works, they show up in the archive and extract properly.

No clue why that is happening

@Access Denied

Thanks for giving it a go.
At least I now know, that it's not specific to my machine.

@Geosammy No problem. I figured at least if I couldn't provide a fix, I could help by confirming it was not specific to your PC. :)

Access Denied said:

It does the same exact for me. Windows built in zip does not show the files nor extract them. 7zip works, they show up in the archive and extract properly.

Well, it's not the file names that are the problem. Once extracted with 7-zip you can send the folder and the files it contains to a 'Compressed (zipped) folder' and that one behaves perfectly.

@Geosammy, 7-Zip shows that the host OS for the original (non-working) zip file is Unix. That's where the problem must have come from, an incompatible 'zip' utility created it.

Edit: it IS the filenames. They contain the > character which is legal in Unix but not in Windows. 7-Zip replaces the > with an underscore _ but windows just says you can't use that name and skips extracting the file.

Bree said:

Well, it's not the file names that are the problem. Once extracted with 7-zip you can send the folder and the files it contains to a 'Compressed (zipped) folder' and that one behaves perfectly.

@Geosammy, 7-Zip shows that the host OS for the original (non-working) zip file is Unix. That's where the problem must have come from, an incompatible 'zip' utility created it.

Edit: it IS the filenames. They contain the > character which is legal in Unix but not in Windows. 7-Zip replaces the > with an underscore _ but windows just says you can't use that name and skips extracting the file.

@Bree

So what your saying is, that zip folder created using Unix as it's Host,
will go unrecognized by Windows?
How does someone using Unix, create zip folder that Windows will recognize?

Geosammy said:

So what your saying is, that zip folder created using Unix as it's Host,
will go unrecognized by Windows?

Yes, Windows cannot have the > character in a file name. You can see this by creating a text file on your PC and trying to type the > character.

If you make a zip file using Unix, the file names have to be compatible with Windows.

Geosammy said:

How does someone using Unix, create zip folder that Windows will recognize?

They must use filenames that are windows-compatible for Windows own built-in 'un-zip' to work. 7-Zip will replace any illegal characters with the underscore, so you can still extract the files, just not with their Unix names. In Windows you can't use...

The following reserved characters:

• 
  
  • < (less than)
  • > (greater than)
  • : (colon)
  • " (double quote)
  • / (forward slash)
  • \ (backslash)
  • | (vertical bar or pipe)
  • ? (question mark)
  • * (asterisk)

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

Access Denied said:

Yes, Windows cannot have the > character in a file name. You can see this by creating a text file on your PC and trying to type the > character. If you make a zip file using Unix, the file names have to be compatible with Windows.

Bree said:

They must use filenames that are windows-compatible for Windows own built-in 'un-zip' to work. 7-Zip will replace any illegal characters with the underscore, so you can still extract the files, just not with their Unix names. In Windows you can't use...

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

@Access Denied
@Bree

Thanks you guys.

@Geosammy You are very welcome :)