mvburch94

Had this same thing come up on our fleet. It is causing sync issues. Some email will come through, some wont, then some all at once after long periods of no email. Disabling the plugin corrects all sync issues for now. They can also access their email using the gmail site directly, so there is not a huge reason to disable the plugin.

Marcos, Thanks for your reply! The network share in question does have ESET installed. I'll see about gathering Procmon and ESET Log Collector logs. Edit: What is the best way to get in touch with Customer Care to track this issue?

I have an odd one. I've tried searching the forums but did not find anything similar. As part of our process, users will open a report, that report will prompt to print, which opens another application that allows them to send information via email. Its complex, but it seems to work with the applications we have in use. The program in question is Print Boss (pb32.exe). This program is run from a network share on all computers that all users have access to. As a part of our environment, all users require local admin rights on their machines, so we know it is not a permissions issue. Here's where ESET comes in: If a computer has version 6.6.2086.1 of the Endpoint Antivirus installed, pb32.exe will open promptly when called for. If a computer has any later version installed, pb32.exe will hang in perpetuity until we pause protection on the endpoint antivirus. The instant protection is paused, pb32.exe opens up and the process continues as normal. Most of our computers are using the latest version of the Endpoint Antivirus. The only ones that are still on 6.6.2086.1 are legacy hardware tied to production machines that still run on Windows XP. Within the ESMC 7 we have put a policy in place in an attempt to address this issue. These include an exclusion to the detection engine, which points to the network share where the program executable lives. We also have a rule under Networking > Application modification detection which excludes all .exe and .dll files in said network share; basically every process this program uses. After confirming the policies are working on a computer with the issue, the behavior does not change. What am I missing?