Zoltan Endresz

Dear ESET experts, It seems the manual uninstallation in Windiows 10 safe mode works on remote computers also. Unfortunately it takes a lot of time and have to get permission from the colleagues from an another time zone and so on - not so funny on several dozen of problematic clients. My question vould be, which is the problematic component of the three new - see upper. Is there any info concerning this matter? Maybe do you plan to fix this issue by a new software release?

Sorry Marcos, we are talking about remote computers, so it is not possible to fix them on the known Restart safe mode > Start the uninstaller > Restart in normal mode > Reinstall the ESET way, as we can read it on the manual called [KB2289] Uninstall ESET manually using the ESET uninstaller. I did it on the past a lot of times on Windows 7 but I was never able to do it on Windows 10. My available remote managemet tools are the following: - Remote Desktop (mstsc) - Funk Proxy Master - TeamViewer The affected cca 90 computers with failed update are for example in Mexico, USA, Italy and so on. Unfortunately three changes were happened in nearly same time: - ESET Security Management Console updgrade to 7.1 - ESET Management Agent update from 7.0 to 7.1 - ESET Endpoint Security update from 7.1 to 7.2 I'm affraid to touch the system because I does not have idee which component cause the problem and do not want to increase the number of the problematic clients. Approximately 1600 further clients are waiting for the update in our enviroment.

Hello TomPark, Here are the files. Thank you for your efforts in advance. As additional information, the update finished successfully on 1879 computers but failed on cca. 85. Best regards install.log setupapi.dev.log setupapi.setup.log

Hello Marcos, Thank you for your quick repy. I tried to upgrade mostly the version 7.1.2045.5 and maybe a few 7.0.2100.4. Additional information: On 2th of January the ESMC server and webconsole was upgraded to the latest version: ESET Security Management Center (Server), Version 7.1 (7.1.717.0) ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0) I started the bulk update on the endpoints after a few days. It finished successfully on 1870 computers and unsuccessfully on cca. 85 clients. I feel maybe the problem is exist since the ESMC upgrade. Best regards Zoltan

Dear ESET Experts, I'm currently working on the update of our computers to the latest version of ESET Endpoint Security v 7.2.2055.0. Unfortunately it seems the update failed on a lot of computers with the following error message: SoftwareInstallation: Installation failed with: (0x643), Fatal error during installation (0x643), The older version of ESET Endpoint Security cannot be removed. The affected computers are in many countries such as Germany, USA, China etc, therefore the uninstall via the ESET Uninstall tool in safe mode is not possible bacause the more than 110 affected clients worldwide. Sadly this number seems to be inrcreasing. Could you please recommend a solution? Thank you in avance.

Hello Again, So sorry, I have to correct my previous note. The problem was solved correctly just by the latest version EES 7.0.2100.4 . The other EES 7.0.x version were buggy - as I see from my point of view.

Hello All, For your information, it seems my update problem is solved - see upper. Shortly, I had update issues on the following configuration: - ESET File Security 6.5.12017.0 on the server side + ERAA 6.5.522.0 + EES 7.0.x on the client side The issues disappeared by the server upgrade to version 7.0: - ESET File Security 7.0.12016.0 on the server side + EMA 7.0.577.0 + EES 7.0.x on the client side So, maybe it is not the best idea to test the 7.x version EES software on 6.5 server version server enviroment. I hope I helped.

Hi All, I have same issue. I installed the ESEt Endpoint Security v.7.0.2091.0 for testing on a few computers, but the Detection Engine does not update. The ESET icon spinning and send message: "Module update in progress" continously wihout any results. ERAS and ERAA are v. 6.5.5.22.0 We plan the ERAS update shortly to v. 7.0 but maybe it is not so good idea yet - until I'm not sure that the new version will work properly.

Try the configuration below, this works fine:

Ooops, indeed. I'm so sorry MartinK, I was careless during the task creation process. Thank you for your update.

All right, then I will try to describe it. My problem is that I see many computers with outdated ERAA version and few another with suspicious phenomens. For exaple please check the screenshot below. The ERAA is outdated on the affected computer. I ran a few Update Modules task for install the latest version. The feedback is "Task finished successfully", the process bar turned to green, but the installed ERAA still remain the expired version. Based on my experiences on the same cases the only one chance to fix these issues to log on the affected clients remotely, reboot it in safe mode, start the ESET uninstaller tool and reinstall the ERAA. This is a really painful proces to do it from Europe on a Chinese or Mexican client. This is the reason because I started experiments and tried to use the built in ESET ERAA uninstall tasks and possibilities. Unfortunately it does not help because the installed (probably damaged or corrupted) ERAA still remain exist on them. That's why I opened this new topic.

Dear ESET Staff, Based on my experience unfortunately sometimes it is neccesary to reinstall the ESET Remote Administrator Agent on a far away computer. We use a Group policy which check that the ESET Remote Administrator Agent service running on the affected computers or not. If not, the ERAA installation start automatically. I tested the following idea, for fix the damaged ERAA: 1.: Start a Uninstall ERAA task via the ERAC 2.: It works fine, I lost the connection with the client 3.: I deleted the client from the ERAC 4.: Theoratically the Group Policy upper should reinstall the ERAA, but does not appear into the client. Could you please help me?

Description: Improved Dynamic Group Templates possibilities Details: It would be useful a possibilities during the Dynamic Group Template creation a "but not" option. For example: "Security risk" but not "A computer restart is required" and not "Virus signature database is out of date". An another solution would be a radio button field for choose the interesting and unnecesary warning/error messages. For better understanding, I see a lot of "red" computers in my console because the reasons upper, but most of them are inactive for a couple of weeks. These clients will turn to "green" state shortly when they will connect to the network again. With the improved dynamic group options I would be able to define a group for check the really ineteresting issues.

Description: Trigger tasks based a definied activity time frame Details: Maybe it would be useful a possibilities to create tasks for a group of computers wich were active in a specifield time frame. For example "if they were not active during on the last two weeks" or "if they are active at the moment". Description: Delete the duplicated computers automatically Details: Day by day I find "duplicated" computers on the system. I created a report to find these computers (Group by: Computer name and Count: Computer), then time to time I delete the older entryes. It is a bit confusing. Description: Make a task chain Details: It would be wonderful a new possibility to make a task chain. For example: Task 1: Update the EES Task 2: Trigger a pop-up window on the affected client (Please restart your computer or Your computer will restart in 60 minutes) Task 3: Wait 60 minutes Task 4: Restart the client

Hi ScotWStewart, I mean the ESET is corrupted or damaged on the affected computer. In same cases usually I reinstall the EES. Please try the following: - Check the following link: https://support.eset.com/kb2289/?locale=en_US - Download the special remover tool from the ESET from the link upper - Copy it into the affected computer - Start the client in Safe Mode (msconfig > restart in safe mode ...etc ) - Start the uninstaller tool and follow the instructions, choose the ESET component, etc... - Restart the client in normal mode - Reinstall the ESET packages (For example the ESET Endpoint Security) The trickly phase will start, if you want to use this walktrough on a remote computer, for example from an another country or subsidiary. Unfortunately the remote session will terminate on the 50% of the cases - you lost the connection but the client running with your credentials. But it is an another story. (The solution: trigger a timed restart process (cmd > shutdown /r /t 120) ) I would be very happy for an another repair method, but I don't know either. I hope I helped

Hello! I tested the new EES v6.5 and I can confirm the problem. All of the 17 computers started to work terrible slow. I did a rollback on them to the EES v6.4, then the problem disappeard.