Advice Request Comodo Firewall component being ignored

Please provide comments and solutions that are helpful to the author of this topic.
As I understand watching her videos on YouTube, @cruelsister uses Comodo Firewall on Windows 11 with no problem.
When software is not officially compatible with a new OS, either means that it is not officially tested by the organization who releases it or simply is not compatible. When so many people seem to use Comodo without problem on Windows11 chances are it is simply not tested and has a fair chance it will work on your PC with Windows11 (always with the use at your own risk disclaimer).
 
1. When a software credibility relies on a bunch of not expert and amateur users sharing its SUBJECTIVE OPINIONS in the web, it's a big red signal to stay away from that software.
2. If people love Comodo' products, then is better to wait for the announced Comodo updated/upgraded next version, apparently to be launched in few months.
I agree to some extend with your observations and for amateurs not having a propper backup & recovery I agree with you that it is better to wait for a Windows 11 supported version, and yes I am an enthousiast amateur with some HTML and CSS knowledge and basic programming skills (simple visual basic and python) but . . . . .

I would NOT call CruelSister an amateur or non-expert, for the videos she posts you need the contacts and the skills of an expert (otherwise she would not be able to lay her hands on fresh malware and be able to alter them for demonstration purpose).
 
Last edited by a moderator:
Please, allow me some clarifications:

1. I love @cruelsister and I think she shared and she still shares amazing experiences (not just related to Comodo). However, I don't need to trust @cruelsister in order to enjoy @cruelsister.
The forbidden word here is "TRUST"... users always must have critical thinking.
@cruelsister is an anonymous character, no one knows her personally, her work is subjective, no one controls her tests, no one really knows if the information shared by @cruelsister is true or false. @cruelsister never has been objectively validated or confirmed as a security software expert or as a Comodo expert. By the way, not even Comodo has ever made any official acknowledgment of @cruelsister, validating @cruelsister's tests or information.
In this context, the allegation that @cruelsister is an expert, It is just a belief with no basis in reality, just based on "trust"... and remember, "trust" is a subjective matter.
People are free to share opinions, beliefs and their "trusts"... as long as they always remember the difference between "subjective" VS "objective".

2. I do love Comodo, and I used @cruelCF for a long time. When Comodo stopped updates, upgrades, and bugs weren't fixed... I stopped to use Comodo.
It's common sense, the fact I emotionally love @cruelsister and Comodo... it doesn't necessarily means I need to be a fanatic or a fanboy.
Yeah, no doubt, I'll test Comodo again, and I'll love to have @cruelCF again, but only after updates/upgrades.

Final words:
1. With all due respect, "experts" normally are not anonymous characters found in the normal open web posting free software tests. In real world, "experts" normally are known people working at big companies, or they are out-off-the-grid (anonymous but posting in the darkweb etc).
2. If Comodo containment were the panacea for security, all security software would have already incorporated (long time ago) this layer into their own software. The wheel is not invented... it is copied.
I'm sorry, but could you put one more @cruelsister in your post, she may not have been alerted :)
 
@Decopi is expressing valid points and concerns about the software and is not a stalker. We’ve spoken.

Cruelsister’s skills of playing with malware are not under a question mark and I admit I have been stalking her (I stalk many of you on all threads to establish your reputation). She is not going around telling people to deploy Comodo.
From time to time Cruelsister’s posts have been inordinary let’s say.
I like the way she calls various highly-preached, endorsed and promoted Microsoft technologies/products with their real name (garbage), without sugar coating.

Unfortunately in her (Meghan if I am correct)’s videos, I don’t see any fantastic Comodo protection modules/abilities/technologies. I see some user-dependant firewall prompts and various other alerts that can be issued by loads of other products. I am not certain what exactly is being displayed there.

Nevertheless, this is effort and must be respected.

As to Comodo, we have discussed it on another thread. Let’s just say it’s far from brilliant.
 
If we could all just ban the phrases "with all do respect," and "@cruelsister" in this thread that would be greeeeaaat, mmmkay. My eyes are starting to go croseed after reading this thread.
If you think your poor eyes are tired now, from these phrases, just wait till a heated Comodo discussion erupts. You’d wish you never had started it.
 
Please, allow me some clarifications:

1. I love @cruelsister and I think she shared and she still shares amazing experiences (not just related to Comodo). However, I don't need to trust @cruelsister in order to enjoy @cruelsister.
The forbidden word here is "TRUST"... users always must have critical thinking.
@cruelsister is an anonymous character, no one knows her personally, her work is subjective, no one controls her tests, no one really knows if the information shared by @cruelsister is true or false. @cruelsister never has been objectively validated or confirmed as a security software expert or as a Comodo expert. By the way, not even Comodo has ever made any official acknowledgment of @cruelsister, validating @cruelsister's tests or information.
In this context, the allegation that @cruelsister is an expert, It is just a belief with no basis in reality, just based on "trust"... and remember, "trust" is a subjective matter.
People are free to share opinions, beliefs and their "trusts"... as long as they always remember the difference between "subjective" VS "objective".

2. I do love Comodo, and I used @cruelCF for a long time. When Comodo stopped updates, upgrades, and bugs weren't fixed... I stopped to use Comodo.
It's common sense, the fact I emotionally love @cruelsister and Comodo... it doesn't necessarily means I need to be a fanatic or a fanboy.
Yeah, no doubt, I'll test Comodo again, and I'll love to have @cruelCF again, but only after updates/upgrades.

Final words:
1. With all due respect, "experts" normally are not anonymous characters found in the normal open web posting free software tests. In real world, "experts" normally are known people working at big companies, or they are out-off-the-grid (anonymous but posting in the darkweb etc).
2. If Comodo containment were the panacea for security, all security software would have already incorporated (long time ago) this layer into their own software. The wheel is not invented... it is copied.

I invite you to check out my latest video on Comodo IS.
I had 2 BSOD during my test and especially 2 Ransomware that managed to completely encrypt my test machine while in Sandbox.

And "with all due respect" I'm also an appreciated and recognized tester on this forum, just like Cruelsister whom I admire a lot ;)
 
In simple words, any software with lot of unfixed bugs, without official Windows 11 compatibility, and without updates and upgrades... should not be touched.
Well of course. Software that is hobby-project-alas, the CEO is telling you to “love it for what it is or install something else”, is not actively in maintenance — it is common sense to avoid it.

In some cases old, EOL software must be used, as this is the software that businesses use to do their day-to-day task and migrations is expensive.

But in the ocean of antiviruses (every time you turn around a new one pops up), there is absolutely 0 excuse to use sub-optimal software developed on hobby bases.
 
Okay after this group hug of Cruel Sister has anyone something to say about the problem posted being "Comodo Firewall component being ignored"

I think that's been solved, because CPF not officially supporting Windows 11. Without that there's really no point to using it.
 
  • Like
Reactions: Trident
Okay after this group hug of Cruel Sister has anyone something to say about the problem posted being "Comodo Firewall component being ignored"
It’s been said times and times and times again, not sure how many times we will need to discuss the vast number of bugs in Comodo. This time it is apparently in the network filtering driver.

Reinstalling Comodo may fix the issue. Otherwise, other firewalls can be installed or, support may be seeked on Comodo’s forums.
 
But for Comodo, Cruel Sister and Shadowra you make an exception?
I initially registered for the Comodo discussion and even had no plans to stay. I remained because of other people. Comodo discussions are very powerful, It all becomes like a boxing ring. I love challenge. Unfortunately Oerlink is not around now.
 
I invite you to check out my latest video on Comodo IS.
I had 2 BSOD during my test and especially 2 Ransomware that managed to completely encrypt my test machine while in Sandbox.

And "with all due respect" I'm also an appreciated and recognized tester on this forum, just like Cruelsister whom I admire a lot ;)
Speaking of those deserving much respect, your videos and production skills are superb (even without text boxes). However for the Comodo video that was posted, I think the issues with the BSOD's and infections may have been the result of how that malware was introduced to the VM.

As you kindly supplied to me that malware used for verification I actually ran this test twice although it took a few hours to do so without any evidence of systemic infection. This being the case I gave thought on why we have this discrepancy in results. In my testing the VM was set up with sufficient resources although not overkill by any means. Also I broke the 302 (I think that was the amount) into packets of 10-15 (although even running 10 consecutive malware files is not something that any user will even see) and allowed them to run for 5 minutes. After that time the sandbox was reset and I moved to the next packet.

Even though the CF VirusScope module detected and deleted some before they could run contained, there was still left ~160 (if memory serves) and I could easily see how gang-banging a bunch could cause system instability. Actually I did attempt to do just that, first by bleeding resources out of the VM and banging through 50 at a time (didn't ever get to the ransomware), and the system did indeed crash (actually froze).

Anyway, with no criticism of your videos intended (Broń Boże), this may be the difference in the results between us.
 

You may also like...