Jump to content

Bug in EEA 6.5.2132.5 found


Recommended Posts

After the Certfix issue of ESET , ESET released a new Endpoint Antivirus version of 6.5 6.5.2132.5 however a new bug was introduced causing automatic roll out to fail. 

What happens is the following:

We install the MSI using a command line script and cfg.xml next to it for all the default settings. It doesn't matter if the install is started via commandline or manually but the following happens:

1. ESET installs with no issues
2. When the software is activated the update failed because no username and password in the license (this is correct because it is a local install and the update mirror is local and the license does not contain the username and password). In the CFG.xml a local mirror location has been designated. 

3.You open Advanced Settings and check the update folder which is correctly listed as according to the cfg.xml along with all the other settings (although the profile name is weird). 
Anyway when you press OK to save the settings

4. press update the system updates from the local mirror. withou any issues. 

The bug is that when you install ESET with the cfg.xml it sets all the settings as according to the cfg.xml file but it does not activate the settings untill you manually open the settings and press OK! 

This is an issue as we have 1000 PCs that we need to do manually which is not an option at this time.  


Link to comment
Share on other sites

  • Administrators

Later this week we are going to release a new build of v6.5 which should address the issue with update settings.

Just out of curiosity, are you using Endpoint v6.5 because of Windows XP on the machines or there's another reason why you don't want to upgrade to Endpoint v7?

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...