TomasP

Hi, we have introduced ESET LiveGrid with our v5 Windows products.

Hello, I am glad to announce that we have just released new versions of ESET Cyber Security, ESET Cyber Security Pro, ESET Endpoint Antivirus for Mac OS X and ESET Endpoint Security for Mac OS X with added support for Mac OS X 10.11 El Capitan. The files are already available to download at our international site www.eset.com/int/download and the local sites should follow soon. T.

Hello, I recommend to create an activation task in ERA and assign it to "Not activated security product" dynamic group, with the trigger set to when the computer joins the group. This way, upon the installation and first connection to ERA, the product will get license details and activate automatically. You can also use the command line parameter INSTALLED_BY_ERA=1 so that the product does not prompt the user to activate before the automatic activation takes place.

Hello, Our developers are working on the plugin and we aim to have it finished in the following weeks. Once it passes testing, we will release it. Thank you for your understanding.

Hello, As there were many issues fixed in the 6.2 version, I recommend to upgrade to this version first and see whether that changes things. You can upgrade using the component upgrade task (does that work in your situation?)

Hello, After you uninstalled our product, did the issue disappear? In other words, did you confirm the issue was caused by the presence of our product?

As the issue happens on various computers, could it be that the USB drive itself is corrupted, or the files on it get overwritten? Did you try a different drive?

Hello, Please try to install the Endpoint locally, error 1603 usually means an error in the Windows Installer, not the ERA task. I suspect the installation will fail locally as well, so it won't be an ERA issue. In that case, please create a log from the manual installation according to hxxp://support.eset.com/kb406/and submit it to our support team at hxxp://www.eset.com/support

Hello, the OVA is intended to be deployed as is. Additionally, the Windows version of ERA server defaultly uses a different database type than the OVA, so they would not be compatible.

Hello, As for the point 2 from rugk's list, you do not need to uninstall version 8 first. If there was an issue, it was an isolated one (as confirmed by other people in this thread). Also by directly reinstalling, you eliminate issues from points 3 and 4 - the settings will be kept and converted to the new format, as well as the license will be preserved. Users installing v9 as a fresh installation will have a link in the activation dialog to a username/password to license key converter.

Hello, I have seen this issue occur in the past. In my experience it happened when not all components upgraded (some did and some did not, so they were not compatible then). What helped was to run the component upgrade task once again, so that all the remaining components upgrade too and get "on par" with the rest of ERA.

Hi, I am not sure why would uninstallation of Trend Micro also remove Malwarebytes. Those are two separate and independent softwares.

Well you said that you have removed the ESET product from that computer and that you don't have any ESET product on your server either. So do you or don't you have some ESET product installed? Could it be that the sender uses our product and the message is inserted on their side when sending the email?

Hi, Today we released ESET Smart Security 9 and ESET NOD32 Antivirus 9 in Slovak, Czech and German languages. The rest of the languages (including English) should follow in the coming weeks.

Hi, Today we released ESET Smart Security 9 and ESET NOD32 Antivirus 9 in Slovak, Czech and German languages. The rest of the languages (including English) should follow in the coming weeks.

Hi, in the case the number changes, we recommend to add an exclusion based on the process accessing (such as a back-up tool), rather than the path.

In case there is a specific file mentioned in the error message and there is no access to it, it is usually due to a faulty disk, or a corrupted installation. It is interesting that it is present on all your computers. Is the number of the computers large? Would it be possible to remove the installation manually and then reinstall?

Hi, Please have a look at this thread: https://forum.eset.com/topic/6033-windows-10-forget-folder-view-setting-when-ess-is-installed/ We released a new version of our cleaner module (v1113), please check whether it resolves the issue.

Sorry for the confusion, I did not mean upgrading to v6, but to use the latest build of the v5, as version 5.0.2228 is not the latest one. However, as you have already removed our product and the issue still persists, I believe it is not caused by ESET product.

Hi, What browser do you use? Does the issue still occur after reloading the page using the Ctrl+F5 shortcut?

Hi, The release is planned to correlate to the El Capitan release so that the users experience no incompatibility issues.

Is there anything in the server log, or in the Agent's trace log regarding this issue?

Hi, If you do not wish to have this scan run after the updates, go to Tools > Scheduler and untick the Startup scan which is scheduled to run after a successful VSD update. However, please note that you will make your PC slightly less protected by doing so, as the critical files your PC uses won't be checked against the newest threats as often. Additionaly, as pavilion_alex suggested, please create separate threads for different questions, so that there is some order to what is where and so that other visitors of this forum can easily find the topics categorized as well.

Hello fanar, We do not distribute the links to the older versions of ERA as we want our users to always use the most updated version of our products, since those contain fixes of previously found bugs. If you experience issues with the current version, please contact our support department so that they can help you resolve them, or so that we can fix the issues in a next build.

Hello Keynan, When the update works, you need to make sure the SysInspector module updated to version 1254. Then, upon the next initialization of our antivirus, the problem will be gone.