Large EXE files

Discussion in 'ESET NOD32 Antivirus' started by elmolincoln, Jan 11, 2010.

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

    elmolincoln Registered Member

    Joined:
    Sep 14, 2009
    Posts:
    16
    Does anyone have any recommendations for configuring NOD32 to more efficiently handle VERY large EXE files? We have several situations that require very large executables. The first is the distribution of Autocad 2010 comes in a 1.3 to 1.5 executable file. These extract into a directory structure for installations. Second, our own application that we develop for telephone companies is growing rapidly with all the Microsoft Redistributables in it (Framework 3.5 and SQL Express (x86 and x64)). Those will grow to 400-500meg and extract into an structure for installation also.

    We have run into this type of situation before and I have gone into the policy manager and configured it NOT to scan files on OPEN. That has seemed to resolve it until now. If we rename a 1.5gig to something other than EXE, nod32 seems to ignore it and we can copy it in a timely fashion. If it is an EXE it is painfully slow when the file is the x64 installation. Any ideas or recommendations?

    Anything would be much appreciated.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Try setting a size limit for archives (ie. to 50 MB or less). However, you should understand that any possible malware in large sfx archives will not be detected.
     
  3. elmolincoln

    elmolincoln Registered Member

    Joined:
    Sep 14, 2009
    Posts:
    16
    we would have to rely on real-time detection (upon execution) correct? We are creating most of the files (contents are already scanned) and I would look to apply this type of policy to just a few of the machines that are impacted only.
     
Thread Status:
Not open for further replies.