I was going to post again in this thread but for some reason I can’t reply to that thread anymore. ???
In short: I got another cfpres.dll error, very much like the one I reported in the other thread. System setup is the same as what I posted in the other thread, except that I’m now using v.3.0.18.309.
Key point: I did NOT get the error upon booting up my machine. Instead, it happened when I was starting to install a Windows Defender update. I don’t let Windows do updates automatically, and so Windows Defender updates need me to initiate the download and then the install process. The CFP error happened just after I had started the WD update install process. As noted in the other thread, I got the error before when installing a Quicktime update.
The first error message said “Error 0x0: failed for …\Application Data\Comodo\Firewall Pro\Data\ResFiles\fw_alert_yellow_L.png”
The second error message said “ERROR: Error while extracting resources from C:\Program Files\Comodo\Firewall\cfpres.dll . Aborting application”
After the second error, CFP killed itself. :o
The error happened yesterday morning; I installed the 3.0.18.309 update two nights before that. I think there was one other Windows Defender update between those two events.
I"ve gotten the same error with two seperate clean installs withing a few restarts. It’s becoming a big issue. Comodo is failing to start pretty much every time. What is causing this?
Following is the reply I got from the technical support dep. of COMODO.
Please do the following to Manually uninstall CFP:
Do the following steps in Safe Mode(Press F8 when the system boots up
to login to the Safe Mode):
Step 1: Disable the firewall by right clicking firewall icon on the
system tray and select Exit
Step 2: Disable the comodo helper service
Click->Start->Run-> type services.msc…
On the services window Right click on comodo firewall pro
helper service-> Properties ->Disable
Step 3: Open Registry and delete the following entries. Before doing
this please take a backup of the registry through file-> export.
*Right click and Delete the entry COMODO Firewall Pro under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Right click and Delete the *entry *Firewall Pro *under
HKEY_LOCAL_MACHINE\SYSTEM\Software\Comodo\ and
*Right click and Delete the entry *1 under
*HKEY_LOCAL_MACHINE\SOFTWARE\ComodoGroup\CDI\
Step 4:Restart the system
Step 5: Go to the Installation Folder C:\program files\comodo\ and then
delete the Firewall folder
Step 6: Delete the file *guard32.dll *under C:\windows\system32\
Step 7: Delete the following files cmdhlp.sys, cmdguard.sys and inspect.sys under C:\windows\system32\drivers
Step 8: Delete the 'Common’ and ‘Firewall Pro’ folders under
C:\Documents and Settings\All Users\Application Data\comodo
Step 9: Delete Firewall Pro folder under C:\Documents and
Settings\Administrator\Application Data\Comodo(Administrator can be
your user account name or the user account through which CFP is installed)
Step 10: Restart the System
Install the new CFP 3.0.18.309
I hope this will resolve your issue.
Regards
Mark
Technical Support
i get similar errors after logon. heres a temporary solution that may work for many of you until developers find a way to fix this properly. seems that this version of Comodo cant always handle loading so early in the boot process… you can untick Automatically start the application… under Misc->Settings. Navigate to All Programs->Startup, right click, choose Open all users and paste Comodo shortcut there. If you want it to start minimized to system tray - go to shortcut properties and under Target add -h like this: “C:\Program Files\COMODO\Firewall\cfp.exe” -h
This happens when something intercepts CFPs ability to extract its files on the fly. It may be because of an AV blocking one of the graphics files or a file system failure.
First please scan your disks for errors to see if anything is wrong with your filesystem. If the issue persists, and your filesystem is FAT, in the most cases, converting FAT filesystems to NTFS filesystems would provide a better filesystem and remediate the issue.
Note that this is most probably related to an AV software(Or similar) blocking CFP to create its resource files.
We would really appreciate if you are able to play with your AV software and try different scenarios.
Ofcourse we will be working on the issue and fix if there are any issues.
Hi Guys,
We are coming up with an update this month to minimize the possibility of this error. Although file extraction is simply creation of file operation, but we have added extra checks to ensure that there are few re-tries and additional checks before we really decide to abort application.
Will update here to everyone to re-try once we have update out.
