• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 490
  • Last Modified:

NOD32

So, this NOD32 log states that it scanned 650,000 items.  I infection was fouuuuund but not cleaned.  Now, all you have to do is simply scan the log of the 650,000 items it scanned, 20 at a time, to find the one item not cleaned.

Since I don't have few days to devote to this, does anyone know of a better way to find the secret file not cleaned using ONLY NOD32?
0
classnet
Asked:
classnet
  • 2
1 Solution
 
TMekeelCommented:
If you right-click in the scan log and export to txt file, you can search it with notepad.
If you really want to stay in ESET, click Computer Scan on the left, click the date and time of last scan in the middle, and you should be able to scroll through pretty quickly and find the infected file.

Usually a non-cleaned infection would be quarantined as well, which is in Setup > Toggle Advanced Mode > Tools > Quarantine.

Under the tools section, you can also click the Log Files link, right-click a log file, and check "Scroll Log", as well as filter the log by event.
0
 
classnetAuthor Commented:
Sorry... I don't have the time to scroll 650,000 lines.

Piss poor program... they should indicate the file that cannot be cleaned.
0
 
classnetAuthor Commented:
NOD32 sucks
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now