Detection mismatch for KB5021037

I see a mismatch in the detection logic between fixlet 502103701 and 502103703 which causes a false positive when the CU has been applied.

502103701 looks for exists value "CurrentVersion" whose ((it >= "12.3.6024.0" and it < "12.3.6174.8")

502103703 look for exists value "CurrentVersion" whose ((it >= "12.0.6024.0" and it < "12.3.6444.4")

The wrong minor version number causes a false positive. This seem to have changed recently though I haven’t seen any modification annoucments.

3 Likes

bump!
we have same problem :slight_smile:

1 Like

Looking at the relevance at bit more and I think the issue is the registry key hives have been reversed.

If you look at the the 2 fixlets for KB5021045, fixlet 502104503 for 32-bit SQL is looking at x32 registry and fixlet 502104503 for 64-bit SQL is looking at x64 registry.

Now compare that with the 2 fixlets for KB5021037, fixlet 502103703 for 32-bit SQL is looking in the x64 registry and fixlet 502103701 for 64-bit SQL is looking in the x32 registry. :confounded:

I have opened case CS0387747 with HCL support

2 Likes

:star_struck:

2 Likes