Vacendak

Marcos, I have just tried to play arounf with the "Email client integration" and "Email to scan" options under the Web and Email section. I of course opt in for "Integrate into Microsoft Outlook" and tried to disable only "Enable email protection by client plugins", then selectively for received email/sent email/read email. No luck. Only removing "Integrate into Microsoft Outlook" will do at the moment. While doing those tests: Opening and closing Outlook (then killling the process), I noticed that the ESET interface becomes stuck for a while, and I cannot access the Advanced Setup window, for instance: it opens but does not fill-in, i.e. hangs and remains blank. Even with the Outlook process having been killed, said process kill, or an ESS9 response to closing Outlook, hogs the CPU for a bit (no additional running process shows-up though). Once the Outlook closure is out of the way, the ESET advanced setup window fills up appropriately and I can again remove the outlook integration tick.

Marcos, Thanks for looking into this. Good idea but no. Back to silly CPU load. Oh and I forgot to mention that Outlook cannot be closed (with the ESET add-in ticked on). Well, the application closes, but I have to kill the Outlook.exe process.manually. As mentioned in the other thread, for some reason, not always repeatable, which is annoying: If I leave Outlook alone (with the ESS9 add-in enabled of course) for a while by letting it run in the background, the activity somewhat abates and I can then close Outlook normally. So maybe there is a finite operation that the ESET add-in performs, get stuck somehow and at times completes at other time does not... Sure my PC is old, hence likely to send the fan spinning a bit when it gets pushed too hard, but we are talking about emails here, not high FPS computer gaming. And it definitely worked fine not so long ago. Again, I had only recently realised that ESS9 was ready for download/update, and things were fine prior to that.

There is a serious problem with the ESS9 outlook add-in, I use Outlook 2016 but the symptoms are the same. See the thread "ESET SS9 Huge memory leak with Outlook 2016" It can be disabled within Outlook (options, look for add-in), but I have discovered recently that it gets back on by itself after a while, likely when ESS9 updates. [edit] Even better now, I can no longer disable the add-in from Outlook unless I am running my administrator account, something I do not like to do. The only solution now is to uncheck "Integrate into Microsoft Outlook inder ESS9 "Advanced Setup/web and email/Email client protection". This leads to a continuous red flag but this is the only way for me to be able to read my email without my PC fan whirring like mad for no reason. I have been with ESET for years and always recommend it for being "light and unintrusive", hence my uncovering this problem after long and protracted attempts to realise it was down to ESS9... one of the last thing I would have thought possible. I cannot say for sure, but this problem may have cropped-up when I pressed that button to upgrade to SS9. Can something be done about this please? The first post on the linked thread is from January already.

Add me to the list. Removing the ESET add-in indeed solves the problems listed above: Slow M$-Outlook 2016 start, huge CPU usage for no reason, and having to close M$-Outlook by killing its process. On that last point: If M$-Outlook runs for a while (at high CPU usage) and one waits for it to calm down a bit, it becomes possible to close it the normal way without having to kill the process. The CPU usage spike and the "cannot close M$-Outlook" issue had been bugging me for a while and I have only checked the possible to ESET SS9 (9.0.381.0) this morning, hence the two months since the last post.