Conflict between SUPER encoder & NOD32 v3.0.772

Discussion in 'ESET NOD32 Antivirus' started by Philippe_FR22, Oct 17, 2008.

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

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Hello,
    I just noticed that there is a problem with NOD32 and SUPER encoder 2008.
    During installation and during SUPER execution, NOD32 (v3.0.772) reach 99% of CPU and only with that application !! With other applications, no problem were noticed.


    After installation and when SUPER is executing, NOD32 stay at 90% and more and it is impossible to use SUPER application. After having killed SUPER, everything is OK... When executing other applications, no CPU overload were noticed...

    Regards
    Phil
     
  2. Rmuffler

    Rmuffler Former Eset Moderator

    Joined:
    Jun 26, 2008
    Posts:
    995
    Location:
    San Diego, CA USA
    Hello Philippe_FR22,

    Please exclude SUPER encoder.

    Thank you,

    Richard
     
  3. Philippe_FR22

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Thk you for answer... I should do the same for the installer, same problem... But why this particular application/installer ?
    Thk you
     
  4. doktornotor

    doktornotor Registered Member

    Joined:
    Jul 19, 2008
    Posts:
    2,047
    Shrug; who knows. Stupid coding most likely. There's a funny thing called netfxupdate.exe from MS which gets run on installing .NET hotfixes... It conflicts with virtually any antivirus I tried, exact same behaviour as you've described. Just hangs, eats CPU and produces no errors, nothing useful until you kill it or disable AV to let it do its job.
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Just to make sure, do you have advanced heuristics and runtime packers disabled for access in the real-time protection - ThreatSense engine setup?
     
  6. Philippe_FR22

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Hello,
    Configuration is the "default one" proposed by NOD32 Antivirus (EAV 3.0.772)

    Regards
     
Thread Status:
Not open for further replies.