Nick M

Ah. Thanks very much for your clarification. I guess I got some bad advice from a support rep who advised that I should watch this thread and that the update would make a difference. Sounds like I'll need to get TCC profiles set up to work around this.

Ah, apologies for my apparent total inability to correctly read dates. Don't know what happened there. I just pushed Endpoint Antivirus 6.7.600.0 using a client software install task, and the client machine still showed a popup asking for full disk access (screenshot attached here). This is the second install of this build that I've done, with the same behavior.

@AlexW, Endpoint Antivirus 6.7.600.0 has been available for about a week, as you mentioned. So it predates the recent posts in this thread. Do you mean that a new version of 6.7.600.0 is available (with no version number change), which fixes the full disk access issue that @TomasP was talking about a couple of days ago? In that case, can we continue using preexisting client software install tasks that are set to use that version number, or do we need to recreate them? Thanks for your help!

I'd like to post a reply to this topic, but replies are no longer allowed: With Chrome 69 now discontinued, and Chrome 70 as the current stable version, how has ESET protection changed? Does Endpoint Antivirus still protect Chrome? I have not seen any more of the error messages I referenced in the other thread, so I assume that ESET has stopped attempting .dll injection into Chrome.

A post-crash alert in Chrome like the one you linked is exactly how I became aware of this issue.

I understand that ESET Endpoint Antivirus uses .dll injection to Chrome as part of its normal operation. Google has announced that starting in Chrome 69, Chrome will start blocking this code injection, and by January 2019, all injection will be blocked. (https://blog.chromium.org/2017/11/reducing-chrome-crashes-caused-by-third.html) How will this affect the protection that Endpoint Antivirus provides, and how that protection happens? Will there be any reduction in Endpoint Antivirus' capabilities? Or does ESET already have adaptive changes in development to address this Chrome change?

I'm experiencing this same issue in an enterprise deployment. As Mox described, with Endpoint Antivirus and Google Drive File Stream running simultaneously, our Macs become unresponsive to the point that they are unusable. Just wanted to add my voice as another administrator who's very interested in a fix for this issue.