Hello,
all of a sudden this cumulative updates for win10 version 21h2 is showing not relevant to my computers. is there anybody else having this issue ? we have recently upgraded the Bigfix version however i do have other clients which are win 1809 and 1607 and the cumulative patches has no problem of showing relevant. so seems like problem is only with the win10 version 21h2 cumulative updates.
please help
Hello @TheMete, this content only supports Windows 10 Enterprise LTSC 2021. On your Win10 21H2 endpoint, what is the results of the following QNA:
Q: operating system
A: Win10 10.0.19044.5487 (21H2)
Q: values "EditionID" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" of native registry
A: EnterpriseS
Q: values "ProductName" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" of native registry
A: Windows 10 Enterprise LTSC 2021
Thanks, Gus.
Just to be clear on what Gus is saying, this is a Microsoft limitation, not a BigFix one. From the MS KB article for this update at February 11, 2025—KB5051974 (OS Builds 19044.5487 and 19045.5487) - Microsoft Support :
Hello All,
SO this is not teh first time i am patching with this cumulative update. Our OS and version is correct . However , i did realize in BF relevancies for this patching is showing this below .
I did compare relevancies of the patch from MS24 NOV: Cumulative update for the Feb and seems like relevancies are same too. so it makes no sense why FEB patch is not applicable. Becasue i was able to successfully install the last year NOV and dec .
Moreover,
When i remove this follwing relevancy and create a task(by copying the fixlet) correct computers coming up as relevant .
exists value “EditionID” whose (it as string as lowercase is “EnterpriseS” as lowercase) of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion” of native registry
SO i wonder even though this EnterpriseS reg exist in under wow64 , maybe BF is not able to find it and like wow64 redirection issue ?
I hope i am making sense.
Thank you all
That’s very strange; the EditionID of “EnterpriseS” definitely belongs under the native path, not the wow6432node path. Do you have a different value under the native path, or is EditionID missing from the native path entirely?
In either case of the value is missing or incorrect that implies some corruption or misconfiguration or your image. If the value is present but wrong, is it possible someone performed an “upgrade” to a non-LTSC version?
Can you post a screenshot of what “winver” reports?
here is the winver:
also here is the reg.
seems like relevancy for edition iD used says " contains enterprise" vs now says it exists the exact string like :is Enterprises" see below
New one
MS25-FEB
exists value “EditionID” whose (it as string as lowercase is “EnterpriseS” as lowercase) of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion” of native registry
MS24-JUN
exists value “EditionID” whose (it as string as lowercase contains “enterprise” or it as string as lowercase contains “education” or it as string as lowercase contains “serverrdsh”) of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion” of native registry
Even the string described is different . it used to be " contacins enterprise" now is" EnterpriseS"
Thank you, this is all very helpful.
I find it strange that your wow6432Node path (the 32-bit path) reflects “EnterpriseS” while the name 64-bit path reflects “IoTEnterpriseS”.
Those are two different operating sytems - “EnterpriseS” refers to Windows 10 LTSC, while the “IoTEnterpriseS” refers to “Windows 10 IoT LTSC”.
It’s not clear to me whether the patch is supposed to apply to the IoT distribution or now (IoT is basically what we used to call Windows Embedded, usually for special-purpose devices like ATMs, Points-of-Sale, or Kiosks).
As far as MS24-Jun, I’d need to see the specific fixlet or KB article to which this refers. It could well be that there were MS24-Jun updates that applied to both LTSC and non-LTSC, which would explain the differences in Relevance.
Yep, the KB article I linked above (as well as the screenshot I embedded) indicate that this should apply to Windows 10 IoT LTSC. Will refer our Patch Content team here.
Ok I see this is already reported internally and a fix is in progress. Thank you for bringing this to our attention, I apologize that it took so long to sort the details on this and thanks for your patience.
The current content did indeed incorrectly leave off Windows 10 IoT LTSC.
so will they be fixing the relevancy issue ? and release it again?
Yes they will
Additional forum padding
Hi @TheMete, this issue has been corrected in Patches for Windows site version 4494. The fixlets are now inspecting for either condition of EditionID = EnterpriseS or EditionID = IoTEnterpriseS.
Thanks, Gus.
