icon tray options

I believe that NOD32 v.5 can be closed by opening the GUI and clicking on the "X" while holding the shift key. Excuse me if this is not what you were looking for.

 

It works !!!!!!!!!! I finally got the answer for my simple question. Thank you very much.

but..... Eset, it is not normal to close a password protect av so easily....

I mean.... Nod32 v5 did ask if I want to close but didnt ask for the password before closing and THAT is not normal or safe.

guest

tell me why a Eset moderator didnt give me this answer before a member....

 

Sorry, but you didnt targeted the AV (a.k.a. ekrn.exe), you will need password when uninstalling.

 

unfortunately, you are right I am disappointed.

 

Security is security. Wondering which security program you want to coexist with NOD32? Also the system specs.

 

Hello,

When you close the antivirus with the method described by thehudd , the protection is still active. Only the interface is disabled.

Do this experiment:
1. Close NOD32 with the method indicated.
2. Click here: eicar.

You can also check that after the closure of NOD 32, Windows Security Center indicates that NOD32 is active.

To turn on the GUI (interface), run "C:\Program Files\ESET\ESET NOD32 Antivirus\egui.exe"/hide/waitservice"(with quotes).

 

No, not "necessarily".

When the GUI is closed with the method described the protections is NOT disabled (see my previous message).

 

Disabling Real-Time protection should be enough, but mostly you don't need to disable anything. Vendors just say that so they have something to hide behind when it goes wrong IMO.

 

i did not understand the gain of close closing the gui with shift + close
is still in memory ...

 

Hello,

I think I understand the crux of your issue, which is that you want to know how to disable or otherwise unload ESET NOD32 Antivirus prior to installing another software package, is that correct?

This piece of advice is actually an old one, dating back to the Microsoft Windows 95/Windows NT days and may no longer be applicable. There is actually an interesting reason for this, and here's why:

Back in the mid-1990s when Microsoft Windows 95 appeared, many of the developers of anti-virus software released new versions of their products, just like they would with any other new operating system release. However, Microsoft and the various anti-virus developers did not cooperate as much as they now do, and many of these programs were written using a variety of methods that are, generally-speaking, considered poor programming practices, such as making use of undocumented APIs, modifying parts of the operating system running in memory and so forth. While these types of programming "hacks" did work, they tended to do so only when other programs that did similar things were not present. When two (or more) programs started changing the internal behavior of the operating system, it generally resulted in a lock-up or a crash due to the programs not being able to cope with the changes introduced by each other into the environment.

Some antivirus programs also tried to intercept disk and file I/O in various ways, and while those methods tended to work well during typical PC usage, began to break down when performing operations involving the creation, usage/execution and deletion of massive numbers of temporary files, such as during the installation of new software or software updates.

These days, Microsoft has published APIs and guidelines available for software developers who create these types of applications and, in turn, the various third-party developers who write security software are better about using them, so this is less of an issue today then it was a decade-and-a-half ago.

It certainly does not hurt to be cautious and disable security programs before performing some sort of low-level disk operation, however, chances are, your security program is not going to interfere with defragmenting or formatting a disk volume, or installing software.

I do think there are still some circumstances where it is a good idea to disable or uninstall antivirus software, for example, installing an operating system service pack, but that's more to speed up the installation of a huge number of updates to the operating system. And, in the case of a service pack, that's something which is downloaded from a very trusted source, e.g., the developer of the operating system'. And you would always want to have the latest version of the antivirus software already downloaded and ready to re-install after the service pack finished installation.

If you are just installing a routine application obtained from a trusted source (e.g., the author) but are still concerned about the possibility of interference from the anti-virus software, you can always go ahead and disable the on-access scanning component of the anti-virus software until after the installation is complete. I myself would not do this unless a problem occurred when installing the application, or if there was a specific mention of an incompatibility between the installer and my anti-virus software.

Regards,

Aryeh Goretsky

 

I do believe that in v4, disabling real time protection via the task bar icon (right click) closed the application. Used many times to close down while installing new software! Could be wrong though.

 

agoretsky

thans for your long post. Very interesting.

i believe too but if you do ctrl-alt-delete to see the "task manager " (?), ekrn.exe process is still running, so protection is disabled or not ? It must be just "pause" because icon turns red

 

If you dont want realtime protection, The "Automatically start the real-time filesystem protection" option in Advanced setup is useful.

 

Hello,

piranha's,

When you close the antivirus with the method described by thehudd , the protection is still active. Only the interface is disabled (Quand vous fermez l'antivirus avec la méthode décrite par thehudd, la protection est toujours active. Seule l'interface est désactivée).

Do this experiment (Faites cette exépérience):

1. Close NOD32 with the method indicated (Fermez NOD32 avec la méthode indiquée).
2. Click here on: eicar (cliquez ici sur eicar).

You can also check that after the closure of NOD 32, Windows Security Center indicates that NOD32 is active (Vous pouvez aussi vérifier qu'après la fermeture de NOD32, le centre de sécurité de Windows indique que NOD32 est actif).

To turn on the GUI (interface), run "C:\Program Files\ESET\ESET NOD32 Antivirus\egui.exe"/hide/waitservice"(with quotes) (Pour réactiver le GUI, exécuter... (avec les guillemets))

 

i prefere the first version of your answer I received by mail notification

pause=disable=turn off only the component's filtering(scanning).