Unable to download the latest version of iTunes (11.1) for Windows XP

None of these helped. I have already reviewed this.

Bottomline, the iTunesSetup.exe payload was NOT in the location on the Apple Support download page - not good guys!

I did find an iTunesSetup.exe payload in another local at Apple but I am sure that others are probably running into the same issue as iOS 7 requires and upgrade of iTunes to 11.1.

So Matt M., please note, my questions was related to downloading iTunes - not installing it. So you reply did NOT help and the issue was with Apple's download support site. I suggest you folks fix this.

At the time, I disabled my pop-up blockers and cleared the brower's cache and any temp files. No joy.

I found what I needed at ANOTHER location on Apple's Download Support site. So I have the appropriate iTunesSetup.exe file and it installed fine.

As for the Apple Software Update, I have had periodic problems with this in WinXP so I really do not bother as I find it a waste of time.

If I need to update Apple software fot WinXP, I would prefer to update the packages seperately.

So bottomline, I have resolved my problem with finding and downloading the 11.1 version of iTunes for XP. The location of the payload is NOT obvious and Apple's Download site does not work for me. If it works for you then great.

Apple software may be really good on the Mac (the Mac and UNIX/Linux systems are my prefered platforms) but when it comes to WinXP, not so good.

And then being forced to upgrade to iOS7 (on my iPhone 4) was not a pleasant experience especially given this dependenci on iTune 11.1.

As for Apple Software Update, it never sees my installation of iTunes only Quicktime. As I said, it does not provide me any value.

Frankly, I have wasted too much time and Apple, IMHO, has not been very upfront when it comes to where they have some of their payloads for upgrades.

The only reason I was able to resolve this issue w/ iTunes is that Apple's download site is not quite as secure as they think it is. Bottomline, I found what I needed and fixed it but again, far too much time was wasted on something so simple.

Sorry, we do this type of thing professionally and its not something that we share unless it is w/ the organization itself. And then sometimes they listen (like w/ Google a couple times last week) and then many times they do not (like w/ LinkedIn's situation a couple of weeks ago). Apple in the past has not bothered to listen so we do not bother to let them know any more.

As for me, I was just trying to get this silly issue resolved w/o having to resort to other methods.

Thanks. I have a couple of developer accounts - one for work and one personal.

Communications consists to at least two parties to a dialogue. It is not a one way. So far, w/ Apple we have no reason to believe that any feedback previously provide was viewed so we do not bother any more as there appears to be no value.

We also do not publish the vulnerabilities but rather learn what these organizations do or do not do.

Here in the US, my group applies the "3 strikes and you're out philosophy" when it comes to notifying folks of vulnerabilities. No feedback after three notifications. No further information. And no we are not making any money on this.

We do however, document it for ourselves and then occassionally it makes it way into reports that make it to CERT. If CERT chooses to release the data, that is up to them.