Jump to content

Restart required after upgrade of product questions


Recommended Posts

I was wondering if ESET is planning on changing the way upgrades are handles for ENDPOINT AND FILE Security products for Windows. Is it possible to make an upgrade over the top without the restart? I have many customers who bypass the REBOOT option via upgrade tasks in ESMC. Some of them forget about the restart and then have many machines in the pending reboot status with modules in NON-Functional status. Question. In this pending reboot status are the machines vulnerable to malware? I tested one of the machines in this non-functional status after upgrade and it was not picking up Eicar test file.  

Is there any technical explanation as to why reboots are needed to finalize upgrade of ESET products from older version to new?  

Link to post
Share on other sites
  • Administrators

The ultimate solution will be uPCU (micro program component updates) known from consumer products. A uPCU will be downloaded but installed only after the next computer restart. We plan to deliver first uPCU for Endpoint and other business security products with the release of ESMC 7.3 in Q4 this year.

Link to post
Share on other sites

The problem with uPCU concept is many commercial concerns have policies in place that dictate all software updates be tested for operational issues prior to being deployed en mass to the corporate network.

30 minutes ago, tmuster2k said:

Is there any technical explanation as to why reboots are needed to finalize upgrade of ESET products from older version to new?  

The OS might have locks on system areas Eset updates.

Link to post
Share on other sites
  • Administrators
1 hour ago, itman said:

The problem with uPCU concept is many commercial concerns have policies in place that dictate all software updates be tested for operational issues prior to being deployed en mass to the corporate network.

This is not an issue. Program updates can be controlled in the advanced setup plus they will require admin's consent within the ESMC console.

Quote

Is there any technical explanation as to why reboots are needed to finalize upgrade of ESET products from older version to new?  

Without a reboot, old drivers remain loaded after ekrn and other binaries have updated to a newer version. The changes between the two versions are so big that old drivers cannot play with the new ekrn. However, in the future uPCU will work even without a restart with some exceptions (e.g. if Device control is enabled and attached to the system drive); in such case a reboot will always be necessary.

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