I posted at Wilders about what happened to my CPF 2.4,but i think it is better to post here as well:
[quote]…following the attempted creation of an Acronis Image which didnt go well while in Windows…
I was using CPF with highest Level of Alerts
Application Behaviour temporarily completely OFF
After a BSOD ,some cleanup and repeated reboots i have a look at the Applications Monitor and i can see only less than 1/5th of the previous rules…
I notice Superantispyware update rules are missing,so i just tried to make an update to see if rules would stick or not…made the update,BUT the allowed rules wont stick and remain anymore…
Whats worse i noticed that now there is a final rule which allows EVERYTHING …no info at all…
i think it comes from Comodo and not from any hacker or rootkit…
i lowered the Alert Level to just High (it had worked fine like this before)
and removed the Unknown rule ,but it keeps coming back…
I’ll try now to lower the Alert Level to Low to see what happens…
otherwise i think i’ll have to reinstall the darn thing…
Sorry-was unable to insert an image of the rule here so i’ll describe it:
In Application Monitor -the only surviving rules belong to Avira Antivir and Boclean Update- the seventh Rule ,which Icon is the system-like,square,white symbol
is Destination [any] Port [any] Protocol :TCP-UDP OUT Permission: Allow.
Details-
Security Risk: Unknown
Connections : Unlimited
Path :
Parent Path : -
Description : Unknown
Invisible : Allow
Version :Unknown
I tried to delete this rule,but it kept coming back.
I tried to modify this Unknown application by changing in ‘Invisible’ from Allow to Ask and it remained that way.
I’ve lowered the Alert Level to LOW to no effect,new Applications are not listed there anymore.
As i have in the last couple of months changed the Alert Level 3 or 4 times and i had the habit of putting Application Behaviour on the OFF whenever installing or making Images, i gather CPF 2.4 cannot sustain repeated changes in config.
If you stop Application Behaviour whenever you got to install or make an Image and/or you change Alert Levels you are prone to instability in the Applications department so that if you suffer a BSOD of sorts you risk loosing some of the rules…
I remember now that when it happened i wasnt even connected as i was Creating a second Acronis Image with my ethernet cable plugged off,
so my non-scientific explanation is that Rules in Application Monitor were already in a non stable situation and waiting for an excuse to disappear away…
I would like very much to know from someone in the know if that file-Rule in Application Monitor is indeed a Comodo file albeit prompted by abnormal behaviour.
I think i will have to reinstall Comodo anyway.