Peter Randziak

Hello, we were able to find the root cause of the issue and the Dev team already proposed a solution. It should be available tomorrow via automatic updates, restart of system will be needed. We know that this bug may be annoying, but we always concentrate our efforts to ensure maximal protection of our users. This particular bug is not lowering the security in any way as far as the updates are downloaded and applied on the background so the full protection is ensured. Thank you for understanding.

Hello Zardoc, we have it already reported and discussed here.

Hello Zuku, you could push preconfigured package utilizing Remote install feature as described here. Or you could install a preconfigured installation package locally instead of a push install as described here. "Double-click the file to execute the installation. We recommend that you perform a silent install with a suppressed restart (see the switch used in the example below) if you do not want to be prompted during the installation. For example: "C:\Documents and Settings\eset\Desktop\eset_endpoint_security.msi" /qn REBOOT="ReallySuppress" "

Hello Mantra, it is always a good idea to backup your settings especially if you have customized them a lot. The upgrade from version 5 to version 6 is fully supported so you can do it directly, settings should be preserved after upgrade.

Hello SyRenity, as far as you were installing in this way "We did the deployment by uploading the MSI to Amazon S3 and giving people a link" I assume that the users have administrative rights. The easiest solution is to create configuration .xml and send it to users for import of settings with steps how to do it: 1. Download the configuration file 2. Open your ESET Endpoint Security 3. Select setup -> Import and export settings -> select Import settings -> browse the configuration file -> select open and confirm by OK P.S. I would recommend you to protect the settings by password as the users shouldn't be able to change them.

That's good that you were able to fix it. Thank you for sharing the solution with us.

Hello, ESET USSD Control is just simple utility, which was quickly developed in order to prevent exploiting of USSD feature on some Android based devices. This issue was specific for Android OS so there would be no use for it on Windows 8 phone.

Hello LockenetSSmith, ESET Mobile Security for Android v.2 is only in home edition now so managing it by means of ERA is not supported yet. The version for home segment is always developed and released before the business edition. The development team is already working on ESET Mobile Security for Android business edition, but it will take time to develop, test and release it.

Hello, the described steps are meant to get log files, which could help us to find the cause of the issue, they are not meant to fix it immediately.

Hello Marilyn, For the Windows OS I would recommend ESET Smart Security and for Mac OS ESET Cyber Security Pro. More information can be found here. Regarding the licensing you can find info here, in your case answer to question 13 is applicable: Q: I have multiple operating systems running simultaneously using virtual machine software such as VMWare, Citrix or Parallels — how many licenses do I need? A: In situations where the operating systems are running simultaneously, one license per virtual machine is required.

Hello Duluc, it does not affect detection so computers are fully protected. I have this issue on one of my VM and it downloads updates on the background so I have most up to date version of virus signatures 8707 You could check easily which version you have right now, and compare it with version available on update servers here.

Hello, thank you for the information. Could you please share the solution with us when it will be available?

Hello Zardoc, we tried it with Windows 8x64 as well and we were able to install the software successfully. So it is probably caused by some system configuration.

Hello Rpremuz, could you please try to do steps described in this KB article: Windows Security Center is not detecting my Windows ESET security product

Hello Giro360, have you followed the instructions, which I described on 12. of August in this thread?

Hello, could you please run the update manually wait for a while (2 minutes should be enough) and than submit customer care form (directly from the application) with reference to this thread for further investigation. Thank you.

Hello, we are aware of this and we are troubleshooting the issueright now. We will let you know as soon as we find something out.

Hello, You could accomplish this using a HIPS rule. I've included steps to do this in ERA and Endpoint Security/Antivirus below: ERA: open Configuration Editor and expand Windows desktop > V5 > HIPS > Settings > Rules and advanced options. Click Edit to open the HIPS system settings management window and then click New. Type a name for your rule into the Name field and select Block from the Action drop-down menu. Click Add in the Target applications window, select "Start new application" operation, click Add, navigate to the .exe file for the application that you want to block and then click Open. Click OK to close the Add application path dialog and you should see the file displayed in the Source applications window. Click OK to close the Edit rule window. Your client workstations will receive the new rule the next time that they check in to ERA. Endpoint Security/Antivirus: Press F5 to open Advanced setup. Expand Computer > HIPS. Click Configure rules to open the HIPS system settings management window. Click New. Type a name for your rule into the Name field and select Block from the Action drop-down menu. Click Add in the Target applications window, select "Start new application" operation, click Add, navigate to the .exe file for the application that you want to block and then click Open. Click OK to close the Add application path dialog and you should see the file displayed in the Over these applications window. Click OK to close the Edit rule window. Your new rules will be applied immediately on this client workstation. You can apply this setting though ERA even though the application is not installed on the same server as ERA. The information is stored in the configuration .xml file.

Hello Rjch, thank you for sharing the trick with us.

Hello LocknetSSmith, we are working on the support, but the release date is not determined yet. It is the very next product we plan to support in the MSP system. So stay tuned for the news.

Hello Rjch, clear the mirror folder, update cache and windows temp again. Does switching to pre-release updates make any difference? Which update server do you have selected? Is the server connected via proxy server?

Hello Gavin, you could get more info by running ecls.exe with "--help" option so run "ecls.exe --help" Exit codes are following: 0 no threat found 1 threat found and cleaned 10 some files could not be scanned (may be threats) 50 threat found 100 error

Hello Tom Wicker, I am really sorry that you have such negative experience, but we already have a solution. After replacing the binaries nobody had the issue again. Finding a solution may be extremely difficult in such circumstances as far as we were not able to reproduce the issue in-house although we were trying hard to do so. Could you please do the stems that I described earlier in this thread and share the results with us? Thank you very much for cooperation.

Hello Winston, it is not 100% clear to me. So does the issue persist or not after compacting the database?

Hello, so you probably use local mirror to update clients. I would recommend you to delete contents of the mirror and update cache (can be deleted via "clear update cache" option) and let the mirror be created from the scratch. Has this resolved your issue?