Unable to keep file scanned from the Automatic startup check

Discussion in 'ESET Smart Security' started by Galaxykiss, Sep 15, 2011.

Thread Status:
Not open for further replies.
  1. Galaxykiss

    Galaxykiss Registered Member

    Joined:
    Mar 23, 2007
    Posts:
    167
    Location:
    China
    Log first, talk later:
    2011/9/15 22:40:58 Startup scanner file C:\Windows\kmsem\KMService.exe a variant of Win32/HackKMS.A potentially unwanted application unable to clean

    Yes. it is something. but I can't let it go because my os, you know.....:cool:

    I already put it into the Exclusions box in ess5. why does eset alert every time it do the Automatic startup check?

    How to exclude it forerver?
     
  2. MattJN

    MattJN Former ESET Support Rep

    Joined:
    Feb 19, 2010
    Posts:
    149
    Hello,

    The automatic startup file check is an inclusive system and does not reference the exclusions list. It appears to me that the KMService.exe process is starting up when the machine starts and logs in. You might try disabling that startup item and see if the detections remain each time you log in.

    Further, if you have a sample of this file, we would like to analyze it in our lab to see if it is a legitimate infection. Please see this KB on how to submit a sample to us.

    Thanks,

    Matt
     
  3. Galaxykiss

    Galaxykiss Registered Member

    Joined:
    Mar 23, 2007
    Posts:
    167
    Location:
    China
    Dear Matt,

    This file has been sent to your lab every time when EAV found it.

    I use this file for maintaining the activation of windows 7 as a service starts at the log in.

    not many vendor treat it as a bad program but it will be much better if you can setup a exclusion box for startup scan.

    Regards.

    Galaxy
     
Thread Status:
Not open for further replies.