2 Replies Latest reply on Feb 10, 2014 11:24 AM by bkao

    MS update -- uniquely identify by Guid and Revision

    bkao

      Q1. In order to uniquely identify a MS update for all catalogues, do we rely on BOTH the Guid and Revision?

      I am asking in the context of WUA API, IUpdateIdentity  and IUpdateSearcher. UpdateID and RevisionNumber

       

      http://msdn.microsoft.com/en-us/library/windows/desktop/aa386482(v=vs.85).aspx

       

      IUpdateSearcher::Search method (Windows)

       

       

      Q2. If answer to Q1 is positive, then its is true that for a certain KB, the Guid will remains constant over time when Microsoft publishes newer revision (10x, 20x..) available to the public? 

       

      Q3. With the same chain of thought, for a Microsoft box that has a Guid with revision 202 installed, and for the same Guid that has 203 becomes available, would windows update able to install revision 203?

       

      Thanks in advance.

        • Re: MS update -- uniquely identify by Guid and Revision
          Lawrence Garvin
          Q1. In order to uniquely identify a MS update for all catalogues, do we rely on BOTH the Guid and Revision?

          Yes.

          Q2. If answer to Q1 is positive, then its is true that for a certain KB, the Guid will remains constant over time when Microsoft publishes newer revision (10x, 20x..) available to the public?

          It is true for a specific update package that the UpdateID (which is a GUID) is static. This statement is not true for a given KB article, because a single KB article may (in fact almost always does) have multiple update packages, depending on which platforms or applications are affected by the update.

           

          Q3. With the same chain of thought, for a Microsoft box that has a Guid with revision 202 installed, and for the same Guid that has 203 becomes available, would windows update able to install revision 203?

           

          The WUA will install the newest revision that is approved. A revision does NOT cause an update to be RE-installed. A revision is merely a change to the metadata or detection logic in an update package. A revision does NOT include a change to the installer file. Ergo, if an update is already installed, regardless of which revision, the fact that a new revision is available is irrelevant -- the *update* has already been installed.


          A change in the installer file for an update requires a new update package with a new UpdateID.