Very good addition. In one word: the limited user has the right to kill a system, but not to correct his mistake (in case, it is an mistake). In...
The point here is, that this occurs by action of a user. It is not a question, if the file is infected at all, because the (following the new...
Doing so would of course let me do, what I want to. But if eset thinks, that hindering limited users in doing things, where a security problem is...
I prefer to leave the culprit where it is. The limitation is in nod (the part you did not quote). And than come the workarounds. Workarounds are...
I would call it a clever (wo)man's HIPS.
Tell more about your problems, perhaps there is aolution.
Let me guess: You are regularly using an admin account, do you? Eset tells themselves in the help file, that a limited account should be used...
Supposedly tomorrow the new stable version 1.1.0.3 will be out. Kay did some hard work to make some more improvements. Some highlights: Tray...
It is not, the opposite is correct. The reason: If I am the admin of the pc, but log in in a limited account (that's what I do regularly), than I...
Try to initiate a manual update from the admin account. After that NOD32 should update from whichever account your are logged in. But check in the...
Some additional notes: 1. In the OP there have been mentioned Avast and Symantec. Does this mean, that there have been already 2 AV-programs...
As far as I can see, you can permanently disable e-mai-check and web-check, if you uncheck "files" in the respective ThreadSense-settings. This...
Thank you for your response, javacool. I am happy to see, that this is already on your todo list.
As this is my first post here: Hi to all. After installing the new version of SWB (4.0) I tried to make a system snapshot for a limited user...
Separate names with a comma.
