Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. I had this problem and for me the solution was to execute the esets daemon manually before running the main program. The daemon is something like /opt/eset/esets/sbin/esets_daemon. That's off the top of my head, I forget the exect path. But once you run that (manually or in a rc file) the program just works as intended.
  2. My case is #233719 ("Setting up application whitelist + reverting to default settings"). I never said it simulated my keystrokes/mouse just that it somehow changed the settings. But if the settings are sticking with the defaults like they're supposed to, that's good enough for me. Now to see about comparing the xml files. ::exports and compares settings:: Welllll... the XML files I exported do appear virtually identical. I don't know why the blue circles indicating CHANGES from the defaults keep appearing even after I reset the defaults, but maybe you're right and it's just a
  3. tl;dr: What to do when Eset tech support doesn't get back to you? Not sure, but I may have malware. Longer version: I contacted Eset customer care with a couple questions<sup>*</sup> on February second and received an email stating “We will review your case and respond within 1 business day”. It’s 10:00pm on the fifth now and I still haven’t received a response. What should I do? <sup>*</sup> My questions are twofold, and I’ll elucidate them here in case anyone on the forum can answer them. Firstly, I suspect that resetting Eset’s settings
  • Create New...