NOD32 false positive when Updating McAfee Enterprise

Discussion in 'NOD32 version 2 Forum' started by Pain of Salvation, Dec 1, 2005.

Thread Status:
Not open for further replies.
  1. Pain of Salvation

    Pain of Salvation Registered Member

    Joined:
    Apr 21, 2005
    Posts:
    398
    NOD32 detected this when updating McAfee Enterprise 8.0i:



    Happy Bytes, I´ll submit this to you.
     

    Attached Files:

    Last edited by a moderator: Dec 1, 2005
  2. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    You don't have NOD & McAfee running at the same time do you (on-access scanners)?
     
  3. Pain of Salvation

    Pain of Salvation Registered Member

    Joined:
    Apr 21, 2005
    Posts:
    398
    No, I don´t. NOD32 as realtime and McAfee as backup scan (on-demand only)
     
  4. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    Alright, well if you submitted the file to Eset, it should be fixed in a few days.
     
  5. Pain of Salvation

    Pain of Salvation Registered Member

    Joined:
    Apr 21, 2005
    Posts:
    398
    Have just sent it to Mike.
     
  6. POS

    POS Guest

    When will Eset fix this false positive? I really need to update McAfee..
     
  7. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    I agree that the false positive should be looked at, but if updating McAfee is a priority, then maybe you can just disable AMON, but only while updating. My guess is that since a temporary file is the problem, McAfee and NOD32 (with AMON enabled) would run just fine together once the update has completed.

    Again, I believe the false positive should be looked at. However, if you cannot wait a few days, and updating McAfee is a priority, then you must do what you must.
     
  8. POS

    POS Guest

    Ok, I´ll do some tests disabling AMON here... thanks!
     
Thread Status:
Not open for further replies.