Folders to exclude from scan

Discussion in 'NOD32 version 2 Forum' started by screamer, May 5, 2007.

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

    screamer Registered Member

    Joined:
    Apr 14, 2006
    Posts:
    921
    Location:
    Big Apple USA
    I have NOD scheduled set to scan my box on Mon, Wed & Fri, while I sleep.
    I've excluded /$ISR since the scan would take forever if I scanned this folder: FD-ISR has a daily (revolving) snapshot of my drive for the last 4 days. If I do find something on my E: Drive I can always go to the corresponding FD-ISR folder and handle the situation.

    My question is: What "other" folders can I safely exclude from the scan?
    My Documents, My Pictures...

    ...screamer
     
  2. ASpace

    ASpace Guest

    You cannot exclude any files/folders for your on-demand scans.I do believe you should also not scan so often (3 times per week is really a lot) . Don't forget that NOD32 has real-time protection (AMON,DMON,EMON,IMON) which will not allow malware run in the memory and will keep a computer clean .

    I suggest you scan two times per month (in Scheduled scan - every 336 hours or so).
     
  3. screamer

    screamer Registered Member

    Joined:
    Apr 14, 2006
    Posts:
    921
    Location:
    Big Apple USA
    Sure you can exclude files from on-demand scans:

    E:\ /adware /ah /all /antistealth+ /arch+ /clean /cleanmode /delete /heur+ /log+ /mailbox+ /ntfs+ /pack+ /quarantine /scanboot+ /scanmbr+ /scanmem+ /scroll+ /sfx+ /unsafe /unwanted /wrap+ /exclude=$ISR /quit+
    Point well taken. I -do do alot of high risk surfing though.

    I really miss the point here. Then why are scans necessary if NOD will prevent harmful files from executing?

    ...screamero_O
     
  4. ASpace

    ASpace Guest



    The real-time protection will eliminate all malware try tries to load in memory(1)
    The on-demand scan will also scan for not loaded in memory threats (e.g. in archives) (2)

    (1) is the most important . I still believe that scanning 3 times per week is very much but the final decision is always yours :p
     
  5. screamer

    screamer Registered Member

    Joined:
    Apr 14, 2006
    Posts:
    921
    Location:
    Big Apple USA
    I do plan on cutting back my scans to perhaps twice monthly.

    Now back to the original question: What (existing) folders can be safely excluded from a scan?

    Since My docs has been scanned "many times" is it safe to exclude it? Same w/ My Pics, My Videos. Also Downloaded program files have been scanned umpteen times. Is it safe to exclude them?

    ...screamer
     
  6. ASpace

    ASpace Guest

    All folders/files you wish/find appropriate can be excluded (e.g. My Documents,My music ...)

    But excluding MyDocuments ,for example , will not affect much the total scanning time . Generally files/folders are excluded because of compatibility issues. :thumb:
     
  7. screamer

    screamer Registered Member

    Joined:
    Apr 14, 2006
    Posts:
    921
    Location:
    Big Apple USA
    I have no compatibility issues :) But my question was geared to: Is it "safe" to exclude My Docs... since they've already been scanned so many times?

    Part Two: How likely is it that an existing file (whether it be a .doc, .xls, .jpg...) will / can be infected? If so, how does it become infected?

    I know enough to scan any new / downloaded files prior to opening / executing.

    ...screamer
     
  8. ASpace

    ASpace Guest

    Shortly : YES , it is safe .But there is no point because generally people store just docs in MyDocuments and they are not big files , thus scanning it will be fast .

    By a virus.You can get viruses from internet files/external media (CDs,DVDs,USB flash,floppy disks ...) . You are well protected by NOD32.

    That is what the real-time protection (AMON and IMON) does :D . Really .
    Read more here http://www.eset.com/products/ at the bottom
     
  9. screamer

    screamer Registered Member

    Joined:
    Apr 14, 2006
    Posts:
    921
    Location:
    Big Apple USA
    Thanks ! :)
     
  10. ASpace

    ASpace Guest

    You are welcome ! :thumb: Enjoy your Eset NOD32 !
     
  11. WWS

    WWS Registered Member

    Joined:
    Jul 13, 2004
    Posts:
    249
    There's a way to exclude files by deselecting all disks and adding in just the files you want to scan.
    It takes me about 88 minutes to scan my primary and 3 $ISR snaps (about 40 GB). Otherwise it takes me about 22 minutes to scan just the primary (about 10GB).

    see this:
    https://www.wilderssecurity.com/showthread.php?t=157432
     
  12. JohnFL

    JohnFL Registered Member

    Joined:
    Apr 30, 2007
    Posts:
    6
    Being a new user to NOD32, i find that not being able to exlude certain files or folders ( without having to enter the folders that i do want to have scanned ), being a real pain in the you know what.

    I understand that i can put certain folders in the "Folders and Files" area, and then just have it scan those objects. But how do i have is scan the root directory of drive C?

    If i put C:\ down there, then it will scan every folder off of the root directory of C:

    Am i going to have to put every file that is in my root directory down in that area?

    Not a very user friendly way of doing business!
     
  13. JohnFL

    JohnFL Registered Member

    Joined:
    Apr 30, 2007
    Posts:
    6
    And as a follow up on my post up above.... Why can't a Drive be put in the bottom window, that would open up like a tree structure, so that you could easily mark which folders ( or files ), you want scanned, and which not to scan. This is done by many different types of programs, and it seems to me could be easily done in NOD32.
     
  14. JAB

    JAB Registered Member

    Joined:
    Apr 17, 2007
    Posts:
    36
    Honestly, I've never understood this either. It makes the NOD32 on-demand scanning unusable on domain controllers and Exchange servers.

    I've also never understood the argument that one shouldn't use on-demand scanning daily. There are only two possibilities: (1) It's never going to detect anything; (2) it will eventually detect something. If #1, then why have it at all? If #2, why should I artificially postpone the detection by days or weeks by scanning infrequently?

    /jab
     
  15. Joliet Jake

    Joliet Jake Registered Member

    Joined:
    Mar 1, 2005
    Posts:
    911
    Location:
    Scotland
    Scanning every other day as opposed to twice a month must be an extra power of work for a hard drive. Over the course of a couple of years this will add up. If something infected is in an archive it can't harm you until it tries to run and even then NOD can halt it.
     
  16. JAB

    JAB Registered Member

    Joined:
    Apr 17, 2007
    Posts:
    36
    The extra wear and tear on the hard disk is irrelevant in general, especially given the state of hard disk technology these days.

    If my organization has been penetrated before NOD could detect the infection and that infection has since gone dormant, I want to know about it the day NOD is capable of detecting that dormant malware, not 13 days later. The fact of the matter is that detectable dormant malware on a server will tend to indicate undetectable, active malware.

    There is no meaningful detriment to scanning daily. There is arguable benefit to doing so. The fact that NOD does not enable daily scanning of servers because it doesn't allow file and folder exclusions for on-demand scans would be inconceivable, if it weren't demonstrably true.

    /jab
     
Thread Status:
Not open for further replies.