Windows Defender x64 definition update 1.14.1923.4

[Guest]

URL:
http://download.microsoft.com/downl...4c5d-84be-a64fe41cc87a/WindowsDefenderX64.msi
Size: 7400960 bytes
MD5: 1be4fe1565bb1ba40d2d36e8332fa191
Windows Defender Version: 1.1.1593.0
Engine Version: 1.1.1603.0
Definition Version: 1.0.0.0

URL:
http://www.download.windowsupdate.c..._f9b52193a4333f0ee6a6ad8737d8c3c099831b91.exe
Size: 3658568 bytes
MD5: e6bbc179519a76f0b227bcd7937367ce
Windows Defender Version: 1.1.1593.0
Engine Version: 1.1.1804.0
Definition Version: 1.14.1841.7

URL:
http://www.download.windowsupdate.c..._b5b7b9d07425fdc9b57654a268c24b7b4a9b5f81.exe
Size: 800408 bytes
MD5: b50fa747513d41a185c439479a6dec41
Windows Defender Version: 1.1.1593.0
Engine Version: 1.1.1804.0
Definition Version: 1.14.1923.4

 

[Bill Sanderson MVP]

Thanks.

However, I don't want to foster a misapprehension here: Your first URL is
for the 64 bit version of Windows Defender. So far so good--readers need to
remember that it is the version of the OS you are running which determines
whether you need this version--Windows XP Professional x64 Edition or
Windows Vista x64 run only on 64-bit processors. However, the majority of
users of machines with these processors are running the standard 32-bit
Windows XP Professional.

Beyond that basic issue, the definition updates that you mention are the
same definitions that go with the 32-bit versions of Windows Defender--i.e.
they are not "64 bit" definitions.

This does beg the question of whether there are specific 64 bit versions of
malware--and I believe that the answer to that is "yes"--and don't have a
picture of how this is handled by the antimalware teams at Microsoft--except
that I am certain they are aware of the issue and that's part of the reason
for specific x64 versions of antimalware products.