Windows 10: Defender antimalware client update

In Windows 10 version 1709, os build 16299.192, checking for updates shows a new update for the Windows Defender antimalware platform, to version 4.12.17007.18011







Installed without a problem, no restart required. Defender before updating...





After the update...





As with previous antimalware client updates, the update doesn't show in Update History. It can be seen in Reliability History.






Edit: 1st March - another update has been issued, version 4.12.17007.18022. Seems this is to be a regular monthly event.

https://support.microsoft.com/help/4...lware-platform

:)

 

How to manually download the latest version of Windows Defender antivirus antimalware client version?

I am aware that windows defender antivirus antimalware client version automatically download itself to the latest version as a part of windows updates. But i have paused windows updates for 35 days. Is there a way to manually download the latest antimalware
client version now?

 

Windows Defender Security

FWIW

According to this post:
https://www.tenforums.com/antivirus-firewalls-system-security/99752-updated-defender-antimalware-client-post1228544.html#post1228544


this bug is now fixed...

I don't know if this is true because I'm not a Windows 10 user...

 

Looks like the KB article hasn't been updated yet.

https://support.microsoft.com/en-us/...lware-platform

 

... sneaky, sneaky...



*Thumbs

 

This antimalware platform update is available for earlier version of Windows 10 too. Here it is for 1607...

 

Got it here, will have to update the laptop machine in the morning, slowly getting used to Defender, very slowly lol, almost thought of switching back to Avast, but think will stick it out with Defender, in fact removes it from my phone so I won't be tempted to go back to Avast on the desktops/laptop lol

 

edit: I found it. Windows 10 has to be the most counter intuitive OS in history.

Where do you find that System Information in your screenshot? I can only find Defender info when using the old GUI (and it has been updated afaict). So hard to navigate the new system imo.

 

Bru,

You can see the system information by opening Windows Defender Security Centre then clicking on the small Settings icon in its bottom-left corner & selecting About.

By the way, the info shown by the old UI link is still correct.

Denis

 

Thanks, I did figure it out. BTW still having issues with Defender (usually not) running a scheduled task scan since CU. Four computers configured exactly the same with the same scheduled task and none of them act the same. Was hoping maybe this update would fix it, but doesn't look like it.

 

My scheduled scans were still working anyway but I did change the path to the new one given in the KB's info page [https://support.microsoft.com/en-us/...lware-platform link given by Brink above]. I think that any old scheduled scans referring to the old path [C:\Program Files\Windows Defender] should still work because none of the updates have deleted that original set of Windows Defender files [they are merely redundant] and the command line switches remain the same.

Just for info, since the version number is in the path now it might get awkward in the future defining scheduled scans as the version number changes. I have swapped over to using a batch file for my scheduled scans.

• %LatestVersionPath% will always be the latest version because the /od sort order used in the Dir expression makes the For command process all subfolders in ascending date order so the last one to be set as the variable value is the latest one
• -Scan -1 are the switches for a quick scan
• I have this running without incident on 3 Ver 1709 computers [x86 & x64]

Code: set GetLatestVersionPath="dir "C:\ProgramData\Microsoft\Windows Defender\Platform" /ad /od /b" FOR /F "tokens=*" %%i IN (' %GetLatestVersionPath% ') Do Set LatestVersionPath=%%i "C:\ProgramData\Microsoft\Windows Defender\Platform\%LatestVersionPath%\MpCmdRun.exe" -Scan -1[/quote]
Denis

 

I am using Task Scheduler where you are introducing code of some sort which is beyond my capabilities. When CU was first launched I saw others report the same issues with Defender and scheduled scans but not so much since. Really can't see why I would be the only one having issues. Like I said I have the exact same task on four different computers but they don't behave the same and certainly don't work properly as they did prior to CU. It is what it is.

 

Bru,

Sorry I confused things then.

I found another thread of yours [Schedule Scan in Windows Defender Antivirus.

• That being the case, you'll have the tasks' various properties [General, Triggers, Actions, Conditions, Settings] set up the same way on each computer. If all the computers are at Ver 1709 then I expect the Action tab to show

C:\ProgramData\Microsoft\Windows Defender\platform\4.12.17007.18011-0\MpCmdRun.exe Scan -ScheduleJob -ScanTrigger 55but the '55' can vary.

• Might I suggest that you click on All tasks history [on the right-hand side of the Task scheduler window] so that Task scheduler collects records of scanning attempts

• Can you describe the differing behaviour of each computer's task
  • 1 in terms of the symptoms you see as a user, and
  • 2 as they appear in each task's History tab [note that you will have to double-click on each task as if you were going to edit it just in order to adjust the column widths of the History tab entries so you can see them properly - it's a real pain because you'll have to do the same again the next time you want to look at the History], and
  • 3 as they appear in the Windows Defender log at

%UserProfile%\AppData\Local\Temp\MpCmdRun.log {you can just paste the whole path & filename into File explorer to get straight there}.
Denis

 

I've learned to live with it. It just seems odd that the exact same task doesn't work the same on different machines, when it used to. Just witnessed it again. One computer ran the scan as it should, the other did not. It started with the CU so maybe the next update will fix it, but I won't hold my breath.

 

Update: there is now a new antimalware client update taking the version number up to 4.12.17007.18022





first post now updated.