jhufford

Thank you both for the reply, I will retry your suggestion about the order in which the add-on is enabled. I might try disabling the scan of outgoing mail.

What was the solution to this issue, was there any resolution. This issue is still affecting all users running Outlook 2016 or Office 365 Outlook 2016, latest version of 5.0.2265 which according to your own documentation is supposed to support Outlook 2016. Five or more times a day the plugin crashes Outlook 2016 until Outlook auto disables the plugin.

What exactly did your log show you, we have this exact same problem, we have ever port under the sun open and have it opened by application nothing fixes this issue. If we disable the firewall for ten minutes, we can connect for ten minutes. If the firewall is enabled, not only does the attempt to connect to the machine with powershell fail, it does not even generate a log entry. If you try to verify that the ports have been opened on the machine the profile was applied too, the ports do not show up in netstat -aon, or in the ESET SysInsepctor. Someone please point me in the direction of where I can find what exactly the firewall is doing when it is on versus when it is off, because we cannot find an explanation internally we our at a loss.