NOD32 on demand scanner issue

Discussion in 'ESET NOD32 Antivirus' started by tpm4, Apr 24, 2010.

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

    tpm4 Registered Member

    Joined:
    Apr 24, 2010
    Posts:
    4
    Ordinarily, a complete on-demand scan of my system will scan
    approximately 335000 items and take roughly 50 minutes to complete.
    After initiating a case with ESET support over a possible infection,
    I was requested to run a scan with an application called "combofix".
    which I did as per instructions.
    After running this "combofix" scan, I find that my on-demand scanner
    is functioning differently.
    With NO changes to my NOD32 AV configuration and NO changes to
    my system configuration (except for having to install the Windows
    recovery console to perform the combifix scan) and NO programs
    or files deleted, uninstalled or modified, a full on-demand scan now
    will only scan approximately 110000 items and take around 26 minutes.
    Can someone tell me exactly what would cause such a change in the
    way my NOD32 on demand scanner would function (I reiterate that NO
    changes were made to my system or any program/application on it
    except the Windows recovery console) and how to restore this
    program function to the state that I think it should function as?




    Windows XP sp3
    NOD32 v. 4.2.40
     
  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    did combofix find any malware and fixed it?
     
  3. tpm4

    tpm4 Registered Member

    Joined:
    Apr 24, 2010
    Posts:
    4
    Combofix did not cleanse, delete or take any actions against any files
    according to what I saw in the log.
     
  4. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    run this under command prompt
    dir /s /b C:\ |find /c "\"

    it will tell you how many files are on the C: drive (110,000 sounds roughly right). However, AV will count and files within archives too
     
  5. tpm4

    tpm4 Registered Member

    Joined:
    Apr 24, 2010
    Posts:
    4

    That was the issue, the NOD32 on-demand scanner is no longer scanning
    files within archives. There is a message "decompression could not complete
    possible reasons: insufficient free memory or disk space, or a problem with temp folders" (this message will only appear when scanning a single folder,
    and not when I do a full system scan)

    I have 3327 mb physical memory,2627 mb free
    5216 mb swap space,4724 mb free
    8543 mb virtual memory,7352 mb free, and 351 gb
    of free disk space, so I'm assuming there is some issue
    with temp folders, but I have no idea what. I have never
    seen, let alone used any options to modify temp folder
    properties.
     
  6. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
  7. tpm4

    tpm4 Registered Member

    Joined:
    Apr 24, 2010
    Posts:
    4
    Thanks for your responses
    I saw that page earlier, the closest thing I have to that solution is to
    uncheck "read only" in folder properties (I don't recall ever checking
    "read only" to begin with) and hopefully that will solve the problem.
     
  8. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
Thread Status:
Not open for further replies.