Negative effects when system is not restarted after ESET update

[StotheR 0]

Hi,

many of our systems has to be online during daytime, so we do ESET updates at night. This is quite annoying because of late working hours. 

What are negative effects when we update an ESET client and plan the restart in the following night? Is ESET Antivir (Endpoint, File and Mail Security) still fully functional or is the system not secured by ESET until it's restarted?

Regards

 

[Nightowl 202]

Depending on what got updated , sometimes ESET asks for a restart but still have protection for system

When ESET requests a restart , try to download an EICAR test file , it should catch it.

[Marcos 5,071]

Especially when the protection status is red after a product update, it's more likely that real-time protection doesn't work at all. Basically this shouldn't happen frequently (e.g. after upgrade to v7.3+ from an older version) since we don't make substantial changes affecting internal product communication very often.

With the introduction of so-called uPCU updates, this will no longer be an issue and the product will update only after a computer restart.

[StotheR 0]

Thank you for your answers so far. 

I'm talking here about major version updates e.g. from 7.2 to 7.3 which require always a reboot as far as I know. 

[rekun 43]

@Marcos

Is uPCU also available for Efs 7.3?

or is it only for endpoint v8+?

[Marcos 5,071]

To my best knowledge, the first uPCU is planned for upgrade of Endpoint from v8.0 to v8.1

[rekun 43]

Okay, are there any plans to add this to server products as well, as they are even harder to get a reboot window for?

[Nightowl 202]

3 hours ago, rekun said:

Okay, are there any plans to add this to server products as well, as they are even harder to get a reboot window for?

Should probably come but will take more time as far as I believe because server product is more sensitive than the others.

[MichalJ 434]

Hello, in general, once the "uPCU" and "Auto update" is implemented in Endpoint for Windows, we are certainly planning to add it into the server products. Or at least change the behavior, that the upgrade targeted to server, will execute before the actual reboot, meaning the "reboot" operation would trigger the update (the same way as in case of uPCU, which also has a benefit, that it is a differential update, so it has smaller impact on the network as well). 

[LesRMed 22]

Is there not a way for Eset to stop and restart itself to negate a restart, especially on a server? Server reboots are, like Rekun said, hard to get a reboot window for. 

[Marcos 5,071]

8 minutes ago, LesRMed said:

Is there not a way for Eset to stop and restart itself to negate a restart, especially on a server? Server reboots are, like Rekun said, hard to get a reboot window for. 

The problem is reloading drivers, not stopping/restarting ESET. To avoid reboots to update ESET Security, we'll support the already mentioned uPCU updates which will be run after a reboot.