Win32/CMDOW.143

Discussion in 'NOD32 version 2 Forum' started by utilman, Aug 6, 2006.

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

    utilman Registered Member

    Joined:
    Aug 6, 2006
    Posts:
    20
    Since a few days NOD doesn't let me copy the file CMDOW.exe any longer.
    It seems that eset added this file as Win32/CMDOW.143
    How can I fix this, or exclude this file since excluding it at AMON doesn't work?!
    Strange that eset added a perfectly legal file to their database o_O
     
  2. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    I would suggest it would be detected as a Tool or Potentially Dangerous Application (I see now that it is detected as 'Win32/CMDOW.143 application'), either of which would be correct based on the description here.

    If you wish to add an exclusion, you may need to exclude both the long full path and short full path since the AMON exclusions compare explicitly to the call.

    It does look like it could be a very useful admin utility though.

    Cheers :)
     
    Last edited: Aug 6, 2006
  3. pykko

    pykko Registered Member

    Joined:
    Apr 27, 2005
    Posts:
    2,236
    Location:
    Romania...and walking to heaven
    They've added it in version 1.1690 (20060803). U could use NOD32 user advice for excluding it. ;)
     
  4. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    For example...

    "long" path: C:\Documents and Settings\user\My Documents\cmdow.exe
    "short" path: C:\DOCUME~1\user\MYDOCU~1\cmdow.exe .

    If you are not sure how to get the "short" version, go to the Command Prompt and use the dir /x command.
     
Thread Status:
Not open for further replies.