NuclearSSD

I Can see this one has been archived off a few times now, anyway to help find out what is doing this? Microsoft Office 365 - 16.0.12430.20264 ESET Endpoint Security - 7.2.2055.0 Seems Disabling Read and Received email stops this, but not really a solution, would appreciate some guidance please

OK, so seems it is this service, but it does not remove when you ask it to! Order I took to resolve this issue... Remove EFSW Restart Server Run "sc delete epfwwfpr" in elevated cmd (Should get [SC] DeleteService Success) Restart Server Run "sc delete epfwwfpr" in elevated cmd - Yes again to make sure it has gone, you should get a different message... if you get "[SC] DeleteService Success" again then back to step 3.. this has to go before you install again. Install new version of EFSW

Definitely did this in the order you requested, enabled, rebooted, collected logs and sent them to you. I have done the same as above but still getting error. I am just going to try it is a slightly different order... Remove EFSW, Delete Service, Reboot then Reinstall.....

I have followed the guide but then removed 6.5 and install 7.1.12008.0 File Security... However still getting an issue with non-functional modules.

I see this has been archived off... But I see there is no resolution, could someone please advise. It does look like that when disabling "Read Email" under "Email Client Protection" that this issue no longer happens.

Simple question, can we share Dashboards? We have a dashboard that we would like to share with other users. Thanks

Yes... This has been the routed I have taken, unfortunately, this by default is not enabled in the policy, or by default install on the client so I am having to do this manually but getting there

Superb find Sir ? Credit to you on this post

any idea on how to do this by CMD ? going to take forever

Might have come across another post which got me thinking! Looks like my issue is different as the ESET itself was blocking the agent from communicating, it made initial connection then stopped! making me think it was the server, but it seems once the policy had come across, ESET then detected a change to the application and blocked the replication! Allow the communication then resolved my issue.... Adjusting my policy to exclude this from "APPLICATION MODIFICATION DETECTION", or you could turn it off.. Unfortunately I am having to go around and allow it first bef

Linux?

Still the same, oddly though it look like one has checked in today at 3 in the morning, but bit actually given any information to what's installed... It's like it said hello then goodbye and not given any further information other than its name!

Same here, Have about 20 that haven't reported since upgrade on the 19th August! Reboot not helpinghere