Hijin25

Well I'm quite disappointed with ESET and all the antivirus in general, because nobody detected this problem, until the same people of Periform made it public. I wonder what confidence we can have in our security software when it does not check that the behavior of the programs is expected and only relies blindly on the certificates. The problem was active since August 15, and it was not until September 18 that ESET detected it and it was not even for an investigation of its own. And now it turns out that its only recommendation is to format the device, so ESET is not able to protect us from the back door that may or may not have left this Trojan.

Great news, hopefully do not delay too much, since it is a minor problem, but quite annoying.

That's exactly what I said.

According to the configuration of the update task, it should be executed every 60 minutes and if it can not be executed in that interval, run as soon as possible. The task is not executed after every restart or start as you point, it has never done so, I've been using eset for 10 years, the update task is executed during a restart if and only if the time since the last update search has exceeded the 60 minutes.

I guess they do not understand me. The problem is not that the program does not update, the problem is that the update task is executed when it should not do it and it does it poorly. I will illustrate it to see if they understand me. I start my PC at 7:00 AM , The program is updated without problems, then at 8:00 AM it is refreshed again as scheduled, but let's say I reboot my PC at 8:15 AM, in theory the update task should not run until 9: 00 Am, however after the restart the task is executed and remains working endlessly, as I have indicated.

Already reporting this error since May 20, https://forum.eset.com/topic/12040-another-error-in-ess-10/#comment-61618, is exactly the same error reported by NGR. And if nobody has presented problems with the new version has to be because they have not even heard of the update, since again the program is not updated automatically.

The error is even worse in version 10.1.219, previously appeared ocationally, now it is after each restart, it is sad to see how the quality of ESET has been lost since version 9.

And will you just upgrade from version 10.1.210.2 to we'll have to do it manually as the last time? Because I still see many Pcs with version 10.0.390.0.

Thank you for your attention, I regret the delay in responding. I think I've found the cause, audit errors appear during the full scan of Malwarebytes 2.2.1.1043.

I reported this error for a long time in ESS, appeared with version 10.1.210, although I am presented 2 or 3 times a week, but so far has not been paid attention by ESET.

I hope this is what they need. Audit.rar

Forgive my ignorance, how do I export the record to share it?

Excuse me, English is not my native language, I did not quite understand. What is it that I must share?

I have uploaded the file "em023_64.dll.raw" to Virustotal and notes that the digital signature was not verified. Https://www.virustotal.com/es/file/4a11c562321f74256b6ed5f8877bc1a0d3d80b4aaa2a61354a066e74a6bdec6/analysis/

Run the scandisk and found no errors. I forgot to mention that the audit information indicates that each error was repeated 6 times, 12 records in a 2 minute interval.

I have these audit error logs in the event viewer. Code integrity determined that the page hashes of an image file are invalid. The file could be incorrectly signed without page hashing or be corrupted due to an unauthorized modification. Invalid hashes could indicate a possible disk device error. File name: \ Device \ HarddiskVolume2 \ Program Files \ ESET \ ESET Smart Security \ Modules \ em023_64 \ 9584 \ em023_64.dll.raw Code integrity determined that the page hashes of an image file are invalid. The file could be incorrectly signed without page hashing or be corrupted due to an unauthorized modification. Invalid hashes could indicate a possible disk device error. File name: \ Device \ HarddiskVolume2 \ Program Files \ ESET \ ESET Smart Security \ Modules \ em023_64 \ 10375 \ em023_64.dll.raw What do they mean?

Thanks for the suggestion, but it turned out to be a bad idea. I did the indicated procedure but there was no change, and the worst thing is that after doing so the search did not stop after the restart, as before, I had to uninstall ESS.

Thank you, I will prove what it tells me as soon as it happens again, it usually takes two to three days to appear once it happens, and yesterday it was when it happened again.

I am still experiencing this problem with version 10.1.210.2, it does not occur in version 10.0.390. The program looks for virus signature updates outside the normal search range but without completing the process.

We have 5 pcs in the office still working with version 10.0.390. When will the product update arrive? Or do you have to waste several hours of work to keep up with a product you are supposed to upgrade only?

And people who do not visit this forum and have no idea that this update has come out? What about those people who trust that their antivirus, for which they paid a good sum of money, is working 100%. I hope that there really is no problem with the automatic update of the program because if not, this was my last license acquired after 10 years using the program, I had minor problems throughout this time but this would be serious.

Thank you for your attention. In fact, that is the correct way of executing the task, and if there is a restart of the PC in that 60-minute interval, the task should not be executed, but it does and during that unscheduled execution, it does not seem like that point going up And down, you only see the progress bar that does not advance.

Since updating to the latest version of ess 10, occasionally when I restart my PC the eset icon in the system tray shows that it is performing a virus signature update, but it never ends, in addition the execution of the task does not match with the time to be executed. I must restart the PC again to abandon the search and make it at the scheduled time. This problem occurs in my 2 PCs where I use ESS 10, one with Windows 7 64 bit and another with Windows 10 64 bit.

Thanks for your reply. Then there is no need to worry because there is no user information or date detection, right?

I occasionally review the list of active processes through the antivirus tools, and I see the system process detected without any information on the part of the program. This process was not listed in version 10.0.390 or earlier, recently appeared in version 10.1.204. Is it normal that there is no user information or date of detection?