We have yet not made updates live but are in the process of doing so. Once we do that, will announce the same.
Like i said it has a fix for a crash in UPSDBMaker application, if you are seeing that crash, you should else not a must.
I installed the updates and everything works fine. However, just out of curiosity I uninstalled the updated 126.96.36.199 and installed the latest CAVS from the Comodo website.
Everything is still fine but I noticed that the safelist database version is now 188.8.131.52. After I had updated 184.108.40.206 this still said 220.127.116.11 but after installing the latest version from scratch it now says 18.104.22.168.
Does this mean that the safelist database was not updated when CAVS updated itself?
No problems with the new install though: uninstall of old version went smoothly, install of 22.214.171.124 went smoothly, safelist database maker ran quickly and no errors. Full system scan and everything else working as before.
Just to confirm my last post: I checked another system that has CAVS 126.96.36.199 and after the latest program updates the safelist database is still 188.8.131.52, whereas it is 184.108.40.206 on the system where I installed the latest CAVS from Comodo website.
Does this mean that unless you actually uninstall 220.127.116.11 and install 18.104.22.168 you will not get the latest safelist database?
successfully downloaded the update from CAVS updater (:CLP)
now the version information shows :
build version :22.214.171.124
virus database version : 126.96.36.1990
safelist DB version :188.8.131.52
program update version : 184.108.40.206
[colored red] what that means? no error? you mean no more ===> “error 002:failed to load safelist database”?
i still got this error.
Let me explain how safe database versioning works.
When we build setup, we supply a version of safe database with it and that’s what you see as version.
The update mechanism of safe database is not related to when you take updates explicitly, when HIPS alert appear, it checks if a file is safe or not in local data base and if not does a web lookup on comodo server and if it finds file safe on Comodo server, it adds that information to local safe database but in this process version remains unchanged and will always show what was shown just after installation.
So when you run updater, it only looks for program updates and virus signatures updates not for safe database updates.
We have million+ safe records in database which is available on Comodo server, but we can not dump that database on user’s system as all the files information which is in data base may or may not be present so when HIPS comes across a file and it does not find it in local safe database it does web lookup and additionally when you submit a file, before submission that file is checked if it’s already termed safe by Comodo or not and accordingly if found safe is added to local safe database.
So just to summarise, safe database gets updates:
Through HIPS alerts
When you submit files to Comodo server for analysis
Hope this explains as why database version remains unchanged after you update for program updates but changes when you install an updated setup.