Suspected bug since version 3758

Discussion in 'ESET NOD32 Antivirus' started by BTIsaac, Jan 13, 2009.

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

    BTIsaac Registered Member

    Joined:
    Jan 13, 2009
    Posts:
    46
    I know I should've posted this sooner.
    Ever since the signature database has been updated to version 3758, NOD32 has been giving me a large number of "unknown compression method" messages while scanning the firefox setup program I've been keeping around for the past several months, during an in depth scan. I tested it on a second setup program I downloaded yesterday, and got the same results, so I suspect Nod32 no longer recognizes the compression method it uses.
    This is a little frustrating at best, as I'm forced to put up with a really big wall of text every time I run an in depth scan.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Couldn't it be that you're using Vista with UAC enabled?
     
  3. BTIsaac

    BTIsaac Registered Member

    Joined:
    Jan 13, 2009
    Posts:
    46
    Darn. I knew I should've said this before.
    No, I'm using XP, and this is only occurring since the 3758 update, approximately 24 hours ago.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Actually, the package uses an unsupported compression method. After an update of the archive module, the package should be scanned fine.
     
  5. BTIsaac

    BTIsaac Registered Member

    Joined:
    Jan 13, 2009
    Posts:
    46
    Archive module?
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Yes. You can check its version in Help -> About. The current version is 1086
     
  7. BTIsaac

    BTIsaac Registered Member

    Joined:
    Jan 13, 2009
    Posts:
    46
    I see it. Only, it says 1077 with the date saying 2009/01/09, while the build version is 1219.
    Anyway, thanks for the info.
     
  8. BTIsaac

    BTIsaac Registered Member

    Joined:
    Jan 13, 2009
    Posts:
    46
    Just calling in to let you know, that the problem was indeed solved with the latest update. Thanks again.
     
Thread Status:
Not open for further replies.