The applicability relevance for Fixlet ID=512892802, MS26-OCT: Cumulative Update for .NET Framework 3.5 and 4.8 for Microsoft server operating system version 21H2 - Windows Server 2022 - .NET Framework 3.5/4.8 - KB5127687 (x64) AKA KB5128928, is very confusing. I have 8 servers running .NET Framework 4.8.1 that are applicable to this patch. It is creating reporting challenges. Anyone else seeing this?
I do have a few, but it’s not the norm. Of the servers still not patched yet, I have 479 and 6 with the issue. These 6 I don’t have access too, so it’s possible I suppose they had a .NET Framework upgrade..
Interesting find….
I couldn't leave it alone and found the source of the issue.
Relevance 5 has not been updated to detect current versions of .NET Framework 4.8.1.
The important part of the relevance is this snippet:
... whose (it = 533320 or it = 533325) ...
According to .NET Framework & Windows OS versions - .NET Framework | Microsoft Learn, 4.8.1 releases are 533320, 533325, and 533509. Some of my Server 2022 machines have this latest release of .NET Framework 4.8.1, and they are applicable to this Fixlet (incorrectly).
Hi @itsmpro92 can you provide the following QNA output? I would have expected 533509 to be associated with 533509 (Windows 11 September 2025 Release)as stated in the Microsoft documentation you linked.
(names of it, it) of values of keys of keys "Full" of keys "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4" of native registry
Thanks, Gus.