I replied to your question about the Name column but misunderstood the question… so changing my answer. 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.
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
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: