I updated XP a few months ago and 60 or 70 sounds about right... but it was worse than you describe:<br><br>Windows (and Microsoft's update site too!) did not know the ORDER that those updates must be done in! And it does matter. When Apple Software Update shows ONLY those updates you are now ready for, and then afterward shows news ones (if any), that's a privilege we should not take for granted.<br><br>Windows Update offered a ton of updates, about HALF of which could not actually be completed because others were needed first. Reboot and retry. A few more made it this time. Repeat. Repeat. MORE than three times. And it didn't just check an update and then fail--it would actually download the whole update, THEN spend time trying it, and eventually fail... and then discard the update so the system had to re-download it to try (and probably fail) the next time.
<br><br>But the icing on the cake: the failures were for a very simple reason--the system was not YET ready for them--but Microsoft displayed no intelligible message to that effect! I got obscure, technical sounding, and non-specific error messages instead. Along with a suggestion to see the help site for more info--but naturally, no actual LINK to the help page! So I manually TYPED the help address shown in the error dialog, got to the help site, and had to now search manually for the terms in the error. The multiple help page(s) for the error said LESS--that's right, less--than the original error message.<br><br>And not one hint in the errors or the help docs suggested this might be a normal expected part of EVERY large Windows update, caused by updates being attempted (by Windows itself and not in your control) out of order. People see these errors thousands of times a day, yet Microsoft has never phrased them clearly, nor even documented their clear and explanable cause. Not anyplace I could find--and I wasted a LOT of time looking.<br><br>And nowhere in the errors or the help did it say what to DO about the errors. The answer is simple and they could have told me instead of letting me flounder: just keep rebooting and retrying. But nothing told me that. I figured it out eventually.<br><br>Naturally I wanted the update done RIGHT, not just completed after a ton of errors and wondering what state my system was in and what the future might hold. But I had no indication of whether this procedure was "OK" or not. (I guess it was--it's what Windows users expect and accept?)<br><br>I could not believe it.<br><br>nagr[color:red]o</font color=red>mme
<br><br>I require stroyent!
<br>TeamMacOSX.com | MacClan.net