New
#81
And yet there remains this mystery why some users get these registry entries while others do not.
Originally I held the theory that by doing custom Defender scans, or by repeated requests for definition updates it was viewed by Microsoft as 'Seeker' behavior, similar to what happens when you manually hit the 'Check for updates' button in Settings > Windows Update and will get CU updates ahead of schedule.
I do clean installs with each major release, and during 1904 and 1909 cycles, both my machines at some point got these per-release platform Registry entries.
Thinking I could track when it happened in 2004, I set up a Registry tracking routine to check for when it changed thinking I could pin down the event or process. Disappointingly throughout the entire 6 month life span of 2004, and with all my same Defender 'Seeker' behaviors there was never a change to this Registry Key.
Now on 20H2 still nothing, but I'll continue looking for the change.