After running the test, does CPF, even though the test failed, show a popup later? Ofcourse I am assuming you do not have outpost or any other firewall installed while testing. Even not disabled bu uninstalled.
All testing is done with no other firewalls installed. I have a few extra drives in the main machine & often create a fresh new format/boot for troubleshooting purposes. Other times I will test multiple installations on a single install of Windows, but when I do this I use a very thorough method to clean the registry between installs. CCleaner > RegSeeker > jv16 PowerTools > WINASO, each run multiple times untill they turn up nothing more. Then after these 4 registry cleaners scrub for obvious errors (I've tested many registry cleaners & no others seem to ever turn anything up that these one's don't, hence I've developed this strategy to completely clean a registry, wish it could be accomplished from a single reg cleaner but each misses some that the others don't) I go back through the registry manually & remove all remaining traces of a software & it's parent company... often times it can actually be faster just to use a fresh format/windows install.
I'm not sure exactly what you mean about getting a popup later. Sometimes I get a popup at the time, it just isn't blocking the leak. I don't think I've ever had a popup occur late as another poster has mentioned, indeed that would be very odd behavior to get a popup regarding cpil 2 minutes afterward. In my case I believe it's always popped up on time or not at all, but then there may have been times where I've rebooted before seeing a delayed popup, I usually reboot often between any of these types of tests to clear memory & get a fresh uncontaminated start on the next.
-----
Ok I've tried some other versions again. I will present my findings in as concise & streamlined a manner as possible while still attempting to be entirely thorough. Some of these issues are seperate & preceed the failure of the leaktests, but I will include them in a quick rundown anyhow:
1) The latest version from the Comodo website does not install properly, 006 type error, problem with launchpad installing & such. I also get this with CAVS.
2) 2.1.0.1 from download.com is installing correctly, but activation key does not work, error during activation type situation. Although 2.2.0.11 won't install directly, after updating to 2.2.0.11 from 2.1.0.1, then I am able to activate the key. Ok, so at this point I'm thinking, although it was somewhat of a troublesome (from the average user's perspective) & roundabout way of arriving here, I finally got a release version installed & maybe I can see the leak tests functionally blocked now.
3) I make sure to turn on all monitors manually, at least one of them was off by default, I believe it was component monitor. Then I go under the settings & make sure to check all things relevant such as block trojans or something as such & maybe there was one or 2 other things that weren't checked by default, I didn't take note of the precise names. This is on the old style where the settings are all one page rather than multiple pages as in the latest beta mind you.
4) This time, opposite as before, cpil did not yield a popup & pcflank did. I'm not sure if these characteristics can be exactly pinned down as to which way this occurs in which version, or if the firewall is just yielding varying inconsistent results in general which are not particular to a specific version or test.
4a) Needless to say, the cpil test with no popup failed & the test text was presented in the browser. However, I think it's important to note that on previous tests with the beta a popup for cpil was being presented (at least sometimes), yet the presence of the popup alone or choice to deny cpil did not prevent the test text from being opened in the browser. So it's not just a matter of whether the popup appears, it's the coding that's going on behind the scenes that is allowing the leak to occur even when the popup comes up as it should. Additionally, the popup continues to come up for other unrelated internet access untill the system is rebooted no matter how many times you hit deny. Possibly after some extended period of time it may desist, but I've never had the patience to wait it out for more than about 5 minutes as it quickly becomes incredibly annoying & a quick reboot always solves the problem.
4b) Now on to pcflank, which did yield a popup this time around. I believe there may be some consistency here within the inconsistency, as I recall similar experiences during previous tests within the last week. When pcflank does yield a popup, it seems to block the entire internet in general (or maybe it's just the browser), however, it doesn't seem to prevent the results page from being called up by copying & pasting the link to the browser, where the test text has indeed been leaked & is clearly visible. If not for copying & pasting the link directly at this step, one would get the impression here that the leak had been blocked. Also, the resulting persistent popup problem exists here too, only this time it is not only continually popping up for other unrelated internet access, it is blocking other unrelated internet access as well. Again, this bahavior continues untill the system is rebooted, or if there is a timer on it, I've never had the patience to wait it out as it quickly becomes not only annoying, but internet is unusable/unaccessible as well.
-----
I often times tend to be overly complex or descriptive, I'm very analytical & redundant by nature, but I hope that was concise & articulated plainly enough to get a full picture of everything that is going on. I know sometimes reading what someone else is going through can make your head swim if you aren't seeing or experiencing it in the first person.
And by the way, the screenshots I've listed in this thread aren't posted at a real website or going to be part of any public display in anyway, I've just stuck them on an extra server for purposes of this thread. I may add a meta tag when I get time to stop the search engine spiders from indexing it, or just remove the files after this issue is resolved.
-x
