Comodo Internet Security v10.1.0.6474 Released

Hi All,
We are happy to announce availability of Comodo Internet Security Premium v10.1.0.6474.
Thank you for all the feedback on last test setups.

We have updated with following production setup links and we will release updates to older version users most likely on 8th Jan, 2018 after seeing further feedback in next days.

In the mean time if anyone wants to update from older version via updater, he can do so using instructions as posted in RC post via test server that has the same v6474.

Online Setup Details:
Comodo Internet Security Premium
Size: 5.3M (5,513,832 bytes)
MD5: baabd18db4c518a62334e83688a38ef6
SHA1: d28acd2b885f8162beec83fd786e33e1d34b170b

Comodo Antivirus
Size: 5.3M (5,513,832 bytes)
MD5: 3c2b21e36dd51c3928c704cb58243a12
SHA1: f5e6dbb6399aa31a563828b14721280f2f9f2aba

Comodo Firewall
Size: 5.3M (5,513,832 bytes)
MD5: 2035670249e65ff3344fd1836e05e3f2
SHA1: 57f3ecdd157e8e57f21b65adaa6954fefd591393

Offline Setup Details:
Comodo Internet Security Premium (Firewall and Antivirus only)
Size: 67M (69,666,424 bytes)
MD5: 93acf0d810220dba12ce23aa3fb5ddc0
SHA1: 27b2db3674aa84b84b97db3156203d9575079ef4

System re-store point:
1- CIS will create a system re-store point before installation and update. This change essentially solves the problem of broken installation. In case system restoration doesn’t work, we have official uninstaller. So hopefully down the road this problem won’t surface again.

2 - Creates QualityCompat key as required by Microsoft Meltdown-Spectre patch KB4056892 upon installation and update. Last production version 6420 is fully compatible with Meltdown-Spectre patch in all operating systems..
3 - Internet Security Essentials (Protection against Man in the Middle attacks) is now optional (selected by default) and can be found in Components section during installation.
4 - GeekBuddy setup is completely removed. It was optional and not selected by default. If you don’t have GeekBuddy installed and you access Live support, it will launch Geek Buddy chat window in default browser.
5 - “Manual Scan” scan profile now has heuristic option de-selected by default, same like “Full Scan” profile.
6 - In Rating scan, when you see untrusted certificate listing, name will come from “Issued To” field of certificate rather “Friendly name” section. Trusted Root Certificate are listed by “Issued To” field and thus easier to find.
7 - Due to various incompatibilities, “Enhanced Protection Mode” is removed from HIPS settings

8 - Improvement with file upload issue:
We have had frequent issues with file uploading in CIS and this release aims to fix it for ever, following are changes made:
a) Max file upload limit is set to 128MB
b) There are some client side changes to improve performance of back-end; as updates propagate we should see improvement in file submission

9 - Improved detection of untrusted certificates. In last release we introduced Untrusted Certificate scan in Rating scan. But it could show legit certificate also. In this release we have updated logic and we can avoid showing known trusted certificate as untrusted as stated here. e.g. In this release, you won’t see false-detection as reported here. That’s the only one exception for now. Please report if you have any legit cases detected and we can put that in exclusion list.

10 - XP BSOD as reported here
11 - Fixed crash as seen while browsing as reported here
12 - Error with Chinese Translation as reported here.
13 - BSOD as reported by ‘Huolsam’ here.
14 - Sometimes unknown certificates could not be removed as found during Rating Scan. Issue was reported here.
15 - If you disable “check for database updates” option from “General Settings → Updates” section, Trusted Vendor List update check will also not be made.

16 - There are multiple crashes fixed as reported via Crash Reporting feature. We will continue to fix submitted crashes in every release going forward. We hope to see improved stability in next releases.

Please give it a try and share your valuable feedback.


:-TU :-TU :-TU :wink:

Congrats with the release and timely response to the update to mitigate Meltdown/Specter vulnerabilities. :slight_smile:

I installed the Meltdown/Specter patch one my Win 7 SP1 x74 and before rebooting I updated from CIS beta 6464 to 6474. Windows Update didn’t show the update but I used the stand alone installer. Everything is running as usual after the reboot.

This is great news! ;D
I shall be monitoring this thread closely for user feedback. :-La
Hopefully a solid release! I hope to try installing this clean tomorrow. :slight_smile:

EDIT: On small side note I have confirmed that .6420 works perfectly when adding the registry entry to prepare for KB4056892.
Installation went smoothly without error and Windows 10 is now at 16299.192. I did NOT need to reboot in order for Windows Update to detect the newly created registry key.
I did however need to click check for updates 2-3 times before Windows Update detected I needed the patch to download and install. Hopefully I will find time to install .6474 tomorrow!
I will post back with feedback on .6474 also. :-TU

Hi umesh,

The reason was not in updating the Windows and CIS, but in the Windows error. Reinstalled Windows from scratch and everything works fine.


7 - Due to various incompatibilities, "Enhanced Protection Mode" is removed from HIPS settings

This is sad. I will avoid the update for now.

Now the red icon in the firewall section is constantly on the Windows Defender icon and in the Security Center, although it is included in the Comodo. Previously, this was not.

Hi Guys,
I have updated to the new version and everything is ok. One question: now CIS no longer detects me as an infected CCleaner (the previous version blocked it), is this normal?

Can you please share sha1 of file?

It looks as though CIS will still trust a digitally signed file as long as the file hash itself is white listed, even if the vendor is not white listed. See attached JSON dump of CCleaner.

… How do i do? do not know how to do it
is it this (58CB25589CE12E3833AFA31E1FC663BD093BA53F) ?

It’s little complicated file-rating logic and we will be improving logic in next releases.
In brief, if a vendor was removed from Trusted Vendor List, for two days related file will have local rating as unrecognized and if same file is executed after 2 days, cis will check if we have safe sign for file. So unrecognized cache expires in two days.

Considering in v6420 we had Ccleaner vendor in local TVL and it was removed, due to cache logic you see that behavior, so for same file in v6420 you may see CIS alerting and if you fresh install v6474, as ccleaner is not in local TVL and thus was never removed from local trust settings, it will not have that unrecognized cache.

We will be making decision to add CCleaner related vendor in TVL by next week-end.

So can I be quiet? Is not it infected?

Yes, file is safe.

OK thank you very much :-TU

Installed and everything running smoothly with KB4056894 on the Win7 Pro x64 also

Installed and running successfully Win 10 - 1709 build 16299.192 though I do have the Defender Centre notification “Actions Needed In Comodo Firewall”. Also ISE doesn’t install even though it is selected in the optional components and installer downloads ISE.

EDIT (Update): I went into msconfig.exe and selected “normal startup” which reverts to selective automatically, restarted my laptop and the firewall issue went away. Doing further tests but so far this resolved the issue for me.


Thanks for sharing this Eric! I too have this issue. Upon each reboot of Windows 10 Pro, the Defender Centre icon is green then changes red after 2-5 minutes every time. I will have to try your suggestion on msconfig and report back.

Any ideas on what changed in Comodo between this release and the last one to have this occur? Perhaps something to do with the latest Microsoft KB update?

Same here. Can’t trust CIS until it is fixed.

Dustyn and Samma could you try the Security Center reset to see if that solves your problem? Registration with the Security Center in general is often just a problem caused by the general flakiness of the Security Center it self.

Open a command prompt by clicking Start → Run. Type cmd and click OK.

In the command prompt window, type NET STOP WINMGMT /Y and press ENTER.


Type EXIT and press ENTER to close the window.

Restart the system. Windows should start normally, but you may be prompted to restart the system once more to complete the changes caused by resetting the core repository. You may also need to restart once more if Windows Security Center still does not detect your security product.