Updated today to CIS 10 to find several bugs so far:
Update ignored my skin choice, and when changing back to “Modern” theme, window sizes are wrong such that the OK CANCEL choices are offscreen on any options screen. Each time, the screen must be resized to fix the issue. Also, the widget isn’t picking up the theme/skin change. Did you intend that? If not, please fix it.
As others have noted, the REALLY ANNOYING re-creation of the desktop shortcut occurs on any configuration change in CIS, such as going from safe mode to block all traffic, and there does not appear to be a way to manage this. Did you intend that? If not, please fix it.
If things so simple as window-sizing and shortcuts are hosed, what else is wrong, under the hood, that is not so easily discernable? (That is the impression left upon the user with problems like these.)
Problem #1 is annoying but bearable. Problem #2 is enough to make me rethink my use of this formerly stellar product. Whose job was it to beta test this time, and were they allowed enough time to do their job before rollout?
Another issue is with the product branding for the offline installer (and there is a great need for an offline installer.) It is labelled most clearly, and repeatedly, as “Windows 10” although it apparently works for Win 7 as well. When you do that, you do realize that you immediately make Win7 users question whether the product will still work with Win7. Did you intend that? If not, please fix it.
Also, though the download is served from a secure page, the source of the download is not. I can force a secure download by manually entering the URL to the download, and putting in an “S” for the https, but really, did you intend this? If not, please fix it.
This has been such a good product, pay attention and don’t ■■■■■ it up.
Modified to add CIS version 10.0.1.6209 running under Win7-64
2nd modify to add this is an AMD machine
Thanks for your note PremJK. Would you please estimate a time-to-delivery for the bug fixes? Neither I nor others want to wait months. Among the bug issues, I would like to see the desktop shortcut issue triaged, as aside from being an annoyance, it interferes with desktop usage in in other ways, such as for those who do screen sharing for one purpose or another, forcing the use of another machine for that purpose. So, that one alone causes work disruption.
Seems this fix will not come in a days but weeks. Also I’m wondering if I choose the right solution for defence, because of this small bug:
do they testing their releases? because all pointing that they’re only moved shortcut creation function somewhere upper or lower in the code as it should be.
even such a small issue they fixing more than week, but as they said April, 07 - should be fixed within days.
How can I be sure now that this product is a reliable?
Hi PerfectDay,
We released a patch on 10th April to fix most critical problem, however we could not put other fixes like this shortcut one in that release.
A fix is coming by this week-end that will fix shortcut issues and some other issues pointed out in preview build.
Hey, the issue is still there.
Ok, let’s do it in other way.
Environment: Win 10 Home x64
SW build version: 10.0.1.6223, DB 26971
Severity: Minor
Reproduced: 100%
Summary: After closing Contained Apps or Unrecognised Files window, the shortcut of application appearing on the Winows desktop. The bug bringing inconvenience to user, despite of minor severity.
Steps to reproduce:
Pre-conditions: Comodo shortcut is deleted from Windows Desktop, Lycia Theme is using
Open the Comodo Internet Security 10 application
At main window find Contained Apps
Click on Contained Apps
Press the CLOSE button
Verify that Comodo shortcut is present on Windows Desktop
Delete Comodo shortcut from Windows Desktop
Click on Unrecognised Files
Click OK button
Verify that Comodo shortcut is present on Windows Desktop
Expected result: shortcut shouldn’t appear at the Windows Desktop after closing appropriate modules
Actual result: Comodo shortcut appearing at the Windows Desktop
I am not your QA engineer, thus didn’t checked other modules, so it’s possible there are also some modules can be with this bug. Please refer.