Error since update (3.5?) - Error loading CFP.DLL [Merged Threads]

Yes I can and will. Its the firewall folder. Thank you for the help I will come back if further problems.

Please do not try to update again if you want CPF3.5 I would suggest uninstall of CPF3 then install of CIS firewall only.
Or wait for further news reguarding this problem.
Thank you
Dennis

simply put this forum is abysmal, the product is abysmal, support is non-existant, go ahead and ban me make my day. I now have to reinstall XP because I dont want a trace of this poison around. I can see why its free.

I’m running COMODO 3.5.54375.427 on XP SP2 on 2 computers, my son’s and mine. CFP won’t start on my son’s after a Windows Update yesterday but runs fine on mine. Neither has the cfp.dll file in question on any drive. None of the .exe files start except cfpconfg.exe which stopped logging at the time of the update.

Unlike some earlier, I’ve been pretty happy with CFP until this little hickup. I tend to see this type of problem as a part of living with Windows, so get a MAC and take a walk Dawg. LOL

Any help would be appreciated.

I’ve had the same problem - error message regarding CFP.DLL - since installing Comodo on Sunday. It worked fine after install, then did an automatic update and has since refused to start, giving me the same error message. Any help would be much appreciated!

Yesterday I got a Toshiba Satellite Notebook with Windows Vista Home Premium 32-bit w/SP1. I fully patched Vista, then downloaded CFP 3.5 and installed. The install went smoothly and the firewall was running fine after a reboot. I then turned off the Vista firewall. Then I had CFP check for and apply updates to itself. As best as I can remember (it was late), when I hit the Finish button, I got the error about the CFP.dll missing. I rebooted and CFP was no longer running. I tried to launch it manually, and got the CFP.dll error message. I tried to uninstall and got the CFP.dll error message. I tried to launch a web browser and research the problem, but my browser was unable to access the internet. So, finally I did a System Restore to a point prior to installing CFP, turned on Vista firewall, and all was well.

I have been using ZoneAlarm on my desktop, but had wanted to try CFP on the notebook. I hope that this gets resolved soon.

Hi all,

I have also the same problem. It occured after an update of windows and Comodo, not sure what is the cause.

When i inspected the directory: C:\Program Files\COMODO\Firewall i discovered that there were two files:
cfp.exe1
cfpupdat.exe1

I thought that this might be a backup for just before updating, so i made a backup of the two exe’s and renamed the two ‘exe1’ files without the ‘1’.

When i started cfp.exe it worked again, when i tried updating i saw it getting two new exe’s and then this error message:
Error 112: Unable to copy file: guard32.dll. Please try again.

When i looked at the directory again it made two new exe1 files, and after restarting comodo i get the same error.

I did the whole trick again and then started the updater as ‘Administrator’ and that worked :slight_smile: I now have the newest comodo working.

For people that have two computers where 1 is working and the other not, try copying the working exe’s over to the one that doesnt work (as long as it is the same OS). Otherwise try getting a working exe from the same os from somebody else.

I cant attach my files because they are too big.

I hope this helps everyone here.

greetings,
bra1nDeaD

Any update on this? Has it been fixed?

Sorry no nothing yet
Dennis

Hi,

This may be a dumb question, but until this is fixed, is my PC ‘safe’ on the net, or does Comodo recommend that I install ZoneAlarm (say) to protect me?

Thanks,

Alan.

Maybe this will help someone.

I’ve got CFP 3.0 installed on my mom’s computer (running WinXP Home with SP2). I noticed a balloon saying that an update for CFP was available. I clicked on it, thinking that would start a d/l, but when nothing seemed to be happening, I went ahead into CFP and started an update manually. The update d/l’ed and installed, but then I got an error or two. There was an error saying that a log file could not be updated. I can’t remember for sure if I got an error on CFP.DLL at that point.

I restarted Windows and got the error on CFP.DLL. I also noticed that the wireless connection wasn’t working. I thought that that was probably a coincidence, since the firewall didn’t seem to be running, but since I’ve seen others here mention problems with their Internet connections, maybe it wasn’t a coincidence.

I restarted Windows again. Error on CFP.DLL again and it still wasn’t able to establish a wireless connection.

So, following the advice I read somewhere in these forums, I re-ran the 3.0 installation file (CFP_Setup_3.0.25.378_XP_Vista_x32.exe). It told me that CFP was already installed and gave me the option to uninstall. I chose that and the uninstall ran without incident. I restarted Windows and the wireless connection was back. I re-ran the 3.0 installation file and re-installed 3.0. It installed without incident and CFP 3.0 is back up and running (and the wireless connection is still working).

So, if you’re having trouble doing an uninstall using Add/remove programs, you could try running the 3.0 installation file and see if you can uninstall from there. It worked for me.

At some point I’ll remove CFP 3.0 and the Comodo AV and install the new CIS, but for now I just wanted to get things back to normal.

James

So, here’s something I did. If you upgraded and the upgrade failed (aborting aplication error because could not read some dll), delete the new files (backup them), and rename the old ones back to original (from exe1 to exe). If you have the error Could not copy guard32.dll that means that you are not running cfpupdat.exe as an administrator. So, right click on the cfpupdat.exe file in firewall dir an select Run as administrator. There you go, all the files are now copied succesfully. You’re up to date (B). Don’t give up because of this little glitch. It’s the best firewall you’ll get for free.

Thanks a lot!

I had exactly the same problem as kevenl and I took your advice: it works again!

Hey there…1st time posting and please keep in mind, I am not anybody’s MVP…but, I had a similar problem, don’t know why it began, but suddenly I could do nothing with comodo…and no advice I found here helped. I couldn’t activate comodo, couldn’t uninstall comodo, and couldn’t reinstall on top of comodo, because of the ‘missing’ .dll.

Soooo (and again, i am no MVP) I deleted any obvious comodo keys in the registry.

Reinstalled with no issues.

FWIW, this worked for me. (:KWL)

This ‘little glitch’ cost me 3 hours yesterday.

Not too long ago I would have agreed but I have my doubts now…

So u r saying deleting the comodo reg keys will make the installation work?

i can not uninstall th comodo, and it is bloking a port what i badly need
what sould i do ?

now i am really upset !!!

is there a fix for this yet?

i’ve read my way through the web on this and here is what I’ve found and what worked for me (XP/SP2 and no experience in troubleshooting whatsoever):

similar thing happened:
cfp vanished from the tray, clicking .exe or desktop icon gave msg along the lines of: couldn’t find some entry point on cfp.dll…

copied cfp.dll and cfpupd.dll from C:\Docs and Settings%user%\Application Data\Comodo\Firewall Pro\Data\TempFiles\ (where the update files are put) to the program directory (should be C:\Program Files\Comodo\Firewall\ ).
CFP started allright and would let me do an update manually via the misc department.
seems to be running allright now (according to the “about” window it’s version 3.5.55810.432)

the manual that I found recommended to start cfp as administrator after having copied the cfp.dll, run the update and then copy the cfpupd.dll but it worked fine the way described above.

funny thing though: also my avast! AV vanished and wouldn’t start with a similar msg.
I know it’s completely OT but maybe someone has any idea where to look for cure since I couldn’t find anything helpful…

thanks for the suggestion kartfix…that worked for me.

How did this release make it out the door?