After your message, the next time it happened to me, I tried a winsock reset.
It seems to have improved things, as I went longer before it happened again - but it did happen again, I’m afraid.
Maybe it’s a bug in cis 8012 that you can’t fix. Beta 3 runs just as wonderfully on my PC with Windows 11 as it did on my old PC with Windows 10. As always, my PC is well protected. How to uninstall 8012 can be found in the forum, otherwise you will have problems installing the beta version.
You could try setting rules for specific websites in the Firewall/Global Rules, but that’s not very convenient. Or a rule that allows connection for all websites except… etc. - but you get more and more frustrated and switch to another firewall.
@cruelsister has no problems using the latest BETA as I had concerns about using it.
2 Likes
I wanted to update this thread because I finally found the cause of this problem.
“Adobe Crash Processor.exe” - in this case, it was part of Adobe Acrobat.
I have Adobe Crash Processor blocked from internet access. Normally, this is a non-issue, but apparently, it can effectively kill internet access - I don’t know if it does this directly until it can reach its target servers or whether its constant attempts to call home are effectively overloading Comodo so that it can’t process any other network calls.
What I do know is that when I find myself with internet suddenly dead, if I kill the “Adobe Crash Processor.exe” process, my internet is instantly restored.
I just wanted to post this in case others run into the same issue.
And if there’s any chance that it’s overloading Comodo Firewall, then this failure mode should be taken into consideration in future updates.