I’m experiencing the same updating bug (keep updatingto version 87).
I spotted another bug: it uses too much battery while scanning apps being installed or updated.
I have 100% on battery and I update 7 apps with Comodo. The process is three times slower and it drains my battery to 96%.
Without Comodo or using another security product the process is faster and battery goes to 98 - 99%.
I have just changed phones from a Samsung Galaxy S3 to the S4 and it’s failing to update, not sure if it is the device change though, presently on Version 86.0 virus definitions
All CMS users experience the same thing now it has nothing to do with your phone. It’s a bug in the CMS update which is being fixed that’s why. Just wait
Oh well yes its a bug that means… I get error saying Update failure…
Initially I thought it was coz I updated the device from GingerBread to JellyBean but seems it ain’t so…
When things don’t go right, you get to see the difference between a free app and a paid for one!..come on comodo, how long does it take to fix this update issue ?
I too feel the development is slow & Devs dont give much attention to CMS threads.
And there is no false positive submission thread. I know you can submit FP through CMS but submission in the forum are solved fast as in the case of CIS. But do they solve FPs in CMS case? I submitted couple in the forum here too many days back, they are still detected by version 1.5 & 2 too. I know they can be added to trusted lists but FPs need to be fixed.
Now, database is updated only when user opens CMS interface (otherwise, CMS will not check for the updates). Sadly, many users install a security app and want to forget about it. They don’t open it at all → CMS has obsolete databases all the time, it cannot detect newest threats. It should be changed - maybe another service checking for updates every time when user will connect to the Wi-Fi etc. (depending on user’s settings). without user’s interaction.
Health Check - Health Check scans for malicious apps and many other risky things. Unfortunately, update logic here is not correct. Health Check first of all check for malicious apps and in the end of this process it checks for the updates. That doesn’t make any sense.
How should it look like is:
User starts Health Check.
CMS checks for updates&downloads them and install (if available).