Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While trying to script deployment of .msu's I realized that certain KB articles had multiple releases. One example of this is KB2524426.

KB2524426 was released May 2011 and re-released June 2011. There are similar other re-releases KB2536276.

Since the KB article is part of the file name I used this thinking that each contained a unique update (.msu). Now that I know this is not the case, I'm trying to figure out if taking the most recent KB release will suffice when creating/deploying an update package.

share|improve this question
up vote 2 down vote accepted

The re-release corrects issues that appear once the patch is released. I would say its only cumulative if it says so in the technotes released to describe the patch.

share|improve this answer
Makes sense. Since the subsequent releases are meant to improve or correct the first release, can you think of any case in which using just the most recent release would not be enough? – Randolph Nov 2 '11 at 3:13
It depends on what the re-release fixes. You would want to read the technote of the re-release to see why they're re-releasing the patch and whether or not it applies to your environment. – Mitch Nov 2 '11 at 12:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.