Jump to content

Disable/Enable Eset through command Prompt


jgillen

Recommended Posts

I'm hoping someone can help me out with this.  We are having issues with ESET capping out our CPU usage during speed tests over the internet.  This is preventing us from getting accurate results to provide our ISP customers during troubleshooting and installs.  I was wondering if there was a way to use command prompt to disable ESET and all of its functions for the speed test and then enable it after the speed test.  We run ConnectWise Automate on our machines and I was hoping for this option so I can create a script for it and make it a button to press for our technicians out in the field.  Does anyone know if there is a command line to accomplish this, or perhaps a different solution that would accomplish the same thing?

Link to comment
Share on other sites

  • Administrators

You can pause protection but only remotely from the ESET PROTECT console using a Run command task as per the instructions at https://help.eset.com/ees/10.1/en-US/idh_config_ecmd.html.

Instead of that, I'd recommend trying to find the root cause. Please carry on as follows:

  1. When the issue occurs, enable advanced operating system logging under Tools -> Diagnostics -> Advanced logging in the advanced setup
  2. After 30-60s stop logging
  3. Collect logs with ESET Log Collector and upload the generated archive to a safe location (e.g. OneDrive, Dropbox,...) and drop me a personal message with a download link.

 

Link to comment
Share on other sites

I'll see if I can get some log files for you.  We are able to get 1Gbps when ESET is uninstalled on a computer, but when it is installed, we can only get about 400 Mbps.  We did some testing on several different machines, and it seemed that ESET was maxing out the CPU during every Speed Test giving us inaccurate results. We were able to replicate this on every machine we tested on.

Link to comment
Share on other sites

We ran Speedtest.net and Fast.com for our speedtests.  We would do an uninstall of ESET and run the speed tests and then do a reinstall and run the speed tests again. We noticed CPU usage through ESET would jump during those times causing a limit on the speedtest results due to hardware usage. We were running Dell E7470s with i7 processor and 16 GB of RAM with 512 GB m.2 NVMe.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...