SamBul27

When CompatTel is running, this is a prompt for me to investigate in Event Viewer if some unauthorized malware was installed. So disabling it completely is not a good option, unless I can disable it for Eset updates ONLY. Also, on older PCs CompatTel is helpful in prompting Microsoft to adapt its new code to old device drivers not updated for many years by the device manufacturer, which may cause blue screen otherwise, so its questionable if this tool is "useless". It might be Eset adapted minor module updates several times daily, which triggers CompatTel to run at each Eset DB & Module update. Not really a good idea, it causes unbearable activity by CompatTel at each update. Weekly Eset module updates would be more reasonable.

Does anyone experience similar issue? Any suggestions? It happens when internet is switched on after several hours offline.

After update to the latest Eset 15.0.16.0, Microsoft CompatTelRunner.exe runs very long at near 100% CPU and very active disk usage after EACH Eset minor dbs update. Never seen this before, but it looks now Eset updates trigger CTLR activity typical when a new unknown program is installed. Why such change happen, how fundamental are hourly Eset updates to trigger CTLR, and is there a way to selectively disable Windows Compatibility Telemetry triggering only after Eset updates?

I just updated all modules, still being in pre-release mode. The bug seems to be fixed for now, Interactive notifications are working again. The modules updated today were: Databases for advanced antispam module: 6819P (20210430) Rapid Response module: 18186P (20210430) Detection Engine: 23222P (20210430)

Mine is the same, so its obviously a mix of release and pre-release modules in that update mode. B&PP in my tests doesn't affect Interactive mode alerts showing up.

I'm currently on pre-release. So I assume, ALL modules installed are pre-release modules, unless not available. I don't have any issues right now with Interactive dialog, after reverting to older versions of modules updated April 28, 2021. You know what modules were released that date, I don't remember. So for me the missing Interactive dialogs bug is clearly module specific, and its NOT caused by firewall module. When I have time, I'll reverse to release modules and see, but why do that, if even previous pre-release modules don't cause such bug on my end? I think, the devs should allow sig updates despite module updates are on hold. I mean, some folks still use very old Eset versions, and still get sig updates.

By Module Rollback option in Eset Update setup. It suspends module updates until set time or till suspension is revoked. However, this should not stop signatures and other Eset components updates required to provide all claimed protections. In fact, module updates are seldom, may be once in several months, but signature updates are done many times a day. So it appears to be a bug that suspending module updates also suspends signature and other regular DB updates required for Eset to function effectively.

This reply doesn't answer my Q about signature updates, while module updates are blocked. As to Firewall module, I've 1420 of 02/18/21, and it works very well, so I've no intention to go back to 1418, and in general to older modules, since currently installed pre-release versions work well. It might be an old FW "pre-release", but as soon as I rolled back from April 28, 21 two or three module updates (not the Firewall module), Interactive mode started working properly. So a different module (out of 3 updated on pre-release yesterday) affected this. Hope it narrows the bug search for devs.

I just checked Eset settings and found that I'm on Pre-release update channel. I rolled back the last modules update, rebooted, and now I've Interaction Prompts on screen again. Eset version remains the same, and I noticed that Eset Firewall module version 1420 remained also the same, only modules updated on April 28, 2021 were reverted, since there are no modules with that date anymore in the list. So it looks like a different last updated Eset module causes the issue. I blocked module updates for now. Does it mean that signatures won't be updated either? is there a way to keep updating signatures, while blocking module updates? May be its better to stay on Release channel rather than Pre-release in general?

May be there is a Pre-release Eset Firewall module that fixes the bug? Let us know pls when its released. Juts tried Windows Weather app, and it doesn't load data either. Had to switch to Auto Firewall mode.

I'm curious, why for example "DNS poisoning attack prevention" or "Maintain inactive TCP connections" code would be "removed in new Eset versions"? Removed without any substitution? Moved to Enterprise version?

Eset main GUI was open when Telegram was launched. But this is just an example, many apps behave like this. I did reboot the system (not shutdown) to no avail. I rely heavily on interactive mode when running some apps, so its very unfortunate Eset bug, basically doesn't allow me to run quite a few apps, because some of their components must be allowed to access web, while others should not be.

Here is the screenshot. Is it possible that Windows may consider such Dialog as a popup and block it? But no recent Windows 10 20H2 updates, last security update installed 2 weeks ago.

Tested again. After Learning mode created rules for Telegram, I switched to Interactive mode, and Telegram loaded content based on the above new rules. But after I disabled these new rules and restarted Telegram in Interactive Firewall mode, it again couldn't load any content, and no Eset Prompt appeared. So Interactive Mode appears broken in the last release. Didn't happen to me before anything like that. The main Eset GUI is kept open, but it doesn't affect anything.

Just noticed that Eset Firewall Interactive Mode doesn't work any longer after recent upgrade to v. 14.1.19 . The apps that required manual permission before in Interactive mode, or even had such permission in Advanced Rules, now can't access internet. Eset shows no prompt ever at such apps launch. The same apps work fine in Eset Firewall Auto and Learning modes. As an example, Telegram stopped loading content despite existing "Allow" rule, and no Eset prompt appears at Telegram launch. But there are a lot more apps behaving like this. I tried to delete all Telegram rules, then they get auto created in Learning mode, but Interactive mode still doesn't show any prompts and blocks Telegram. However, it passes all browsers traffic without prompts. Any way to fix that?