I just updated Comodo firewall. When I restarted my machine the next time, I got the message:
The active configuration format/version seems to have an old format.
……recommended to reconfigure the new version… old settings will be lost….Would you like to reconfigure it now?
Why does it not say “Commodo Firewall” first, so we know what program is giving the message??? I thought I had some new virus!
Why are the old settings not automatically backed up, with a facility to recover them and use if needs be?
Why is there not a link to a better explanation of what this gobbledygook means?
Exactly the same here - said “No” as I didn’t know what the heck was asking and up pops the Comodo screen. Then Googled for the message and found this forum.
So what are we supposed to do now? I justed restarted the PC - and the message doesn’t appear anymore. So is the “active configuration” going to stay in an old format? What effect does this have on the firewall?
Come on Comodo - you’ve got to do better than this.
Get your developers to think what these messages mean to ordinary users. Of the developers know what what “Configuration Migration” means - they’re too close to the subject to not know. But us users? How are we supposed to know?
“No” is probably the better choice. I chose “yes” (I realised it was CPF, although it took mea while), and I had to teach it all over again about everything, which is very annoying, because CPF is such an intrusive application, asking about virtually everything that happens.
I have also this message poping up every time I start up the PC.
I have uninstalled two times, but the same problem persist, even used the special uninstall program, but the same result is still there.
What is the course?
Is there any solution for this problem?
System. XP PRO SP2 all win updates installed.
Comodo ver. 2.x worked perfect.
I start from ver 2.4, worked perfect, then to the very first 3.0.x?. Uninstalled and reinstalled a version before 18.104.22.168, then uninstalled that version. “Clean” unistalled that ver. and reinstalled ver. 22.214.171.1248 and later updated that ver. to 126.96.36.1990.
The problem message is the same all the way from the first update to ver. 3.x.