iTunes 5 download is corrupt with 1.0.6 on OS X and XP




14 years ago
11 years ago


(Reporter: mgw, Unassigned)


Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

If I download the above URL, I get a corrupted file on both Mac OS X and Windows
XP SP2 when using Firefox 1.0.6.

Specifically, the corruption is zeros from bytes 0x1f0ade9 to 0x1fofde8 --
exactly 20480 bytes.

This seems to be the cause of great amount of complaints from users trying to
download the new iTunes version. See:

It works fine using IE on Windows or Safari on the Mac.

Reproducible: Always

Steps to Reproduce:
1. Dowload the above URL (obtained from
2. Launch the resulting binary on Windows XP

Actual Results:  
You get a "some files are corrupt" message from the installer

Expected Results:  
Launched and run the iTunes installer.

Comment 1

14 years ago
That byte range should be:

0x1f0ade9 to 0x1f0fde8

of course.

also, I just tried Firefox 1.0.2 on Mac OS and the download resulted in the
correct file.

Comment 2

14 years ago
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050909
Firefox/1.4 ID:2005090906

Changing OS to ALL.


14 years ago
OS: Windows XP → All

Comment 3

14 years ago

It turns out that the IE/Safari versions have the same checksum as each other (different from the FF 1.0.6 
version, and no zero corruption), but they still end up with the "some files are corrupted" error from the 

So, this should just be considered a "download results in different binaries" bug instead...

Comment 4

14 years ago
yes, apple has annonced that there was an issue on there side.

please try again.

Comment 5

14 years ago
Apple takes the blame for this one...  Resolving INVALID.
Last Resolved: 14 years ago
Resolution: --- → INVALID


11 years ago
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.