prutulica
February 2nd, 2009, 07:50 PM
Hello.
I've been running NOD32 3.0.669.0 for about 2 weeks and today I got infected with Neshta.A virus.
What is strange is that when I scan from within NOD32 itself or from context menus it is able to detect this virus... However, if try to manipulate the virused files (move, rename and even launch!) it doesn't detect anything...
The "Real-time file system protection" is enabled, ALL the options available for it under "Advanced setup" are checked and I disabled "Optimized scanning" as well. So the real-time protection I'm using is at maximum... and still the situation doesn't change at all.
On "Scan on" there are the following options (checked of course): File Open, File Creation, File Execution.
Any ideas why it behaves like this??? I mean NOD32 clearly is able to detect the virus when I force a manual scan... but why it isn't able to detect it on the fly as I "play" with the viruses files (on my local hdd)?
I tend to believe this is a bug.
I've been running NOD32 3.0.669.0 for about 2 weeks and today I got infected with Neshta.A virus.
What is strange is that when I scan from within NOD32 itself or from context menus it is able to detect this virus... However, if try to manipulate the virused files (move, rename and even launch!) it doesn't detect anything...
The "Real-time file system protection" is enabled, ALL the options available for it under "Advanced setup" are checked and I disabled "Optimized scanning" as well. So the real-time protection I'm using is at maximum... and still the situation doesn't change at all.
On "Scan on" there are the following options (checked of course): File Open, File Creation, File Execution.
Any ideas why it behaves like this??? I mean NOD32 clearly is able to detect the virus when I force a manual scan... but why it isn't able to detect it on the fly as I "play" with the viruses files (on my local hdd)?
I tend to believe this is a bug.