this is a valid rant. anyone in this thread try this on top of adding office 2010 or 2013 before running updates?? you're looking at about 2.2gb of updates. even on decent i5 machines being pushed from a local WSUS it takes 2-3 reboots and about 2 hours. I had better luck with qchain and ordering the updates myself with win2k and XP. I don't get how they can't seem to order them correctly to not cause failures every time.
As others have said, i .net updates seem to be the worst as far as time consuming. office updates..... i really question rather they're updating anything or flat out deploying whole sections of the damn program... /s
All we want are at least roll up packs that we can integrate into install media when it's needed.
And, unless i misunderstood, service packs rarely bring new features unless it's something very critical they're deeming a feature to make you think you're getting something neat for free. NT4sp3 was common when i got into NT and networing and i don't recall a service pack ever including something that wasn't fairly critical for security patching.