MS Antimalware Platform 4.18.2001.6 only on one PC

v2009.7 is now on MS Catalog.

Just got 4.18.2010.4 via Windows Update.

Crizal said:

Just got 4.18.2010.4 via Windows Update.

With that version you cannot see the list of exclusions created. It has a bug.

Now I got version 4.18.2010.7

looks that has been came from WU on friday the 6th.

Version 4.18.2010.7 via Windows Update.

It's also already available via MS Catalog.

I have a VM (Win 10 Pro 20H2) that consistently gets new versions of Windows Defender long before any of my other PC's get it and I have no idea why. It's not on any beta program or Windows Inside program.

This morning it was updated to Windows Defender 4.18.2011.5-0.

MrMoerby said:

I have a VM (Win 10 Pro 20H2) that consistently gets new versions of Windows Defender long before any of my other PC's get it and I have no idea why. It's not on any beta program or Windows Inside program.

This morning it was updated to Windows Defender 4.18.2011.5-0.

There's been discussion earlier in this thread starting here:

MS Antimalware Platform 4.18.2001.6 only on one PC

...about the 'how and why' of those getting advance Defender Platform updates. Some users will, for reasons that remain unclear, have some variation of Registry Keys here:

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\MpEngine
    MpCampGradualRelease    REG_DWORD    0x1
    MpCampRing      REG_DWORD    0x3
    MpEngineRing    REG_DWORD    0x3

Other's by ADDING the keys will then magically get these pre-release versions.

Farvatten said:

Some users will, for reasons that remain unclear, have some variation of Registry Keys here:

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\MpEngine
    MpCampGradualRelease    REG_DWORD    0x1
    MpCampRing      REG_DWORD    0x3
    MpEngineRing    REG_DWORD    0x3

Thank you!!! Finally, the mystery may be revealed. This has been bugging me for eons and no amount of Googling revealed any answers. My Googling Kung Fu obviously sucks.

I checked the VM that updates earlier than the others and this is what I see:

Code:

PS C:\WINDOWS\system32> Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Defender\MpEngine"

MpCampGradualRelease   : 1
MpCampRing             : 3
MpEngineRing           : 3
MpGradualEngineRelease : 1

The PC that gets updated later comes back with nothing, so no registry keys.