Nod32 detects all .exe files from any games as a potential viruses

Discussion in 'ESET NOD32 Antivirus' started by Leschy, May 22, 2008.

Thread Status:
Not open for further replies.
  1. dorgane

    dorgane Guest

    Make manual update there is 3121 ;)
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    No need to send it, ESET are aware and it is being addressed.

    Cheers :D
     
  3. metalalbert

    metalalbert Registered Member

    Joined:
    May 22, 2008
    Posts:
    46
    Cool! You guys are fast! Thanks for the help, the notice is gone now :)
     
  4. dorgane

    dorgane Guest

    ...del this post
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    The problem has been identified and fixed with update 3121. It was not actually a typical false positive caused by signatures or heuristics, hence it took us some time to figure out the cause.
     
  6. Leschy

    Leschy Registered Member

    Joined:
    Sep 23, 2007
    Posts:
    55
    Location:
    Munich
    yes, it is fixed, great job. Thank you very much!
     
  7. MasterTB

    MasterTB Registered Member

    Joined:
    Jun 19, 2007
    Posts:
    547
    Location:
    Paran?, Argentina

    Running 3.0.650 Spanish here, AV sig 3122 now and still no problems. But as I've been reading it is a 657 problem??
     
  8. bafranksbro

    bafranksbro Registered Member

    Joined:
    May 22, 2008
    Posts:
    8
    I'm not getting the false positives anymore but every time it does an automatic update it locks the computer up and makes it unresponsive, I have to manually restart the computer by holding my reset button. It doesn't lock the computer up on manual updates since I did one when the "fixed" virus definitions were released but every other update since then was automatic and has locked this thing up. It locked it up when it did an auto update while I was having the false positive problem and it's still doing it now.

    Again I'm running v3.0 on this computer but on my laptop I'm running v2.7 and it hasn't had any problems at all. I'm thinking of going back to v2.7 on this computer as well.
     
  9. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    The easiest fix is uninstalling and reinstalling EAV. V 2.7 is not developed anymore and new features will be added to v3.
     
  10. heiopai

    heiopai Registered Member

    Joined:
    May 22, 2008
    Posts:
    5
    i have done this and i HOPE this has fix the problem.

    it will be great for the customer if eset explain in detail what caused the problem, maybe in a little technical way so the user can understand what happend today.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.