In previous versions of NOD32 V3 there was a critical bug, which made it possible for a limited user to remove e.g. system files from their original places by using the quarantine-command in the context menu. This bug has been solved with 3.0.667. Thank you so far, Eset. There is still a little glitch (but not critical). If a limited user now tries to quarantine a file, where he does not have write / delete access, there is a small sound; at first I thought, this would be only a hint for the impossible action. But than I noticed, that there opens a message box, which tells about the problem. As long as this box is open (it closes itself after 1 minute), the quarantine-command is grayed out and unreachable (even for files, where the limited user has full access). The (little) problem is, that this message box opens in the background of Windows Explorer (or whatever file manager is used) and there appears no hint at all, that there is a message box open. I think, that the box is supposed to open in the foreground (or perhaps a better solution: a tool tip (similar when a scan has been started automatically). As I said, no problem at all and not a big issue, just wanted to let you know. Seen on XP SP3 with German build 667.