Security Update API does not return results for 40+ KBs

[ERG2001]

Hello, I'm working with a project team who is building a security/compliance app that takes details of applicable KBs for (usually Windows Server) systems from WSUS and/or SCCM, and uses that export as input to call Security Update API. In general, this process works, but the team will have a consisten number (about 45) updates that are determined to be applicable, and these updates are not found when calling the Security Update API.

Can the forum moderator help us identify why these particular KBs are not being found? There is bit in of a pattern as 25 of the 50 "missing KBs" look to be related to .NET Framework updates, and there are at least 4 related to servicing stack updates, but remainder, on surface, don't appear to have any specific pattern.

Compared the missing updates to another post from this forum in 2018, and there were no common KBs (from the 2018 post), so curious if someone who directly supports the Security Update API is able to repro independently and then confirm what behavior is expected and whether we have possible fixes or mitigations.

MissingKBsv2.xlsx SecurityUpdateGuideSupersedence.docx

[mdressman]

Thanks for reporting. We will take a look.

[ERG2001]

Thank you!

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

---

From: Matthew Dressman [email protected] Sent: Tuesday, December 17, 2019 10:39:09 PM To: microsoft/MSRC-Microsoft-Security-Updates-API [email protected] Cc: ERG2001 [email protected]; Author [email protected] Subject: Re: [microsoft/MSRC-Microsoft-Security-Updates-API] Security Update API does not return results for 40+ KBs (#48)

Thanks for reporting. We will take a look.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FMSRC-Microsoft-Security-Updates-API%2Fissues%2F48%3Femail_source%3Dnotifications%26email_token%3DAOBFLH5GWRMFZVSJRMYWWR3QZHAQ3A5CNFSM4J4F7IA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHFA4AI%23issuecomment-566889985&data=02%7C01%7C%7C733d5f7262924dec916108d78384fcab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637122479498727877&sdata=QGwNgm5Rv%2FQMOTInstiQZv3N11KmObNWXnS4aiHOdFU%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOBFLH5C7E4VH7SK7QNM4IDQZHAQ3ANCNFSM4J4F7IAQ&data=02%7C01%7C%7C733d5f7262924dec916108d78384fcab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637122479498737882&sdata=KU1Ha3fWHWzgHZXCYC%2B73zALCFPFEf4PcPD9ld%2Bfp10%3D&reserved=0.

[chemamartinez]

Same problem here. Any update on this?

Thanks.