To do this:ġ)Open the General tab in Internet OptionsĢ)Click Delete in the Browsing history sectionģ)Check or uncheck options make sure Temporary Internet Files is checked You should delete your Temporary Internet Files. To do the latter (with Internet Explorer closed):Ģ)Change the Control Panel view if it is in the Category viewĥ)Scroll down to and uncheck the box next to Use HTTP 1.1 Options would include downloading this file using a different browser, such as Firefox or configuring Internet Explorer so that gzip encoding is disabled.
FIND CORRUPTED FILES ON WINDOWS 10 ZIP FILE
In eitherĬase, gzip encoding, a Unix compression method, is applied to the Zip file and, for whatever reason, Internet Explorer may then have a problem correctly downloading it. Another possibility would be that the server is set to always gzip files being downloaded. If this Zip file download has not been set with the correct mime-type specification (octet-stream) to denote that it is a binary file this issue may occur. Also, downloading with Internet Explorer may be one of the factors in the issue. It may be caused by settings on the server where the file is stored. However, the issue may not be with the original Zip file. which browsre you are trying to download the file? Normally, the best thing to do would be to delete Temporary Internet Files and download the file again.
FIND CORRUPTED FILES ON WINDOWS 10 UPDATE
Update to add #1: Added browser/operating systems information and MIME type for the two extensions.įirst, make sure that the files you are trying to download, are supported MIME-Types in IIS. I've confirmed that the MIME type for XLSX file isĪpplication/ and is inherited from the root configurationĪny thoughts on what could be causing this or to troubleshoot it? I've confirmed that the MIME type for ZIP files isĪpplication/x-zip-compressed and is inherited from the root configuration I've confirmed that the download is corrupted across multiple browsers (Chrome and Internet Explorer) and multiple operating systems (Windows 7 and Windows 10). I've confirmed it's not response compression gone horribly wrong. I've confirmed it's not our HTTP monitoring module, mangling the download. I've confirmed it's not storage of the files. I've confirmed it's not the upload process The original file, on the file share, is 5,521 bytes. You can see where the data is changing starting with the second line. Left is the file share, the right is the local, downloaded copy. Here's a screen capture comparing the binary data of two zip files.
When a user downloads a file, we're seeing some files get corrupted, XLXS and ZIP files example, though TXT files seem down load just fine. We have a network share we're using for file storage that is accessed through a virtual directory for download.