Jump to content

Negative effects when system is not restarted after ESET update


Recommended Posts

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

 

Link to post
Share on other sites
  • Most Valued Members

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.

Link to post
Share on other sites
  • Administrators

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.

Link to post
Share on other sites

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. 

Link to post
Share on other sites
  • 2 weeks later...
  • ESET Insiders

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

Link to post
Share on other sites
  • Most Valued Members
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.

Link to post
Share on other sites
  • ESET Staff

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). 

Link to post
Share on other sites

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. 

Link to post
Share on other sites
  • Administrators
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.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...