Had a little discovery today when we realised possibly the fastest replacement of a KB Article ever, (almost instantly!).

 It appears that the following behaviour is experienced when you perform a manual installation of MS12-034 for Silverlight:

  • The critical update KB2636927 updates and patches all Silverlight 5 instances to 5.1.10411.0
  • The critical update KB2690729 updates and patches all Silverlight 4 instances to 4.1.10329

However, in WSUS, one observes this:

  • The critical update KB2636927 updates and patches all Silverlight instances as 1 entity (All versions) to 5.1.10411.0
  • The critical update KB2690729 is not available in WSUS.
  • On the MS12-034 security bulletin page, you will read that KB2690729 in MS12-034 is replaced by KB2636927.

 

This then means that any systems with Silverlight managed by WSUS would ultimately still need KB2636927, as it gets evaluated as still needing that since the 'older' KB2636927 has already been replaced. That might then suggest why there is only 1 'version' of Silverlight in SUP/WSUS. Therefore, do not be too alarmed if all systems with Silverlight 4 or below are upgraded to 5 after the application of May's security bundle via Configmgr!

Anonymous