Missing July content

Will we see the following KBs published sometime soon?

https://www.catalog.update.microsoft.com/Search.aspx?q=KB5041016
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5041017
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5041081

5041016 and 5041017 are included in yesterday’s release Content Release: Patches for Windows - July 2024 Security Updates

Not sure about 5041081 but will inquire

Hello ,
Even the KB5041081 is also released , please refer

Thank you

1 Like

Thanks, Girish, I was looking at “Patches for Windows”, didn’t think to check the “Updates for Windows Applications” site.

Can someone explain this?


Its because of the “Source ID” column most likely buried waaaaay to the right of what you can see.

Let’s focus on the Name column. Why does the end of the fixlet name not contain the KB I am searching for? Is the name value useless?

I replied to your question about the Name column but misunderstood the question… so changing my answer. :slight_smile: When you search using that search box, all of the columns that are visible are searched. You can hide the Source ID column if you want.

Forget the search capabilities of the console. Why did or why does MS do this cross referencing? If a person only searches on Name column, you will come up empty in this case.

Microsoft has been doing this for some time now…publish one “wrapper” KB article and then reference the individual product updates under another.

Visiting the bulletin page for KB5041016 leads to this page: July 9, 2024-KB5041016 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows Server 2022 - Microsoft Support

which includes this snippet referencing the individual bulletins for each product (3.5 and 4.8 under one, and I think a typo on the second line should probable be 3.5.1 and 4.8.1 )

Hi @jbruns2017, the .NET Framework updates have a parent KB# and child KB# relationship. The parent KB# is (KB5041017) and that is the value we use in the source ID field and the child KB# are (KB5039879 and KB5039886) are referenced in the name of the fixlet and they cover different .NET Framework versions:

KB5039879 - Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10, version 1809 and Windows Server 2019

KB5039886 - Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 1809 and Windows Server 2019

You can also see this relationship and breakdown at the following Microsoft site:
https://support.microsoft.com/kb/5041017
and
https://support.microsoft.com/kb/5041016

Thanks, Gus.

1 Like

Then is it safer to search with REST api calls to examine the Source ID column and not the name?

Thinking along the lines of having a CVE number and trying to get the KB from it.

Yes you can. Or you can use Web Reports where you can create a content report and filter for either CVE and/or KB#. Or you can even create a filter in the console which allows you to search for a specific source id with KB# or CVE as in this example below:
image
or
image

1 Like