HIPS Dysfonction since Windows Migration

Xstof25 · June 9, 2019, 6:23am

Hi everyone,

My configuration is: Windows 10 1903 X64, Comodo 12.0.0.6818.
Since the migration of windows I have a dysfunction of COMODO HIPS (HIPS in safe Mode). It blocks a lot of programs that before the migration of windows were not. For example Dashlane, Outlook, Adobe DC, searchProtocolHost, Comodo Dragon etc. etc. Even when unlocking them they come back every second or every time I reuse them.
I uninstalled COMODO completely and reinstalled but I still have the same problem.
What can I do now?

Best Regards
Xstof25

R2C2 · June 9, 2019, 8:20am

EricJH post:269:

There is a bug with CIS on 1903 where CIS will log memory access being blocked where there is no memory access happening. It is a usability error; it’s not an error that has impact on functioning of programs nor is it a security risk.

CIS always has blocked memory access to its processes as part of how CIS protects its self. The blocking gets logged in HIPS logs.

Now with Blocked Applications this blocking is brought to the front and confuses people. Blocked Applications is not very informative and doesn’t inform about the nature of a block. It was probably introduced to make managing certain blocking actions easily visible and manageable. But Blocked Applications overplayed its hand by brining memory access to the front, offering to unblock memory access where it is not capable of doing so.

This freaks people where there is nothing to worry about. 99,9999% of the programs work normally when they don’t get memory access to CIS processes.

Just_An_User · June 9, 2019, 11:30am

Same problem here, and my computer is sooo slow because of this. I will give only another chance with the next update, if that doesn’t solve the issue I will uninstall COMODO indefinitely .

prodex · June 9, 2019, 12:42pm

Read this and…

EricJH post:269:

There is a bug with CIS on 1903 where CIS will log memory access being blocked where there is no memory access happening. It is a usability error; it’s not an error that has impact on functioning of programs nor is it a security risk.

CIS always has blocked memory access to its processes as part of how CIS protects its self. The blocking gets logged in HIPS logs.

Now with Blocked Applications this blocking is brought to the front and confuses people. Blocked Applications is not very informative and doesn’t inform about the nature of a block. It was probably introduced to make managing certain blocking actions easily visible and manageable. But Blocked Applications overplayed its hand by brining memory access to the front, offering to unblock memory access where it is not capable of doing so.

This freaks people where there is nothing to worry about. 99,9999% of the programs work normally when they don’t get memory access to CIS processes.

this:

EricJH post:251:

Blocked Applications will amongst other things register when a program gets blocked when it tries to access CIS processes in memory. It registers CIS protecting its self. It has always done that since its conception as Comodo Firewall v3 back in 2006. CIS up to this day log memory access attempts in HIPS Logs which most mortals do not look at. 99,999% of the programs that try to access CIS processes in memory work without a glitch without getting memory access.

Blocked Applications is not capable of unblocking memory access confusing the users further and making them worried even more. It is my strong opinion that Blocked Applications should be removed from the UI. It simply creates too much confusion.

To add to the confusion. With 1903 there is a bug with which CIS will report memory access by 32 bits programs where they are not asking for memory access.

In short. 99,99999% of the programs will work without a glitch when memory access to CIS processes is denied. Blocked Applications is not thought through enough and creates confusion making users think something is wrong where it isn’t. Allowing memory access introduces an element of risk so we only advice to allow memory access when an application needs it to function properly.

DecimaTech · June 9, 2019, 12:59pm

Please use the search feature as this is a known issue.

Citizen_K · June 9, 2019, 1:41pm

Your problem may not be linked to the erroneous logging. Please start a separate topic providing version information about Windows and CIS and how you updated CIS. Also post screenshots of the HIPS logs and Containment logs.