Forum Discussion
Exploit Guard - Network Protection
Win 10 Pro.
One was 1709 and the other was 1603.
In the case of 1709, we had to delete wdnsfltr while unjoined.
In the case of 1603, we took it off the domain, applied 1709, rejoined and network came back. wdnsfltr never started up in this case.
DH
What Windows Defender platform version was running at the time of the issues, look at C:\ProgramData\Microsoft\Windows Defender\Platform\x.xx.x.xxx for example. The issues we've seen have been a combination of Defender platform and OS version.
Do you still have issues now with platform 4.14.17639.18041-0?
- Dylan HainesMay 10, 2018Copper Contributor
Both clients are at that version now, but part of the troubleshooting for both was to update them to 1709 so not sure what was there before.
On checking now on other PCs, some platform folders are empty, some are at 4.12.17007.18022-0, etc etc
How do we ensure everyone has current Defender regardless of OS patch level - is there a KB we can quickly push on everyone?
Thanks
DH
- Steve NortonMay 10, 2018Brass Contributor
Do the clients without the latest platform version have the latest engine and definitions, Get-MpComputerStatus in PowerShell will show you?
- Dylan HainesMay 10, 2018Copper Contributor
Fails on PCs where AVG is still running.
PCs where AVG is gone have been updated to 1709 and so far have the latest Defender.
DH