OEC GROUP IT

Well, what file would be failing to be renamed on an update? ESET is the one who programs these errors into the software. It would be helpful for a technician working on a computer with this error to have more information from the software. What is the location of the file(s) that gets renamed on update? Please advise.

I've pushed out the update for endpoint antivirus 6.6.2052.0 and issue is still present from the previous update. When receiving this error, does it mean the computer's virus db definitions are not being updated? Is there any solution to this error? I receive a number of ESET error emails everyday from the same computers.

Absolutely, I will open a case. Thank you!

I tried doing this but receive error: When installing through ESET Remote Administrator, I see error in event viewer: "Product: ESET Endpoint Antivirus -- Error 1920. Service 'ESET Service' (ekrn) failed to start. Verify that you have sufficient privileges to start system services." When running MSI on the computer: Service 'ESET Service' (ekrn) failed to start. Verify that you have sufficient privelages to start system services. The installation begins but gets stuck at starting the ESET service.

I've successfully upgraded almost all the computers in my office to the new version of ESET Endpoint Antivirus version 6.6.2046.0 with no issue by deployment with the MSI installer from ESET's website by using Admin Arsenal PDQ Deploy for deployment. However, there are currently 2 computers that I am unable to install the new version on. The system logs in event viewer in computer management on them are showing error as follows: "Product: ESET Endpoint Antivirus -- Error 1923. Service 'ESET Service' (ekrn) could not be installed. Verify that you have sufficient privileges to install system services." The computers completely uninstalled ESET Endpoint Antivirus version 6.5.2107.1 on upgrade and left the computer unable to reinstall or upgrade as the service "ESET Service" or ekrn is left behind and cannot be stopped or reinstalled. On the affected computers, the following is what I've tried as well as the results: - Deleted ESET service ekrn in regedit. After doing so, I'm able to reinstall 6.5, then do an uninstall through appwiz.cpl of ESET to get a clean uninstall of the software. After, I've tried installed version 6.6 and there is still an error 1923. - I've also tried removing the software using ESET Remote Administrator by removing ESET Remote Agent and ESET Endpoint Antivirus and redeploying the newest version, but still receive the same error 1923. - I've also tried using the ESET removal tool provided on https://support.eset.com/kb146/?locale=en_US then reinstalled with no luck on the new version. Both computers are on Windows 10, one on patch level 10.0.14393.1593, and the other on 10.0.15063.540. I have a few other offices to upgrade the software on, so I'd like to be prepared with a solution should it come up again. Any help would be greatly appreciated.

Does anyone have any input on this at all???

At the company I work at, we use ESET to shut down all of our computers everyday at 10PM through the use of a scheduled client task through ESET Remote Administrator (Server), Version 6.3.136.0 with ESET Endpoint Antivirus version 6.3.2016.0 for an on demand scan and shut down after the scan. Attached are the trigger settings for: Daily Start: (schedule begin date) 22:00:00 End: no end Schedule: every 1 days Invoke ASAP if Event missed: NO Use Local Time: Yes The problem is that we have had a few cases where every day, the scan won't start until 10AM the day after and shutdown the computer. If a user is away from their desk, this is a huge problem because they lose all of their work. There is an option to cancel the shutdown, but there's only about a 10 second window to cancel. From checking the logs of when the task is actually running, on these computers facing this issue, the task is showing successfully ran at 10AM. I've looked around just about everywhere I can think of as to why this may be happening but I cannot find a thing. - The task is running based on the local server's time and the computer's time is synced from the server's time. - I've doubled checked the computers' time and it is definitely not set to PM when it's actually AM time and visa versa. - Invoke ASAP if event missed is not checked in the task. - There are no left over tasks to be ran if missed. - I've uninstalled both ESET and ERA remote agent from one of the affected computers as well as deleted the host name in ESET remote administrator. - Completely recreated the scheduled client task - There are no locally scheduled tasks on the computer to scan with option to shut down after scan - Within ESET antivirus on the computer, the "Action after Scan" is set to "No Action" - The applied Antivirus and Remote Agent policy has no set action to shut down after on demand scans and the policy is applied to 270 other computers that are not experiencing this issue - There are no scheduled tasks created through windows to shutdown the computer - The system logs show that the shutdown is triggered by ESET I am flat out of ideas. The only thing that prevents this from happening is disabling the client task on the affected computers so it's definitely an issue with the scheduled client task through ERA. But why only a few select computers??? Can someone please give some insight as to what could be causing this?