When you click on an update that has been superseded in WSUS, you get a warning that says you should verify the update is no longer needed before declining it. According to Microsoft, you're supposed to approve the superseding updates first, wait for computers to take them, verify the old ones are no longer needed by clients, and then you can safely decline the superseded updates. Yeah, umm... that's not very practical, Microsoft.
For years I've just blanket declined superseded updates, but I recently came across an article that says you shouldn't do that.
So my question is this: Why not?
Is there ever a scenario in which a particular update is not applicable to a client but the update it supersedes is? Can anyone give me a compelling reason why blindly declining a superseded update is not a good idea?