I'm running the trial version of NOD32. I just installed it yesterday. I was previously running McAfee. I uninstalled it and cleaned out the registry before installing NOD32.

Today, my wife started up the computer and went to check for new e-mail. We use IncrediMail. Just as the e-mail was coming in, NOD32's scanner popped up and started scanning. I didn't set up any scheduled scans yet. NOD32 flagged these two..........

On both, NOD32 said it could not clean, so I deleted. Not sure what these are or why NOD32 started a virus scan. I wasn't near the computer when she started it, and she didn't watch that closely, so I'm not to sure of all the delails. Can anyone help?

We are seeing a few oddities amongst this issue, will have to wait for Marcos, Jan or Bandicoot to come along...

Are you sure you haven't got a scheduled scan on your system, and maybe it missed one, hence upon next boot it starts?

Cheers

Click to expand...

Contrary to what I said in my OP, I did set up a schedule scan. I forgot I did that. Too many things going on. I set it to scan weekly and to start on Monday the Dec. 20. How it started on the 19th, I don't know.

Hm well I found (after I discovered NOD finding the Spybot dummy during a scan) that NOD also went off when I was scanning the system with Spybot - twice in a row, in fact. So, activation of "access" of that file should cause AMON or IMON to kick off in such a manner, maybe

Hm well I found (after I discovered NOD finding the Spybot dummy during a scan) that NOD also went off when I was scanning the system with Spybot - twice in a row, in fact. So, activation of "access" of that file should cause AMON or IMON to kick off in such a manner, maybe

Hm well I found (after I discovered NOD finding the Spybot dummy during a scan) that NOD also went off when I was scanning the system with Spybot - twice in a row, in fact. So, activation of "access" of that file should cause AMON or IMON to kick off in such a manner, maybe

I just want to say thanks for the help. I'm noob to NOD32 and trying to learn. I set it up according to Blackspears suggestions. I'm finding it easier to configure than I thought it would be. So far I like it a lot. I just wanted to make sure what happened today wasn't something I did.

Correct me if I am wrong, but I thought AMON was NOT supposed to detect spyware and the like. I thought they fell under "potentially dangerous applications" and only an on demand scan with NOD32 was supposed to detect these types of things. What gives? Did they change this and not tell us or did I miss it?

Correct me if I am wrong, but I thought AMON was NOT supposed to detect spyware and the like. I thought they fell under "potentially dangerous applications" and only an on demand scan with NOD32 was supposed to detect these types of things. What gives? Did they change this and not tell us or did I miss it?

Click to expand...

This appears to have been found throuh a scheduled scan which poped up:

Piper said:

Contrary to what I said in my OP, I did set up a schedule scan. I forgot I did that. Too many things going on. I set it to scan weekly and to start on Monday the Dec. 20. How it started on the 19th, I don't know.

Maybe the MODs should try to make this into one thread to diminish the confusion, as these two threads are the same subject, or at least the same detection although one is an on access detection and the other an on demand so I guess there is a difference.

LOL, that's ok, there are 2 many threads on this subject, making my head ache

And yes, AMON sprung into action on that thread, I wonder if it did so because a signature was written before they had PDA's in a seperate database (well that's what it appears to be, or a flag of some sort that can be switched on or off).