This update simply fixes a AV Update issue. As stated here by Umesh (Comodo head of AV Labs):
AV Updates will continue hopefully tomorrow as stated by Umesh.
Here are the download links for those who would like a fresh install and are new CIS users - Latest CIS build as of Wednesday, January 06th, 2010 - Existing users can update via internal updater.
Unfortunately the previous (merged) thread was locked too quickly
The question is for those who are using Firewall only.
Will the update “from withing” download unneeded AV database or such update will just change the version… or
it’s better to wait resuming the DB update so that would not break the Firewall functionality
I’m kinda not in a mood to go through complete reinstall of perfectly functioning Firewall if something are expected to go “wrong way” due to AV issues I’m not interested in.
This update V581, just has binary update of 1MB+ and does not bring an AV updates as such.
So feel free to update to V581 even if you use Firewall only.
In CIS V4, firewall users will not be affected in case we ever issue AV bases update. Although binary update, even though caused due to AV issues will always be common and user is advised to always keep latest version.
So we are making sure that in CIS V4, firewall users are not bothered for any AV bases update.
I have upgraded to *.581 build (full CIS) but cannot update past 3468 (although 3490 is shown on “… latest additions” page. Do I need to replace bases.cav manually or is there a problem with the updates server currently?
Edit: Btw, on another computer yesterday evening, I installed *.581 from scratch but couldn’t update at all (stuck on update 1) saying I had the latest version.
I have two questions: this version is tested for errors and whether the Comodo testers that tell developers about bug reports? Just shake one version over another is very expensive and I would like to have a stable product, not its raw version.
@umesh: When will the issue get solved that AV database’s MD5 and size differs for some users?
That’s a state that shouldn’t be, I’m anxious it is leading to aberrant detections.
Hello Everyone:
Seems that the AV DataBase misconfiguration issue has been fixed, like some other people i had an issue with the misread of database version no, but as of 8/1/10, AEST 0230, data version corrected itself from 3482 to 3501, thanks to the people behind the prompt action: We are only human i spose mistakes will occur sometimes :: Cheers People :-TU :-TU :-TU ;D ;D ;D!!!
OK, updater did worked fine on my XP-SP3 (will wait a few days to update the W7) and the DB IS BEING updated right now. (took just one minute to go from 3474 to 3502).
Seems working fine!
THANK’s.
edit:
My XP-SP3 bases.cav updated to DB 3502 is as follow:
98.530.347 bytes, mod at 2010-jan-07 15h40m38sec UTC
MD5= 5BFF805106BB462615689FEAABEA043A
SHA-1= 51af75b080a494a18189ef07c366258beccd9574