Unable To Clean

Discussion in 'ESET NOD32 Antivirus' started by niteghost, Jan 19, 2012.

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

    niteghost Registered Member

    Joined:
    Sep 13, 2004
    Posts:
    122
    Using Essex Nod32 V 5.0.94.0 , did a scan ,but Nod32, is NOT able to clean the Toolbar. I tried to traverse usiing the path indicated by Nod32, but to no avail. What can I do next, please advice.Thanks


    Screenshot:

    http://i43.tinypic.com/29hnv9.png
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Was the potentially unwanted application detected by real-time protection? Could you post the relevant record(s) from the ESET threat log here?
     
  3. niteghost

    niteghost Registered Member

    Joined:
    Sep 13, 2004
    Posts:
    122
    I don't think so, if it dud, then it would not let me install it, right?

    Not sure how I can post the Logs, it is kinda long ?
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    You can find the ESET Threat log under Tools -> Log files. Select "Detected threats" from the drop-down menu, select the records belonging to that detection, press Ctrl+C (or select Copy from the right-click context menu) and paste the text from clipboard here.
     
  5. niteghost

    niteghost Registered Member

    Joined:
    Sep 13, 2004
    Posts:
    122

    1/18/2012 10:54:00 PM Real-time file system protection file C:\Windows\TEMP\SBS_LIBNSIS_TEMP_20120018225349.750_ 31 probably a variant of Win32/Toolbar.Babylon potentially unwanted application unable to clean NT AUTHORITY\SYSTEM Event occurred on a file modified by the application: C:\Program Files (x86)\Sunbelt Software\CounterSpy\SBAMSvc.exe.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    I'm not sure if it's a good idea to use CounterSpy in conjunction with ESET's real-time protection or they may cancel out each other. In this case, it has probably locked up the file and thus ESET could not take any action.
     
  7. niteghost

    niteghost Registered Member

    Joined:
    Sep 13, 2004
    Posts:
    122

    U are probably right, thanks for the input, appreciate it It did "warn" me about the conflict when I installed Essex,I just forgot about it.
     
Thread Status:
Not open for further replies.