none
What is the difference between KB2267602 and KB915597. Both are labeled as "Definition 1.141.3676.0"

    Question

  • What is the difference between KB2267602 and KB915597.  Both are labeled as "Definition 1.141.3676.0"?  They both show up in my WSUS server but only the KB915597 ever seems to be needed by any of my clients.

    Thanks

    Tuesday, January 22, 2013 12:33 PM

Answers

  • One of the great mysteries of life...

    As you might surmise from the numbers, 915597 is much older than 2267602. Also, there is no KB article for 2267602, but there is for 915597. As you note, the 915597 is the one that installs. This is also the case in my environment. v1.143.502.0, which arrived today, is the currently detecting package. (v1.143.533.0, which has a later build number, is not detecting on anything.)

    My educated guess is that somebody screwed up, tagged the 2267602 number somehow (by accident, or by ignorance), and now some automated process somewhere just bugs off and builds the package whenever. But what doesn't make sense is that more builds are distributed in the 2267602 update than in the 915597 update, which begs the question: Are we not getting some Definition Updates that we should be? And, why is the detection logic different? (read: What's 'broken' in the 2267602 package that's causing it to be N/A on all systems -- and is anybody actually doing any QA on these packages?)

    Looking at today's releases:

    1.143.533.0 2267602(Y) 915597(N)
    1.143.502.0 2267602(Y) 915597(Y)
    1.143.466.0 2267602(Y) 915597(N)
    1.143.421.0 2267602(Y) 915597(N)
    1.143.408.0 2267602(Y) 915597(N)
    1.143.401.0 2267602(Y) 915597(N)
    1.141.3362.0 2267602(N) 915597(Y)

    and before that the last release for 915597 was Jan 18.

    And where is that v1.141 coming from anyway???


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Wednesday, January 23, 2013 12:31 AM
    Moderator

All replies

  • One of the great mysteries of life...

    As you might surmise from the numbers, 915597 is much older than 2267602. Also, there is no KB article for 2267602, but there is for 915597. As you note, the 915597 is the one that installs. This is also the case in my environment. v1.143.502.0, which arrived today, is the currently detecting package. (v1.143.533.0, which has a later build number, is not detecting on anything.)

    My educated guess is that somebody screwed up, tagged the 2267602 number somehow (by accident, or by ignorance), and now some automated process somewhere just bugs off and builds the package whenever. But what doesn't make sense is that more builds are distributed in the 2267602 update than in the 915597 update, which begs the question: Are we not getting some Definition Updates that we should be? And, why is the detection logic different? (read: What's 'broken' in the 2267602 package that's causing it to be N/A on all systems -- and is anybody actually doing any QA on these packages?)

    Looking at today's releases:

    1.143.533.0 2267602(Y) 915597(N)
    1.143.502.0 2267602(Y) 915597(Y)
    1.143.466.0 2267602(Y) 915597(N)
    1.143.421.0 2267602(Y) 915597(N)
    1.143.408.0 2267602(Y) 915597(N)
    1.143.401.0 2267602(Y) 915597(N)
    1.141.3362.0 2267602(N) 915597(Y)

    and before that the last release for 915597 was Jan 18.

    And where is that v1.141 coming from anyway???


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Wednesday, January 23, 2013 12:31 AM
    Moderator
  • I believe 2267602 is the Defender update for Windows 8, whereas the other one is for XP through 7.

    I don't have Windows 8 nor any plans to have it in the near future. They screwed with just too many things at once and it's hard to drop it into my domain with other computers. So it would be great to find a way to keep 915597 on auto approval and not have to automatically download 2267602.

    Not really a question, just a comment.

    • Proposed as answer by Dave Harry Thursday, July 11, 2013 1:22 AM
    Thursday, July 11, 2013 1:18 AM
  • I believe 2267602 is the Defender update for Windows 8, whereas the other one is for XP through 7.

    This is correct, and was confirmed by Ben Herila in another thread about a month ago.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, July 11, 2013 4:59 PM
    Moderator