Windows machine only showing superseded patches

Usage and Config Patch
1

Hi Folks,

I have a Windows 10 machine that is only showing superseded patches as relevant.

It has

MS19-SEP: Servicing Stack Update for Windows 10 Version 1809 - Windows 10 Version 1809 - KB4512577 (x64) (Superseded)
MS19-JUL: Servicing Stack Update for Windows 10 Version 1809 - Windows 10 Version 1809 - KB4512937 (x64) (Superseded)
MS19-JUL: Servicing Stack Update for Windows Server 2019 - Windows Server 2019 - KB4512937 (x64) (Superseded)
MS19-JUL: Servicing Stack Update for Windows 10 Version 1809 - Windows 10 Version 1809 - KB4509095 (x64) (Superseded)
MS19-JUN: Servicing Stack Update for Windows 10 Version 1809 - Windows 10 Version 1809 - KB4504369 (x64) (Superseded)

when I look at the patches that follow, i.e MS19-OCT (KB4521862) it’s not marked as relevant.
The endpoint is reporting in correctly and has been rebooted in the last two weeks,
I can’t see anything that is wrong.

Anyone have any advice?

Thanks

1 Like
2

I manually applied the updates that were superseded which surprisingly ‘worked’ with the exception of MS19-JUL: Servicing Stack Update for Windows Server 2019 - Windows Server 2019 - KB4512937 (x64) (Superseded). Interesting to note reporting Server 2019 when all systems are Win10 and there is a Win10 equivalent.

3

When patches are Superseded, a relevance clause is added that will make the tickets non-relevant by default. This is to prevent clients from spending resources evaluating the superseded content (since there are a lot of superseded patches), but has a side-effect of making them appear “Remediated” to Web Reports, even if the patch was never installed.

Copies of the fixlets that are in Baselines do not get updated, unless you re-synchronize the baseline, so you may use your Baseline relevant components to see how far out-of-date your computers are; or apply a Client Setting to continue evaluating superseded content (which will make the client evaluation loop take much longer).