same problem, update fails:
Virus Database Update window says it is around 90% done then it fails
“Please wait while the virus database is being updated.”
then it counts new versions from 19332 to 19353
then “Finalyzing…”
then “Failed to update the virus signature database.”
Windows XP Professional
Comodo Internet Security Premium
Product Version: 5.12.256249.2599
Virus Signature Database Version: 19331
This PC wasn’t rebooted for much more than four days. So I would say it is not because of Windows or new Windows updates.
Windows Updates have a long track record of inadvertently breaking non-Microsoft program functions, so that could very well be causing it. If you can, go mention that in your support ticket.
Well, we’re back to where we started. Now the signature updates stopped working again and the website database one is going through again.
If I get a response to my ticket I’ll try to mention it.
same problem, update fails:
Virus Database Update window says it is around 90% done then it fails
“Please wait while the virus database is being updated.”
then it counts new versions from 19332 to 19353
then “Finalyzing…”
then “Failed to update the virus signature database.”
Windows XP Professional
Comodo Internet Security Premium
Product Version: 5.12.256249.2599
Virus Signature Database Version: 19331
This PC wasn’t rebooted for much more than four days. So I would say it is not because of Windows or new Windows updates.
Well, it’s not exactly the same. I have Windows 7 and I am using the latest Comodo Internet Security.
Hey guys, from what I know Comodo has been making some changes to their virus database, making it smaller and creating generic signatures to improve efficiency. Your problems may be related to that so I recommend contacting Comodo and seeing what support they can provide since this appears to be a server side issue.
Quote from: MurderHeWrote on Today at 01:15:21 PM
Well, it's not exactly the same. I have Windows 7 and I am using the latest Comodo Internet Security.
So the problem is your installed versions of Windows and Comodo?
Okay, okay, I just thought the problem is:
Quote from: MurderHeWrote on Yesterday at 03:09:42 AM
I just got a notice on my taskbar telling me that the virus database hasn’t been updated for two days.
If I force it to update the “Check for Signature Updates” fails while all the other updates appear to go through just fine.
Nothing has changed on my computer lately.
Sometimes I feel like Bill Engvall wanting to say “Here is your sign”. I was replying to another person’s issue when they said it was was same, but from appearances was not.
I received the following reply from Comodo. Part of the answer was the same as one given earlier in this thread, but the first part is an addition to it. My updates are working fine now. Maybe someone else might profit from it. However in the part where you use the command prompt, they let out that you need to use the program as administrator by right-clicking on the Command Prompt in Accessories and choosing “Run as administrator”.
We are sorry that Comodo update is not happening normally. Please follow below steps that could fix this issue.
Please disable IPv6 from your computer. You could follow below instructions to disable IPv6.
For Windows 7, 8 and Vista
- From the Start menu, select Control Panel. Make sure you are in the Large or Small icons view (Windows 7), or Classic View (Vista).
- Open Network and Sharing Center.
- On the left, select Change adapter settings (Windows 7) or Manage network connections (Vista).
- Right-click the connection for which you want to disable IPv6, and select Properties.
- Uncheck Internet Protocol Version 6 (TCP/IPv6) and click OK.
For Windows XP
- From the Start menu, select Run…
- Enter cmd .
- Enter ipv6 uninstall .
Open Command prompt and enter below commands one by one.
- ipconfig /flushdns
- netsh winsock reset
Please open Registry editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings, copy values of DefaultConnectionSettings and use it to replace the data stored in the location HKEY_USERS\S-1-15-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings.
IMPORTANT: You need to back registry before performing the above step. Please find instruction about backing up the registry in below link. How to back up and restore the registry in Windows - Microsoft Support
Restart the computer and try updating Comodo Internet Security.
The problem with that is disabling ipv6 is not a long-term solution as the Internet is switching over to ipv6, so that needs to be enabled for future internet connectivity.
It can’t be that hard for Comodo to enable ipv6 on their update server. That should take them all of 5 minutes, tops.
I also get this problem
I use Windows7 Pro and have tried reinstalling Comodo. The only difference to previous posts is that restarting Windows seems to clear the problem temporarily. The problem recurs after a few days, but I do get updates during that time and I am able to scan at any time.
I refuse to disable IPv6. This is not an acceptable solution. COMODO should fix this from their end. . . Soon
For the moment, I am sure about this:
My COMODO 5.12 successfully updates after a reboot, but not afterwards.
That is why I get this error message every time my machine is up for a longer time.
1. Please disable IPv6 from your computer. You could follow below instructions to disable IPv6.
For Windows 7, 8 and Vista
- From the Start menu, select Control Panel. Make sure you are in the Large or Small icons view (Windows 7), or Classic View (Vista).
- Open Network and Sharing Center.
- On the left, select Change adapter settings (Windows 7) or Manage network connections (Vista).
- Right-click the connection for which you want to disable IPv6, and select Properties.
- Uncheck Internet Protocol Version 6 (TCP/IPv6) and click OK.
For Windows XP
- From the Start menu, select Run...
- Enter cmd .
- Enter ipv6 uninstall .
Open Command prompt and enter below commands one by one.
- ipconfig /flushdns
- netsh winsock reset
Please open Registry editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings, copy values of DefaultConnectionSettings and use it to replace the data stored in the location HKEY_USERS\S-1-15-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings.
IMPORTANT: You need to back registry before performing the above step. Please find instruction about backing up the registry in below link. How to back up and restore the registry in Windows - Microsoft Support
Restart the computer and try updating Comodo Internet Security.
This worked for me ( Win 8.1 x64 ) although didn’t do option 2. While this fix works we shouldn’t have to be doing this. While it may be easy for experienced PC users it may not be so for inexperienced users. I hope this will be fixed in future updates. I’ve been a huge fan of Comodo Internet Security and will be for years to come. But please fix this issue. Thx for the fix, it was doing my head in.
Just so everyone knows, my Comodo license key was the cause of the signature updates not updating. I got Geekbuddy to issue me a new license key and updating virus signatures worked properly again upon re-inputting it.
So basically Comodo had intentionally disabled your previously fully working product ?
I mean a licence key and the remote checking thereof can’t suddenly and quite randomly ‘go bad’ and all that can it ! Some form of local data corruption or whatever with no other obvious problems or side-effects is almost implausible. Some identifiable action must have caused the problem with your licence key apparently preventing the product working as it should do.
If so then I wonder just how many of the other update problems various are actually being caused quite intentionally by Comodo effectively disabling updates remotely. Historically, there are more often than not several instances of much the same problem occurring at much the same time. They can’t all be just random problems, there has to be some connection. I’ve long since suspected that Comodo have been intentionally disabling products, particularly older products on older systems, in an attempt to force users to upgrade to a significantly more bloated and potentially totally unsuitable product.
Hi ambrougham,
If what you are saying is true (Intentional), I can’t imagine why Comodo GeekBuddy would issue a new key? 88)
I mean a licence key and the remote checking thereof can't suddenly and quite randomly 'go bad' and all that can it ! Some form of local data corruption or whatever with no other obvious problems or side-effects is almost implausible. Some identifiable action must have caused the problem with your licence key apparently preventing the product working as it should do.
There are numerous reasons why things go bad, some known and unfortunately some unknown or unidentifiable.
[Sorry for the necro but since this is the #1 hit for the search “Comodo failed signature updates” I figured I would comment back]
Okay this issue has plagued me through many different PCs from my desktop (CyberPower Fang III with i7 [at] 6.44Ghz 64GB RAM) to my latop (HP Elitebook 8440p i7 [at] 4.24Ghz 16GB RAM) and my son’s computers, wife’s computers, and several of my friend’s computers – today it was my work computer…
Typically I just uninstalled the Comodo software, cleaned the registry with CCleaner and then reinstalled. I figured there needed to be better way. The only thing all these PCs have in common is that they are running Windows 7 [Pro or UE] - so my first assumption is that it is something in a Widows update (UAC or Windows Defender) every once in a while that causes this.
Today I found if you temporarily shut off UAC and Defender and then click the “Update” button in the Comodo interface - not the “Fix it” button. It bypasses the issue. and the update proceeds like normal.
The problem is Microsoft’s watery internal security not Comodo’s host server. The issue is occurring because some level Window’s Security Center is seeing the update attempt as an unauthorized action - not that of the system’s security software, and is blocking some level of the transfer.
I just suggest permanently disabling the MS junk security bloatware since it is a joke anyway and any hacker worth his salt will be able disable it in a heartbeat (even if that proves difficult to the end user rightfully disabling it… lol)
It still occures from time to time and too often in my opinion.
Following provided tips do not help for sure:
The license thingy would make sense, if cfp checks it after downloading (and installing?) the newer versions, if the update window process information are correct. But that sounds very weird to me.
How can i check my (free) license?
