Unexplained Explorer.EXE crashes...

[Eddy]

Comodo hasn't been just a firewall for a long time.
And even if you think just to install the firewall, it installs some av components as well.

https://blog.kaspersky.com/multiple-antivirus-programs-bad-idea/2670/

For the best protection security software digs itself deep into the OS nowadays.
When multiple security software are installed they are trying to take the same space in the OS and it is not uncommon to lead to conflicts.

[Alex Farlie]

(Adding additional information.)

Having had to reinstate Comodo after some erratic internet behaviour, I found the Explorer.exe fault reccured. I then did a a check of Shell extensions, and found that Cavshell.dll had re-enabled itself. Disabling the relevant shell extension seemingly removed the Fault condition.

So as I said earlier I think the fault is either a bug in Cavshell, or it's an interaction conflict between Comodo and Avast.  I lack the tools to dig into this further, but would appreciate it if
more effort was made between Security software providers, so that they communicate interaction issues and bugs. Perhaps this is something that could be raised by the Avast developers with Comodo?  I consider a silent installation/re-enable of shell extension which when Avast is also running causes a major part of Windows (explorer) to crash to be a bit concerning, and something someone with less honurable intentions might try to exploit.

[bob3160]

(Adding additional information.)

Having had to reinstate Comodo after some erratic internet behaviour, I found the Explorer.exe fault reccured. I then did a a check of Shell extensions, and found that Cavshell.dll had re-enabled itself. Disabling the relevant shell extension seemingly removed the Fault condition.

So as I said earlier I think the fault is either a bug in Cavshell, or it's an interaction conflict between Comodo and Avast.  I lack the tools to dig into this further, but would appreciate it if
more effort was made between Security software providers, so that they communicate interaction issues and bugs. Perhaps this is something that could be raised by the Avast developers with Comodo?  I consider a silent installation/re-enable of shell extension which when Avast is also running causes a major part of Windows (explorer) to crash to be a bit concerning, and something someone with less honurable intentions might try to exploit.

A simple solution is to forget about Comodo.