iPhone Update to 3.0

I'm running NOD32 v.3.0.672
Upon reading forums elsewhere, I have discovered that NOD32 is blocking this update from downloading in the Apple iTunes software. Disabling NOD32 allows the download and installation processes to happen like they're supposed to.

I have several salesmen with iPhones that will need this 3.0 update. I have password protected the NOD32 configuration and I don't want to give out the password to everyone so they can disable their NOD32's just to get the update. Apple iTunes doesn't show up as a browser in NOD32 (at least the one person's that I looked at) so I can't tell it to not scan iTunes traffic. Is there a way for me to make this 3.0 update accessible through the configuration options without disabling NOD32?

 

Most likely it's caused by a timeout when the iPhone updater minds the delay caused by scanning a larger archive. The best would be if we could get that file for whitelisting so that you don't have to set size limits for scanning archives or temporarily disable web/real time protection.

 

Hi Marcos,

I have been unable to get a hold of a user's pc that has an iPhone until now. Unfortunately, he already did the iPhone upgrade to 3.0 by disabling the scanner temporarily. However, we did find the location of the update file. The file was 230MB in size, so I don't know how you plan on getting a hold of it. Anyways, the path to this file on WinXP is:
c:\documents and settings\%username%\application data\Apple Computer\iTunes\iPhone Software Updates\
The filename is:
iPhone1,2_3.0_7A341_Restore.ipsw
Now, what I don't know is if that filename changes depending on the pc it's on or the user that's logged in.

How do I Exclude this file path? %username% or %appdata% don't work for a path name.

Thanks in advance!

 

This is not true.

I have the same configuration and iPhone updates to version 3.0 without any problem whatsoever.

 

I beg to differ. I don't know how you can tell me it's not true when plain and clear you don't work with me. I have had this problem on 10 different computers and the latest one being today with whatever the current signatures are. The download gets almost all the way done...like to 99.7% and then it bombs (5 times in a row). As soon as I temporarily disable NOD32, it downloads successfully and installs to the phone like it's supposed to.

 

See the post here:
https://www.wilderssecurity.com/showpost.php?p=1467952&postcount=8

 

Thank you! I will try this work around. Is this something Eset will be adding in the future to the standard install? Otherwise, this might be a pain to have to make sure the registries are maintained.

Kind Regards,
Brett