stapp Posted July 16, 2020 Report Share Posted July 16, 2020 Today at boot I got the Windows notification sound. It was Defender telling me it had cleaned 5 items (they will be eicar) It does not say when this 'clean' occurred. There is nothing in Defender history or quarantine. I have the latest cumulative for Win 10 2004 installed (now on build 19041.388) It is not possible to work out when this happened or what they found. Going here to show latest Defender info doesn't help, I mean some of the entries there are strange. but perhaps as a result of the Cumulative? Event viewer..Application and Service logs..Microsoft..Windows..Windows Defender..Operational Debug logs and screenies attached. a2guard_20200716045339(1152).zip Link to comment Share on other sites More sharing options...
marko Posted July 16, 2020 Report Share Posted July 16, 2020 maybe EAM is off in Windows Security Centre ? Link to comment Share on other sites More sharing options...
stapp Posted July 16, 2020 Author Report Share Posted July 16, 2020 Yes it is, but EAM says I am protected by EAM I may do a few unticks and reticks and a reboot as well. EDIT.. Unticking and reticking the Windows Security Center integration in EAM advanced settings has restored EAM as the provider. Link to comment Share on other sites More sharing options...
marko Posted July 16, 2020 Report Share Posted July 16, 2020 nice one - might be worth checking, over the coming days, that EAM registers in wsc each time you restart/turn on the machine as I had the same problem but it was intermittent - sometimes EAM registered after boot but sometimes not - I had to reinstall EAM in the end to fix it Link to comment Share on other sites More sharing options...
stapp Posted July 16, 2020 Author Report Share Posted July 16, 2020 27 minutes ago, marko said: nice one - might be worth checking, over the coming days, that EAM registers in wsc each time you restart/turn on the machine as I had the same problem but it was intermittent - sometimes EAM registered after boot but sometimes not - I had to reinstall EAM in the end to fix it First time it's happened to me marko. It would be nice if EAM gave some indication that it had not registered in WSC and that Defender was doing scans and downloading definitions. Link to comment Share on other sites More sharing options...
stapp Posted July 21, 2020 Author Report Share Posted July 21, 2020 Not happened since. I check every morning after a cold boot. Was this of any interest to you Frank? Or was it just one of those 'race' events? Link to comment Share on other sites More sharing options...
Frank H Posted July 27, 2020 Report Share Posted July 27, 2020 No idea stapp. What I do know is that we added a fix to 2020.8 that will stabilize WSC integration. We've noticed this issue on a couple of machines only sofar. Windows WSC API isn't the most stable one.... Link to comment Share on other sites More sharing options...
stapp Posted July 27, 2020 Author Report Share Posted July 27, 2020 Only happened that once for me Frank. Will try new beta now. Link to comment Share on other sites More sharing options...
Recommended Posts