Required and recommended

[dr.nod32 0]

Dear everyone,

Can you tell what can make a difference between these two statuses after auto-update from the previous subversion? On calls for immediate restart, the other recommends restarting to upgrade the client. In both cases, the real-time module still works.

Best regards,

Denis

[Marcos 4,935]

It depends on several factors, e.g. on the version of the product that you upgrade from or protection features that are active. Or if a particular protection reports that a reboot is required. We are working on improving this so that only a reboot after a critical hotfix will be required, otherwise it should be only recommended.

[dr.nod32 0]

Thank you for the reply, Marcos! When you say protection features, do you mean like the Device control that requires a restart when turned on, so if that module is updated, the endpoint client will require a restart again?

Thank you,

Denis

 

[Nightowl 198]

26 minutes ago, dr.nod32 said:

Thank you for the reply, Marcos! When you say protection features, do you mean like the Device control that requires a restart when turned on, so if that module is updated, the endpoint client will require a restart again?

Thank you,

Denis

 

When it shows in red , click Setup , and then you would be able to see which modules are pending for restart , it will show you that they are not active.

[Marcos 4,935]

1 hour ago, dr.nod32 said:

When you say protection features, do you mean like the Device control that requires a restart when turned on, so if that module is updated, the endpoint client will require a restart again?

Device control uses its own driver edevmon.sys. If the driver is updated during a product upgrade, a computer restart will be required for the new driver to load.

[dr.nod32 0]

Thank you both, Marcos and Nightowl,

Here are screenshots of the Setup pane on the "Restart required" client.

Best regards,

Denis