October Servicing Stack Server 2019 version issues? (and Win10)

[SmokyMTN]

Why are these updates:

00-33341: MS19-OCT: Servicing Stack Update for Windows Server 2016 - Windows Server 2016 - KB4521858 (x64)
00-33342: MS19-OCT: Servicing Stack Update for Windows Server 2016 (1803) - Windows Server 2016 - KB4521861 (x64)

Showing up as relevant for Windows Server 2019?

Even after I installed the Servicing update FOR Windows server 2019.
MS19-OCT: Servicing Stack Update for Windows Server 2019 - Windows Server 2019 - KB4521862 (x64)

I tried to install them just to see what it would do after the 2019 Servicing Stack completed, and it failed. Thankfully, and now not relevant. BUT, it should never show up as relevant to begin with.

Looks like the Windows 10 Servicing Stacks are doing the same thing. All versions showing relevant… 1607, 1703, 1709, 1803, 1809 all relevant to the same version of Windows 10, in this case we’re at 1809 here. But all the versions report relevant.

Thanks,
Chris

[KapaaIan]

I see this too. It looks like the detection relevance is set too broadly. For the 1809 one, it is looking for:

not exists names whose (following text of last “.” of it as version >= “793” as version) of values of key “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version” of native registry

While the 1703 is looking for:
not exists names whose (following text of last “.” of it as version >= “2104” as version) of values of key “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version” of native registry

And 1709:
not exists names whose (following text of last “.” of it as version >= “1444” as version) of values of key “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version” of native registry

We only have those three versions in our environment, but basically since it’s only looking at the last chunk, its not including the actual major build number and thus it’s all over the place.

[KapaaIan]

Yup, and in the same place that relevance exists, the previous month had something like this (cut off after one chunk but it goes on for a longgggg time).

if (exists key "ApplicabilityEvaluationCache\Package_for_KB4512577~31bf3856ad364e35~amd64~~17763.733.1.0" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" of native registry) then ((set of (7;112) contains item 0 of it AND set of (4294967264;4294967232;0;2;4;32;64;101) contains item 1 of it) of (value "ApplicabilityState" of it as string as integer, value "CurrentState" of it as string as integer) of key "ApplicabilityEvaluationCache\Package_for_KB4512577~31bf3856ad364e35~amd64~~17763.733.1.0" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" of native registry) else ((exists keys ("Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-CoreNEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseNEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseSEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseSNEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-EnterpriseSNEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ProfessionalNEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ServerDatacenterACorEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ServerDatacenterCorEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ServerDatacenterEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-ServerDatacenterEvalCorEdition~31bf3856ad364e35~amd64~~10.0.17763.1";"Microsoft-Windows-)

[yipingliu]

We’ve identified this issue in our content and have proceeded to resolve it. We’ll let you know when the update has been pushed and which version it’s available in.

[bma]

Please see comments in: Content Release: Patches for Windows - October 2019 Security Updates