Jump to content

metranscz

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by metranscz

  1. @itman thansk for your suggestion. I already applied the suggested configuration since 2021/03/29 and it seems to prevent the high ekrn.exe writing to the disk. I believe, that the reported issue is solved.
  2. @Marcos In the documentation on the https://help.eset.com/ees/7/en-US/idh_config_kernel.html is explained how this option works, but in my case, the I/O write operation happened during logged user usual work. An efficient increase was during the night when the user machine was in the "lock screen" state, then "idle scan" should expectedly scan these computers, which is not explained the behavior when the user is logged in and do his usual work. The idle scan was written to the disk hundreds of GB per day. In the case when I did disable this option, the write operation does to a normal state (a few MB per day). This happened on many computers with centralized management. Then the main question is how to configure the machine settings to avoid options like "idle scan" but still have a feature, scanning the computer, when is the low machine utilization. It seems to be an impossible challenge, but I hope for some solution.
  3. Hello all, I tried to disable "idle scan" in the configuration option and it seems to be a solution for this behavior. After that, the I/O write operation goes under control and it's written among MB per day, not GB as before. Thansk for your help with investigation, special thanks for @itman, which mention "idle scan" in his first clue. Have you any suggestion for ESET configuration which can replace "idle scan"?
  4. Hello Marcos, it is very odd, have you any suggestions for ESET settings? Could you please explain how can couse explorer.exe significant I/O write operation for ekrn.exe which I posted here from the Task Manager? Were in log collections any differences with and without the Idle check option? Thanks in advance for your reply.
  5. Hello Marcos, I did the second log collection without the idle-scan option. I noticed that the process I / O were circumstances different from those present when the Firefox Web browser is presented on the machine. ie. 91 GB per night with Firefox and 17 GB per night with Chrome, otherwise the I/O are still out of control.
  6. Hi, Our Eset current version is 8.0.2028.0 And yes, the Idle scan option is Enabled. It does this high I/O across many computers in any time. @Marcos I´ll provide the download link for the .zip log collection and hide the answer, will be this option secured, to prevent public reading? It is 480MB. Yes, the esetperf.etl was generated.
  7. Hello, I´m facing today with extremely high ekrn.exe I/O write operation, even if Windows10 machine uptime is around 5 hours. Could someone help me diagnose this issue which is mentioned in a similar closed Topic (https://forum.eset.com/topic/26339-eset-extremely-high-disk-usage-from-ekrnexe-at-windows-startup/) I have ready esetlogcollector .zip output and I´m appending here a few PrintScreens. Thanks for any hit.
×
×
  • Create New...