>>I just went back there again today and got 1 critical update and it was SP1 for XP. SP1 for IE6 was no where to be found!?!?!
>
>Probably because they decided not to put out on the Web?
>
>I do this all the time. I put up a new build. If there's something wrong with it, I certainly don't want to leave it on the Web Site, especially if software automatically senses it and uses it.
>
>I think there was a serious security flaw with the patch in question.

Well that's far more reasonable than the alternative I was worried about - that both had been rolled together into one.

Now a security flaw in such an important patch (it was, after all, on the "critical" list, as opposed to the VFP patch of a few days back) says something about MS' success at indoctrinating its developers with increased security awareness. Given my understanding of the (endless) procedures in place to get "core" products updated in the first place, and my assumption that MS' recent security review/indoctrinations only would have added to that load, it seems remarkable that a flaw would survive that yet get spotted so fast afterwards.

Anyway, thanks Mike.