Comment Re:CORRECTION (Score 4, Informative) 246
If the summary is correct I don't really see how this affects servers all that much... The summary says it is an issue in the first 15-60 minutes after startup. Servers are generally up for longer periods of time so the actual impact would be low for W2K03.
It's about time they fixed this. I intermittently run a Virtual Machine version of XP. A few months ago, I noticed windows update service (running under svchost) would chew up 99% of the cpu when booted up for 10 minutes. Seems the problem was windows updates check for the presence of every single IE update ever released, when they were all superseded by the latest IE cumulative updates anyway and not per-requisites for anything else. I'm not sure why they are patting themselves on the back, when they just did the equivalent of declining superceded updates in WSUS (generally done in seconds, btw).