Failed to delete Medfos Trojan

Discussion in 'ESET Smart Security' started by smseifi, Jul 26, 2012.

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

    smseifi Registered Member

    Joined:
    Jul 26, 2012
    Posts:
    2
    Location:
    USA
    Hi,

    Recently I faced with this issue that ESET unable to delete medfos.AU Trojan and when I hit the delete button an error will come up says error while deleting.

    Any advise in this regard would be appreciated.

    Thanks,
     
  2. smseifi

    smseifi Registered Member

    Joined:
    Jul 26, 2012
    Posts:
    2
    Location:
    USA
    For completeness:

    - version and platform of the operating system: Windows 7, 64bit

    - the name of the ESET product: ESET Smart Security 4.2.76.0

    - information about installed ESET modules:
    Virus signature database: 7332 (20120726)
    Update module: 1040 (20120313)
    Antivirus and antispyware scanner module: 1365 (20120724)
    Advanced heuristics module: 1121 (2011120:cool:
    Archive support module: 1147 (20120620)
    Cleaner module: 1057 (20120626)
    Anti-Stealth support module: 1031 (20120613)
    Personal firewall module: 1082 (20120515)
    Antispam module: 1022 (20120601)
    ESET SysInspector module: 1225 (20120629)
    Self-defense support module: 1018 (20100812)
    Real-time file system protection module: 1006 (20110921)
     
  3. dwomack

    dwomack Eset Staff Account

    Joined:
    Mar 2, 2011
    Posts:
    588
    It would definitely be a good idea to contact ESET Technical Support either by phone or email to get help cleaning medfos.AU from your system.

    In the meantime, you can also check out this KB Article.
     
  4. hogndog

    hogndog Registered Member

    Joined:
    Jun 9, 2007
    Posts:
    628
    Location:
    In His Service
    dwomack is right you need to get in touch with support, the Trojan you have is a nasty one..
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Perhaps we could help better if we knew if it was a detection in memory or if a file was detected. At any rate, it'd be good to enclose a complete log record containing the full path and the detection name when reporting an issue with cleaning.
     
Thread Status:
Not open for further replies.