Microsoft Security Advisory 2862973 should be marked as superseded

Microsoft Security Advisory 2862973 should be marked as superseded

according to Microsoft Update Catalog
:Security Update for Windows Server 2008 R2 x64 Edition (KB3123479)

They said KB3123479 replaced KB2862973,I also testing by Golden Image with downloading from Internet source which
actually does not need the KB2862973 , it just requires KB3123479.

Question is should KB2862973 be marked as superseded or not ?
Since this patch still mark as applicable for computers which already install KB3123479.

Thanks you in advance

Hi teerapongpa,

Yes, you are right about the supersedence part. KB3123479 has superseded KB2862973 for Windows 7 and later versions.

Thanks for reporting this. We will update the content accordingly soon.

Best Regards,
Sylvia

@sylvia Can you please add the below to BigFix patch,

https://technet.microsoft.com/en-us/library/security/4025685.aspx

I don’t see it in the console as of now.

Thanks in Advance.

Hi techadmin,

4025685 is not a number which refers to a particular KB or patch. It’s actually a guidance as mentioned in Microsoft webpage - Guidance related to June 2017 security update release.

If you look up this number as a KB number - Microsoft Security Advisory 4025685: Guidance related to June 2016 security update release: June 13, 2017 - Microsoft Support, the details about this guidance can be found.

To look up the corresponding Bigfix content, please refer to the KB numbers listed in each of the guidance page.

For example, in the guidance-for-older-platforms page, under older platforms table 2 of 3 (

), CVE/Patches released for older platforms (such as, winXP or windows server 2003) are listed with KB numbers as reference. To look up the content, use the specific KB listed for each platforms, eg, 4024323 for windows XP SP3.

Let us know if you have any other concerns!

Best Regards,
Sylvia

1 Like

@sylvia Thanks for the information. But further drilling down, I’m not able to find the below in console, which is part of the MS Advisory guidance.

https://technet.microsoft.com/en-us/library/security/MS09-050.aspx

Please advice.