Jump to content

DriedFish

Members
  • Posts

    7
  • Joined

  • Last visited

About DriedFish

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    Israel
  1. There has been another module update, and the bug is still there! Have we simply been abandoned by ESET? Thanks. D.
  2. Marcos (or anyone else who knows), Is it still estimated that the hotfix for this problem will by available by Sept. 3 (2 weeks from Aug. 20)? Thanks. D.
  3. Marcos, I just saw that you wrote that on the NOD32 thread on August 4. I have updated at least twice since then, and the problem persists. Maybe I just don't understand what a "hotfix" is. Aren't the updates which require a restart "hotfixes"? If not, how will we know of their existence and how will we get hold of them to install? Thanks again. D.
  4. Marcos, reading Anna's posts as a whole and taking the entire internal context into account, I think that what she means is: 1. When she was trying to copy and paste a certain folder, ESET wanted to prevent her action because in copying the folder, she was moving a file within that folder which she considered a desirable file, but which ESET considered dangerous. 2. This behavior occurred only when she used the trial version of ESET; when she uninstalled it and used the paid version, ESET no longer tried to prevent the copying of the folder holding the maybe-infected file, though at some later point it still tried to delete the file. It wouldn't surprise me if the difference in the behaviors was caused by one of the versions being newer than the other. It is odd that she couldn't persuade ESET to remember to ignore that file. Thanks. D.
  5. I am having the identical problem. I opened a support ticket with my "local customer care" on August 13. They keep sending me cookie-cutter instructions like 'reset this' and 'reinstall that'. None of them do any good, of course, and the problem persists. Thanks. D.
  6. Hi! I got a "Threat Alert" from ESS and when I looked in the log file to see what was going on, the field that seemed to tell me what ESS did said "Action: contained infected files". What does this mean? What did ESS do with the attempted planting of the trojan? What do I have to do (if anything) to further protect myself? Thanks. DriedFish.
×
×
  • Create New...