Jump to content

Tatiana

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Tatiana

  1. Hi, 

    I've found the solution. In my case it worked with and older version of mysql, I don't know why but after  8.0.15.0 almost all updates of mysql have failed after made changes on my.ini file and it stuck at starting. 

    In this case you have to install mysql installer community 8.0.15.0 as the kb says, after that you stop the service and make the changes. Finally you restart the service, if it stucks  just restart the server and that's all

    Regards

  2. On 3/7/2019 at 4:01 PM, itman said:

    Personally, I don't believe this has anything to do with Eset detection but rather how CompuTrace is implemented on the devices. Here are a couple of discussions of this topic:

    https://www.bleepingcomputer.com/forums/t/522805/lenovo-thinkpad-t510-bios-computrace-by-absolute-software/

    https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/BIOS-option-to-quot-permanently-disable-quot-Computrace/td-p/104500

    Of note, its UEFI status:

     

    In fact most of the Lenovo machines, in the anti-theft module have the option to disable the Computrace module and it works well because I have tried these machines. But others like HP, which are the client's machines, do not. That's why I can not deactivate them there.
    The Lenovo machines with which I am testing have the module turned on and some are detected by ESET and others are not, taking into account that the scan and security options are active under the same conditions.

  3. 3 hours ago, Marcos said:

    This particular detection requires detection of potentially unsafe applications to be enabled which is disabled by default, however, since it covers legitimate tools that may be misused in the wrong hands for malicious purpose.

    All PC's what I'm talking about have turnered on the detection of potentially unsafe applications and some of them have the alert and the other ones don't

  4. I was doing tests because this has happened to us before with some clients. In all the tests I have done are computers with UEFI. For example a client has 1000 pcs and this happens in 50pcs, despite having the same configurations, in fact in my test environment I have machines where I enable the computrace and I have strict security options and I do not detect it and in others yes.

    For that reason I have the doubt

  5. I understand that ESET can not eliminate detection of the EFI / COMPUTRACE threat because it depends solely on the manufacturer of the machine, BIOS update or Absolute Software.
    The question is, Why on some machines does it detect it as a UEFI threat and on other machines it does not detect it even though it has it active? Could it be because ESET detected unusual connections or what other option could it be?

×
×
  • Create New...