Comodo AV Version 5.12.256249.2599 Won't Update

You install software using LUA? That’s interesting.

I shall try to update it through manual mode. I hope Comodo AV recognizes the updated definitions under LUA. I’ll download the 267MB file and follow the steps as mentioned here:

If it doesn’t, I’ll go ahead to uninstall the 5.12.x suite so that I can re-install only Comodo Firewall part. I hope the above mentioned method works. Later I have to find a low-resource hungry AV which works in tandem with Comodo Firewall…

When you run the installer from Add/Remove Programs or from the start menu you will get the choice to remove components or completely uninstall. You can then choose to uninstall the AV only.

You do need UAC active though, the only recent install I used Admin account for was printer drivers absolutely refused to run in LUA account.

Please note using the manual method you may need to reboot or wait sometime for CIS to recognise the database.

I tried the manual method through ‘Safe Mode’. Sadly, the AV didn’t recognize the latest definition file yet. I’ll wait until tomorrow to see what happens.

Last resort would be waving goodbye to the AV module. Thank you for all the support given to an outdated product. I appreciate it irrespective of the outcome :slight_smile:

I’m compelled to present my experience.

15 Mar 19 I inadvertently clicked the update balloon for my CIS v5.12.256249.2599 on my Win2003 R2 system. Obviously my system became useless after that point; CIS being hopelessly corrupted. No recourse was available other than restoration of %SystemDrive% image dated 15 Jan 19. :-[

After dealing with the obvious ramifications / repercussions of non-sector, i.e., MFT, based partition image-restore , and necessity for HDD NTFS metafile / layout optimization / free-space consolidation, et ali, CIS update to A/V defs with a bulk download occured successfully and uneventfully. A/V updates were attempted subsequently 15 Mar 30 that failed w/ out recourse; the CIS inherent Dx Util stated: NPF.

The then current A/V def file was downloaded from Comodo Anti Malware Database Latest Version & Additions 2022. In Safe Mode I archived - with NTFS security - the currently working A/V def file and copied the downloaded aforementioned A/V defs file, rebooted and subsequently CIS A/V update failed.

Subsequently the CIS /repair A/V def file was archived - in Safe Mode - and the aforementioned A/V defs file was implemented to CIS /repair, and /scanners was deleted. Upon reboot CIS A/V update failed.

I’ve found that CIS Quarantine folder has been a sore point WRT defragging, i.e., the folder, subfolder and files contained therein are ‘locked’ and inherently fragmented will cause prollems with the HDD layout / defrag. It should be known that in all of my previous attempts, the CIS Quarantine folder was ‘poofed’ every single time.

O.k.

If you’re following: where’s the stinkin’ prollem?

It has to be on the drive, eh?

So I chkdsk %sysDrive% /x’d it and the Event Log said this about that:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 3/30/2015
Time: 2:20:30 PM
User: N/A
Computer: Colossus
Description:
Checking file system on %SysDrive%:
The type of the file system is NTFS.
Volume label is HAL9000

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 103 unused index entries from index $SII of file 0x9.
Cleaning up 103 unused index entries from index $SDH of file 0x9.
Cleaning up 103 unused security descriptors.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
Correcting errors in the master file table’s (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

12289693 KB total disk space.
11165296 KB in 43416 files.
17240 KB in 7358 indexes.
0 KB in bad sectors.
134845 KB in use by the system.
63504 KB occupied by the log file.
972312 KB available on disk.

  4096 bytes in each allocation unit.

3072423 total allocation units on disk.
243078 allocation units available on disk.

Attempt to update CIS A/V again with failure as result. I must go to CIS forum; I be stupid. :-[

I read and read. I read many many very mad people. I read thread post more and more people mad and threaten to go away and not bother people like me reading any more. I’m very happy; they’re going away.

I think and realize that I’m not any happier because they went away; I still have this problem.

So now I read more.

I read this:

bases.$$$

Oh, what’s that? I see that I have bases.$$$ with 36MB. Huh. Really.

So I make bases.$$$ go away to a very bad place - tormented by myself perpetually -and leave the existing A/V defs I downloaded in both /scanners & /repair, and I ■■■■ away Quarantine and then reboot out of Safe Mode and CIS A/V defs update w/ out a single hitch.

I waited until now to post; I wanted to see how re-update works. It works; AFTER the BSOD err=77 that occurred during the A/V def update process. That notwithstanding, after dealing with the frag’d Swap File that’s always consequent to ERR=77 BSOD, CIS A/V updeated flawlessly.

I believe there’s a little dragon lookin’ for its Mommy in the CIS A/V def files.

:o

:-\

Status: update virus defs not recognized by the product. My concluding words on this thread:

First, there was no question of being unhappy with Comodo Firewall. It’s a solid product, and this is a handy forum (guides) and decent staff to guide the members.

Next, like Comodo Firewall, I was loyal to Avira free AV on this aged machine. The latter’s product became more and more resource intensive, hence at one point of time I chose to uninstall it from this PC. I thought using AV and Firewall from the same suite shouldn’t tax more than Avira AV. That’s how I chose to go with CIS 5.12.x. But I had no idea about its AV update issue. Hence this thread.

For the given hardware spec, Comodo Firewall works great. I’m happy :-TU

I’ve one question: is CIS 6.x resource friendly like 5.12.x? Thank you.

Bulava. I suggest to wait for the release of CIS v8.2 which is currently in beta. There are great improvements on the update procedure especially noticeable on older hardware; my old ASUS EEE netbook with both XP and Win 8. The improvement is so big I installed the beta on both. The general performance is that it runs a bit lighter than previous versions.

WxMan1. What file does the BSOD tell is related to the crash? Use BlueScreenView in case you can’t remember.

Hello EricJH,

Thanks for the information. I’m using CIS 8.1 Firewall with Avira AV on various machines and devices. Those have powerful CPUs and have abundant RAM, hence no concerns on this front.

But this is an old machine, with single core CPU and limited RAM. I tried CIS 8.1 on this hardware; resource consumption is high when compared to 5.12. Avira’s new edition became too heavy, hence I removed it. As you know, I had this bad experience with Comodo 5.12 AV module. Currently there is no AV on this machine; should find a suitable one soon…

I think there is a specific set of problems with v5.1x that does not happen with v8. The upcoming v8.2 may be interesting for you. I can’t comment on memory usage of CIS 8.2 as my netbook has 2 GB of RAM but other than that the performance gain I noticed gives hope for your old machine.

Its broken again and won’t fix; I repeatedly deleted Quarantine, and bases.$$$

I downloaded current bases.cav offered at CIS-home vdp-updates page, i.e., stated version = 21651

cleared out the existing bases.cav in safe mode, deleted Quarantine, moved in downloaded bases.cav, rebooted and tried to update = failure.

CIS A/V defs version stated in About = 21588

CIS A/V defs /repair = 273455 KB
CIS A/V defs downloaded per above = 273262 KB How is that possible when download version is most recent?

From web-site:

Latest Database Version:
21651
Release Date (all times GMT):
4-Apr-2015 10:59:58

And yet, its smaller than /repair/bases.cav dated 30 Mar 15 from 1 Apr 15 last successful update. Furthermore, the create date of the purported v21651 = 1 Apr 15 [at] 1803. The file offered at the update is NOT what is purported to be.

Watching bases.$$$ during update: sometimes its 0KB other times it starts at 632KB. Status of update shows downloading / applying BASE_UPD_END_USERv21588 thru v21651.

On 30 Mar and 1 Apr bases.$$$ grew to full size, and subsequently renamed to bases.cav. After it fails, bases.$$$ = 36903KB

This is the same ■■■■ that happened last year when the v7 update fiasco occurred. They couldn’t get it or the original v5.12 to work. I had a major support nightmare on my hands. Eventually multiple CIS subscription were cancelled as a result and competitor product was implemented.

O.k. STOP the freakin’ presses right now! :P0l

I had to go and get some serious alcohol into my system - special - to get to the bottom of this.

The bases.cav offered at the CIS-home VPD site s’poda be v21651 release date 15 Apr 4 is indeed the very same that I downloaded from the same site 15 Mar 30, i.e. CRC32 = 15f06379. That is the same file that is included in the presently hosted bases.cav.z dated 15 Mar 29 2312.

It was on the 15 Mar 30 when I ran into A/V defs update failure and implemented that file for successful update post-bases.$$$ / Quarantine deletion. On 15 Apr 1 CIS A/V defs out of date was successfully resolved via web-update which established A/V defs v21588.

Deductively the problem can NOT be anything other than at least one incremental BASE_UPD_END_USER since 15 Apr 1 the time of my original post; all such files previous to my posting implemented properly on 15 Apr 1 with start point of the full A/V def file contained in bases.cav.z with CRC32 = 15f06379 and dated 15 Mar 29 2312, i.e., all incremental updates implemented since then until 15 Apr 1 date of my OP.

I believe that somebody is taunting >:-D one or more of the incremental A/V update-files; it can’t be sunspots 'cause its dark somewhere at the time this is happening.

I wanted to see if an updated A/V defs was available so as to bypass any issues with intermediate incrementals. I just downloaded the current bases.cav v21667

Size: 272059KB CRC32=1a4be892

I was stunned to find this file to be even smaller than what I previously intimated ???

So I downloaded bases.cav.z and found it to contain the very same file, and CRC32 was identical in both cases.

So I checked what version CIS thought was installed, and suprise suprise: v21651

So I clicked the Update Now button for the out of date definitions warning on the main GUI.

It took about 5 seconds for it to return: A/V defs updated - downloading no incrementals - and current virus database shown to be v21657.

;D

The fact that the current v21657 is smaller than v21651 remains an enigma. We’ll see how this plays out over the next days.

Aside from the fact that I wasn’t notified about CIS A/V defs being out of date until I rebooted on the 11th, CIS A/V defs update seems to be functioning properly now.

After I rebooted on the 11th and CIS initialized, the A/V defs out-of-date status was indicated. Clicking the button updated the A/V defs w/out issue.

Today the out-of-date notification again appeared and after clicking the update-button, the update occureed w/out issue. Looks like this once again a non-problem.

  1. :-TU

Hi
I have new information about CIS.
This is somewhat postmortem information , because i am using another anti virus now but any way.
Before i completely remove CIS i decided to check some possibilities.
I uninstalled CIS 5.12 rebooted, end then reinstalled , rebooted , and update failed.
Uninstalled 5.12 rebooted and installed 5.10 , rebooted , and update failed.
Then I uninstalled 5.10 rebooted and installed 5.5 . Rebooted
and …
What happened? Ppdate started , bases.$$$ reached 52 MB and in this situation CIS remained very very long time , but finally update succeeded !
Then i updated again , and again bases.$$$ reached 52 MB , and after very long period , update succeeded.
After some time i updated again . bases.$$$ again reached 52 MB and after long period bases.$$$ reached 669 MB , then bases.$$$ disappeared and bases.cav reached 669 MB.
But CIS reported update failed! , Then reported update failed , anti virus engine not initialized.
Then i restarter cmdagent.exe , and everything was ok.

So, Is it possible that CIS 5.12 has some kind of timer that cancels update and reports failure. And if this timer waits longer , the update will be successful?
And if such timer exists , perhaps it is possible for the users to increase waiting time , and this way make SIC 5.12 working again ?

Questions… Rather pointless and useless …

Read ! Envy !
I am using another anti virus now ! :))))

I just wish they’d fix it. I mean seriously…guys…

ialtaparmakov: what new one are you using? Is it on XP?

What ever antivirus with working updates is better than perfect antivirus with not working updates.
As example of such working antivirus I may point Clam win portable with clam sentinel. :wink:

Once upon a time i was using AVG. After a while I disappointed.
Then i used Avira. After a while I disappointed.
Then i used Avast. After a while I disappointed.
Then i used COMODO. After a while I disappointed.
Meanwhile i heard my friends screaming disappointed in: Symantec , Nprton, NOD, Kasperski, Mcafee…
Now i am using Avast (works on XP). Again. But I see some bad trends. Again.
And on the horizon i see 360 antivirus. As a safe island it cold be good idea? Perhaps I will see…

But do you see the whole picture?
I am (perhaps We are?) drowner in a sea of viruses and i am constantly searching for a safe island…
Around are floating some parts (of a crashed ship). Sоme submerge, some emerge up again…
And if I catch one it soon submerges …

There is a trend floating parts to form a circle of relatively good free antiviruses.
COMODO is still in this circle, but in the past years COMODO had upper place in the top-list…
Perhaps COMODO will stay longer in this circle of relatively good free antiviruses…
Who knows?..

ialtaparmakov: Yes sigh this seems to be the trend with many softwares, websites and even tangible products. In their perceived efforts to make it good for everyone (especially idiots) they are making it all good for no one. Many a developer is jumping on this bandwagon. Many big business is buying out the smaller, better one in order to skuttle it “restructure” it because despite excuses they hate competition and hate free will.

No one fixes will not be because of an outdated version of the program, more than advise the latest version 8.2 it is not this bug, and the memory it consumes less, thus speeding up your system! I did so, and others advise!

As Melih has stated tiredlessly and on numerous ocasions CIS (and its derivatives CPF, CAV) will always be free. It is part of Melih’s vision to give the world top notch protection for free. He sees it as a right.

Antivirus is the first place in the top if it will suit all users, but it so happened that I also used Avira then Comodo (was and is a party to their forums), only an advantage it is so free of charge, the sadness is that these antivirus is no free support even if it is, it can not be of any help, subtly alluding to paid support, that’s why antivirus and are changing their place in the top!