It looks like the problem is back again. I think Is is happen after todays update at 2PM.   /opt/eset/esets/sbin/esets_daemon --version /opt/eset/esets/sbin/esets_daemon (esets) 4.5.15 There is a lot of /tmp/bt.esets_daemon.* files cat bt.esets_daemon.EkR1IE signal = 11 bad addr = 0xcfc00004   /opt/eset/esets/sbin/esets_update --verbose Naruszenie ochrony pamięci (translate: Memory protection violation)   Esets hung in starting loop systemctl start esets.serv