Already done. All “hard drives are excluded” including C drive.
Don’t shellcode injection detection is checked!!
The only thing i didn’t cover in my post was under
Under miscellaneous
Everything is checked minus
Show alerts in case any other software attempts to modify current settings of installed browsers
There may be a problem updating Windows KB KB4541335, delete.
@LBJM. Did you add the installation folder of Robocopy to the exclusions of shellcode injection detection? You mentioned you checked it but I want to make sure you added Robocopy installation folder to the exclusions.
Could you uninstall Robocopy, reboot sand test your system? That way we will learn if there is a compatibility issue with Robocopy.
Robocopy is not a third party install. It is apart of the windows installation on Windows 8.1 and 10. The Windows/system32 folder is apart of the exclusions.
I am unable to recreate the BSOD part of the problem with this build of comodo. Older releases prior to build 12.1.6914 I could. The freezing would still happen, but that is with other applications randomly. The system doesn’t stall out. The problem has now been reduced to random hiccups and the only thing in my testing that is giving me repeatable results is Need for speed heat which might be related to the game. I need more time with this build.
In the past any heavy IO applications would cause the problem.
With the changelog saying
I know at least the devs are aware of the problem, but the root of it comes from windows 8.1 and was carried over to windows 10. It’s a conflict between windows and comodo. Chances are it has to do with the latter trying do too much to control the system. I really just want the firewall comodo and not all the extra garbage it sucks at doing when I already have software that is more robust. At least with my testing I know it’s comodo at it appears to be slowly getting fixed.
Comodo Internet Security Pro v12.2.2.7036
Windows 10 Pro 1909. Latest Updates.
It seems that when i have Comodo installed this NULLs appear as proccess. ( Shown in image below )
Hello liosant, You can change the settings as per your convenient.
Have a nice day!
Kind Regards,
PD
Any news from Comodo about progress on getting 12.2 released? build 7036 is now a month old…
Regarding Secure Shopping. In virtual machine with clean OS I try to emulate the conditions of my computer: Internet Explorer 11 uninstalled (Microsoft vulnerability warning ONLY for having it installed), Edge, Firefox and CIS 7036. Nothing else.
I configure www.google.es as the address to open with SS. I set Firefox as a browser for SS. I access www.google.es. Pop-up appears. I select ‘visit with secure browser’. Nothing happens. I try it several times, I restart the machine. Nothing. In other simulations, it had been able to open it with the following result: it opened in a secure browser and when it detected access to www.google.es again, it would ask again, select ‘visit with secure browser’ again, it would reopen, it would return to ask … loop. Multiple windows. I had already read it in a review, but I had the opportunity to see for myself. In 30 years of profession I have done hundreds of programs, maybe thousands. Always delivered after an exhaustive set of tests to test until the last instruction, until the last if. Has that good habit been lost? Anyway, not this time, decide to ignore the option ‘visit with secure browser’ from the beginning. The fickleness in behavior is surprising (edit: maybe in those other simulations IE 11 was installed).
Well, let’s go for the second one, I go to www.google.es and in the pop-up I select ‘visit in secure shopping environment’. This time it works and opens the secure environment and the browser with the requested address, but oh surprise, on the ‘other side’ i hear a warning. It has detected that the address has been opened and asks again. If I select ‘visit with secure browser’ it returns me to the secure environment and no longer asks. If I select ‘visit in secure shopping environment’ I go back to the safe environment with an error warning me that the browser is already open.
Third. I access www.google.es and in the pop-up I select ‘continue in current browser’. It does nothing and I stay in the same browser. Doing nothing does it well.
To all this, on my real computer, which I do not plan to format to install from zero and fix the problem, SS still does not detect the accesses to the configured addresses despite having uninstalled CIS with ciscleanuptool 3.0.0.32 and SS with Bulk ■■■■ Uninstaller and reinstalled.
Bonus Track: I have also tried to uninstall only SS and reinstall the latest independent version downloaded from the Comodo website. 1.1.421512.98, I think. Two surprises. One: in the independent installation it offers the possibility of unchecking the option ‘send anonymous data about errors and crashes to COMODO to improve the product quality’, with which you save (as I had described in a previous post) the continuous accesses of csssrv64. exe to external ip’s. Two: After installing this version, Edge stops working. Not associating one thing with the other, I have uninstalled and reinstalled Edge packages, Edge itself, and even recovered images from the OS until I saw that it was SS. It is uninstalled and Edge works again.
I sincerely believe that the product needs a revision.
Updated*
Comodo Internet Security Pro 12.2.2.7036
Windows 10 1909 Pro. Latest Updates.
Another ‘Bug’ Report:
It seems that Comodo losing the signatures database returning to 1 in some cases, i’ve faced 2 ways that it may lose it.
1: If an Erase on hard drive happen ( Replace free space with: Zeros, DoD32 / Software used: 0&0 Safe Erase) tested once with zero.
2: Or you got through some BSOD with missconfigured Memory that can lead to OutOfRange area drive access/Null (Page fault on none page area) etc.
Hi,
It is me being “too” impatient and I am sure there are reasons, but I do not understand this company policy where months after the first unfinished release there is still no hope to receive a matured product in the next days.
It is OK for me a forum discussion to be used for repairing the product, but it is not ok to stay in the dark without any info how things are going on. There are several promises to receive the final, but they are (almost) never being kept. For me personally CIS v.8 was the last one which matured to a nicely working release. V.10 was a… lets jump over. Now I use v.11, but it gives often and randomly very high CPU use, v.12… according to the results seen in the forum - there is still a lot of work to be done.
I know CIS is free, but apparently free is not enough.
I don’t see any visible instabilities (only explorer.exe crashing once today out of the blue with c0000374 exception, but that’s not necessarily because of CIS), but also I see one cavwp.exe crash with Access Violation error (that’s already on CIS 12.2 RC). I’ll include all the dumps I could muster. 
Also CIS diagnostics shows me error, so I’ll include that as well.
OS: Windows 7 x64 with latest updates (no extended updates program though).
Why? Internet Explorer is dead.
After being stung by the 12.1.0.6914 (production) release I installed this RC on a single WIN 10 machine and have been very pleased with it. I’ve been running it for about 3 weeks. Keep it up!
6914 was a very unfortunate and unstable build in between stable builds.
Protected Objects in HIPS works? Protected Data i think yes, but Protected Files and Blocked Files?
Hi Perter Pan,
6882 is a stable release and I would advise upgrading to it from 11 if possible due to important vulnerability fixes.
Kind regards,
Reece
I am unable to use CCE and get the error ‘Failed to load engine’.
Is this just due to the hosts file edit?
Reece
Thank you Reece,
Having in mind that currently the upgrade process of the last 7036 is being tested I will have patience to wait for the stable release
With my best wishes,
PP
Why don’t you test it yourself?
I am asking due to the fact that I am not 100% sure that mixing Beta/RC downloads with Release downloads is not going to cause an issue.
Regardless, I have tested anyway and can confirm it displayed the same error.