Hi, I was going to give NOD 32 a trial for a change from my earlier AV program. I was just going thru the reviews in many sites and they have been very positive. I was also checking the features and one aspect of "CLEANING" in On demand and real time was not very clear to me (I also checked the Knowledge base in ESET site). Is it true that for every threat the user has to key his options on a alert screen? The present AV which I use gives a set of predefined actions in the preferences setup itself .>> On detection >>CLEAN. If not being able to clean >> DELETE or QUARANTINE or DENY ACCESS. It can list upto 3 actions one behind the other and it can have the option of denying access to the file for the user to contemplate later.
Hello Nagan By default ESET nod32 will attempt to clean infected files it detects, take a look on this link explaining different configuration options: http://kb.eset.com/esetkb/index?pag...earch&viewlocale=en_US&searchid=1314631283726 All the best NoobStick
The realtime protection always block the threats. The next process - depending of the cleaning level you set- is as follow: no cleaning: the user is asked. standard mode: automatic cleaning, the user is asked only when interaction is needed. Strict mode: automatic cleaning, the user is not asked even if interaction is needed.
Hello, Yes, this I know, but if the false-positive is a system file and that its quarantine prevents booting the PC, it is very annoying.
It's highly unlikely that an FP would be reported on files that are crucial for starting the OS. It's more likely that a user would choose to delete such file that was patched or infected by a virus when prompted for an action.
It's happened before (not with NOD32 as I know). It was a false positive. So I prefer to keep the decision rather than having an automatic cleaning. Each must do his choice: automatic cleaning or not.
So set the cleaning mode to "No cleaning" and you'll be prompted for an action whenever a threat is found. As I wrote, it's highly unlikely that one would encounter a serious FP on system files as it would require multiple failures during the QA process that takes place before releasing updates.
Consulting the documentation, the disinfection process will not delete system files if they cannot be repaired.