/build/static/layout/Breadcrumb_cap_w.png

KBOX(K1000) Superseds Windows 10 Critical Security patches for 1809, 1803, 1709 r

KBOX(K1000) Superseds Windows 10 Critical Security patches for 1809, 1803, 1709. It never used to happen before.
Did anyone experience it?


wf9WChK6yx6rwAAAABJRU5ErkJggg==


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Channeler 4 years ago
Red Belt
2

Yes it happens.

Superseded means there is a newer patch that already patches what that patch was intended to fix.


Microsoft and other vendors release new patches every week, there's a high chance this new patches already includes patches that you have in your catalog. Making them superseded.

Doesn't matter if your build is say 1903(latest), there are already superseded patches for 1903:

For example, take a look at this one:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4507453

wdvLXLnPA3JzgAAAABJRU5ErkJggg==

The vendor (in this case MS), decides what patches are superseded and when, not KACE.





Comments:
  • I clearly get that, what I meant, yes any 2019-07 and older should be superseded. Check the released date of each patch 1709, 1803, 1809 all been released on same date last month but it should not flag as superseded... - haseebiqbal 4 years ago
    • So...

      Let's go over some of those highlighted ones you posted:

      1- KB4512516
      Released On: 08-9-19

      Was Superseded by: KB4512494
      Released On: 8-16-19

      Source:
      https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=5909e402-b1ec-4dc4-8648-d73a81a115aa


      2- KB4512507
      Released On: 08-10-19

      Was Superseded by: KB4512474
      Released On: 8-17-19

      Source:
      https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=a50734e7-f388-46dd-b697-513537829ae3


      3- KB4511553
      Released On: 08-9-19

      Was Superseded by: KB4512534
      Released On: 8-17-19

      Source:
      https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=c33e7db5-e128-4ca0-aa51-fcd3fd32bcb2


      So I'm not seeing any discrepancies between Microsoft (the vendor) and KACE, those patches are already superseded.
      (Yes they lasted less than an ice-cream, but that's Microsoft's call).

      The date is different because KACE needs to wait for testing before the Patched is published in the Catalog.


      See:
      --How soon after release will patches be available via the K1000 appliance?--
      https://support.quest.com/kace-systems-management-appliance/kb/136902/ - Channeler 4 years ago
      • Yah, found the issue.
        Microsoft https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=ea0ef4a1-eb20-4318-984b-10b9e4f6dd3b

        classified it as "Updates"

        Where https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=c33e7db5-e128-4ca0-aa51-fcd3fd32bcb2

        Classified as "Security Updates".

        Because I set KBOX to subscribe Type:Security Impact Critical and Superseded:No, it didn't download the corrected update. - haseebiqbal 4 years ago
  • Current solution is Manually selecting each patch and download those. As Microsoft messed up their August updates :-) - haseebiqbal 4 years ago
    • you could also modify that Smart Label... or modify the Subscription Criteria.

      Or manually, for now, and let's what happens for September... - Channeler 4 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ