NOD 4.2.58.3 web protection @ WIN 7 64bit prevents dl/installation of Safari update

using the Apple Software Update 2.1.1.116 to upgrade a Safari 5.0 installation to Safari 5.0.1 results in error with NOD web protection enabled. Was able to replicate this any given time.



Having NOD web protection disabled solves the matter, i.e. goes through just peachy. Seems somewhat similar to https://www.wilderssecurity.com/showthread.php?t=278098


Virus signature database: 5323 (20100729)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1283 (20100727)
Advanced heuristics module: 1109 (20100519)
Archive support module: 1118 (20100729)
Cleaner module: 1048 (20091123)
Anti-Stealth support module: 1020 (20100713)
SysInspector module: 1216 (20100517)
Self-defense support module : 1016 (20100404)

 

Does setting a size limit for scanned objects to, let's say 15 MB, make a difference? I assume it could be that the Apple update software times out during a scan of the archive. Unlike many other antivirus software, ESET does not use any size limits for scanning by default to ensure maximum protection but allows users to set a limit themselves in the event of problems.

 

please do not start to go down this route again by proposing workarounds like put this down, switch that off and the like. Turning off web protection gets around already.

on the other hand there seems to be an incompatibility pattern of NOD with download utilities like Apple's update and the one from ATI, both executing code at the end of the download. and both do fine with web protection switched off.

it sound more like the old culprit - 2 of NOD modules competing - the web thing still scanning inside the downloaded data stream whilst the next one already scanning the execution.

trust we had this matter discussed before and yet it does not seem to be resolved.

please talk to the developers to get this ironed out once and for all, the users will be grateful, instead of cutting the balls off NOD and limiting its capabilities.

 

I got this error with iTunes. Just do what it says and you'll be fine.

 

maybe you got this wrong, this is about an issue of NOD to be fixed. a workaround was mentioned already