For fun, in my lab (everyone should have a lab, right?) I enabled the Microsoft Server operation system-23H2 one to see what came down when I sync'd. What I got in the lab was (for example)
2024-06 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5039236)
2024-04 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft Server operating system, version 23H2 for x64 (KB5036617)
and older superseded versions of similar
I assume it will be similar updates for 21H2, 22H2, and 24H2
if you look at this link... https://support.microsoft.com/en-us/topic/windows-server-version-23h2-update-history-68c851ff-825a-4dbc-857b-51c5aa0ab248 it implies that "23h2" is for Server OS Builds of 26398. Easy enough (I assume) to check if you have that build with 'select build01 from v_r_system group by build01', and see if you have any of those.
Slightly OT:
I have this as a custom report on my reporting site, and every 2-3 months (I should run it every hotfix Tuesday, but I forget), I run it to see if "anything new and fun showed up I should care about that I should enable".
Select
lc.CategoryInstanceName,
lc.CategoryInstanceID,
ci.DateLastModified,
uci.IsSubscribed,
lc.LocaleID
from v_LocalizedCategories lc
join CI_CategoryInstances ci WITH (NOLOCK) on ci.CategoryInstanceID=lc.CategoryInstanceID
join v_UpdateCategoryInstances uci on uci.CategoryInstanceID=lc.CategoryInstanceID
where
ci.CategoryTypeName = 'Product'
and lc.localeID in (9,1033) --Note, these just happen to be the ones this environment needs, pick more or all if you need them all
order by ci.DateLastModified desc
Caveats: it sorts by 'datelatemodified', so If you enable a product, it'll then be at the top of the list. the "False" ones will either be datelastmodified of 'when it magically appeared at all', or 'when a human changed it from checked on to checked off'.