If i look at event log in firewall, then comodo GUI hangs. Only restart or log out fix it. But if i try it againt, same problem happens. Sometimes hangs sometimes not. 
Hi,
When does gui hang: view firewall events or view firewall events->more?
Please refer to this guide to include more information.
Hi,
I have exactly same problem with hanging-up of GUI.
I experience it on clean install of latest Comodo firewall, it happen right after View Firewall Events is pressed.
Iâm running fully patched WinXP 32-bit, and latest NOD32 v3
Best regards
Jerry
Yes. Itâs same problem . I dicovered, that itâs dependent on Defeat+. If it is switched off. Everything seems to be ok.
- CPU AMD 64bit
- WIN XP SP2 (32bit)
- Avast Home - without resident protection
- Open FireWall event window, itâs seems that Defeat+ must be active to reproduce it⌠then GUI freeze
- Only logout or restart can solve this situation
- âŚ
- Admin account
So is it disabled? Or deactivated permanently (under defense+ options)?
Are there any related entries in defense+ or firewall log?
Do you experience this issue just after you logged in and havenât launched any application yet?
Uncheck everything under defense+ ->advanced->defense+ settings->monitor settings, set defense+ to your working mode (train w/safe, clean pc or paranoid). If problem is gone, start to check one item at time to find out on what stage issue occurs.
Now. I unchecked every option in defence+ setting, but it hang again. It hang in defence+ option menu too after i accept it. When i disable defence+, then it working fine⌠probablyâŚ
There is no event in defence or firewall logâŚ
When i try to change defence+ option (and itâs disabled), then it hangs after i press apply button.
Try to disable some of autorun entries (e. g. with the help of Autoruns).
This way it may help to find out what driver/process/application is the reason of problem.
I killed every process and stoped all unnecessarily services and applications. There was only windows core precesses. But nothing changed.
I click on Proactive defence at first page (Defence+ is active), then i click Apply - without any change. Then if i try to open firewall log, GUI freeze. (:SAD)
What is strange, that all logs are empty.
Are there great amount of intrusion/suspicious attempts that continue to increase at the time you try to open the log?
[attachment deleted by admin]
No. There are only zero values.
Now i have 20 intrusion attempt blocked by firewall, but log still empty.
Itâs rather difficult to find out what is in confict with CF in your case. Try to use some of wininternals utilities (process monitor, file mon). Keep an eye on cfp.exe (CFâs GUI) in this case. Maybe it will give some clue to what is going on there.
Also you may try to reinstall CF from scratch.
Hi all
I would like to stress this problem out again since problem still preserve even in latest stable version of CPF.
I believe that it may have some link to another of my problem on ALL machines - absolutely no logging for some time.
I use CPF v3 on 3 machines and on all of them I had problem with no log at all (not sure from whitch version, but definately start in late 2007). On one machine I did complete reninstall of CPF and problem is even worse. When trying to look into Firewall events (or Defence+ events, doesnât matter) GUI hangs (which is actually problem decribed in this thread). This brand new instalation doesnât even create log file.
I tried to use Filemon and regmon from Sysinternals tools but I found nothing interesting.
The only theory I came up is that since all my machines use non-english Windows version (WinXP SP2) the different name for âLocal Settingâ directory (âData Aplikaciâ for Czech) where logs are stored may cause problems, but this will need confirmation.
Any other ideas?
Best regards
Jerry
Me too. I have also different name for this directory and itâs same name as Jerrys. May be, that problem is right here.
Hi,
I was played around little bit more. And I found this:
- when file cfplogdb.sdb is missing GUI hangs while opening firewall event viewer
- I used Sysinternals utility Filemon to monitor Comodo. I didnât monitor cfp.exe because of too many entries, but I monitor cfplogvw.exe (machine with existing cfplogdb.sdb but no entries (even it have 1,6 MB size)) and I tried to clean all command from menu. See log below. It proves that Comodo in some cases have problem with path and in some cases does not have problem with path, - I marked correct (green) and incorrect (red) path. Also interesting is buffer overflow (blue)
Can any developer please look at that?
Thanks
Jerry
CREATE C:\ ACCESS DENIED JERRY\Jarda
CREATE C:\Documents and Settings NAME COLLISION Options: Create Directory Access: All
OPEN C:\ SUCCESS Options: Open Directory Access: 00000000
CREATE C:\Documents and Settings\All Users NAME COLLISION Options: Create Directory Access: All
OPEN C:\Documents and Settings\ SUCCESS Options: Open Directory Access: 00000000
CREATE C:\Documents and Settings\All Users\Data aplikacĂ NAME COLLISION Options: Create Directory Access: All
OPEN C:\Documents and Settings\All Users\ SUCCESS Options: Open Directory Access: 00000000
CREATE C:\Documents and Settings\All Users\Data aplikacĂ\Comodo NAME COLLISION Options: Create Directory Access: All
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\ SUCCESS Options: Open Directory Access: 00000000
CREATE C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro NAME COLLISION Options: Create Directory Access: All
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS Options: Open Directory Access: 00000000
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS Options: Open Access: All
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS Options: Open Directory Access: 00000000
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNameInformation
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileBasicInformation
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNameInformation
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS Options: Open Access: 00020000
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\ SUCCESS Options: Open Directory Access: 00000000
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS FileNameInformation
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ BUFFER OVERFLOW
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS
CLOSE C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro BUFFER OVERFLOW
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS
OPEN C: SUCCESS Options: Open Directory Access: All
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\ SUCCESS Options: Open Directory Access: 00000000
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNameInformation
DIRECTORY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNamesInformation
DIRECTORY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNamesInformation
DIRECTORY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS FileNamesInformation
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS Options: Open Access: All
OPEN C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\ SUCCESS Options: Open Directory Access: 00000000
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS FileNameInformation
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS FileNameInformation
QUERY INFORMATION C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS FileBasicInformation
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb BUFFER OVERFLOW
QUERY SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS
SET SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS
DIRECTORY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro NO MORE FILES FileNamesInformation
CLOSE C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS
CLOSE C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro\cfplogdb.sdb SUCCESS
SET SECURITY C:\Documents and Settings\All Users\Data aplikacĂ\Comodo\Firewall Pro SUCCESS
CLOSE C:\Documents and Settings\All Users[b]Data aplikacĂ[/b]\Comodo\Firewall Pro SUCCESS
OPEN C:\Documents and Settings\All Users[b]Data aplikac[/b]\Comodo\Firewall Pro\cfplogdb.sdb PATH NOT FOUND Options: OpenIf Access: All
OPEN C:\Documents and Settings\All Users[b]Data aplikac[/b]\Comodo\Firewall Pro\cfplogdb.sdb PATH NOT FOUND Options: Open Access: All
OPEN C:\Documents and Settings\All Users\Data aplikac\Comodo\Firewall Pro\cfplogdb.sdb PATH NOT FOUND Options: Open Access: All
OPEN C:\Documents and Settings\All Users\Data aplikac\Comodo\Firewall Pro\ PATH NOT FOUND Options: Open Directory Access: 00000000
OPEN C:\Documents and Settings\All Users\Data aplikac\Comodo\Firewall Pro\cfplogdb.sdb PATH NOT FOUND Options: OpenIf Access: All
OPEN C:\Documents and Settings\All Users\Data aplikac\Comodo\Firewall Pro\cfplogdb.sdb PATH NOT FOUND Options: Open Access: All
OPEN C:\Documents and Settings\All Users\Data aplikac\Comodo\Firewall Pro\ PATH NOT FOUND Options: Open Directory Access: 00000000
Wonder if anyone is running P2P type software. Seems to generate a perpetual stream of hits that could cause for the GUI not to respond. Does it translate in other sluggishness on the overall system when Comodo appears hung?
Hi all,
here is the solution for this problem (well maybe this is workaround and solution is on the developers of Comodo).
I followed tracks I wrote in my last post. From filemon observation I knew that comodo is looking for log file at wrong path. Instead of looking at
âc:\Documents and Settings\All Users[b]Data aplikacĂ[/b]â which is equivalent for âLocal settingâ in czech windows
comodo wrongly handle czech specific charackter and was looking at
âc:\Documents and Settings\All Users[b]Data aplikac[/b]â
I hope you see the that special letter in your non-czech browser, it look fine in my czech Firefox ;D
So I create such directory a I put old Comodo log database there and be surprised right away I saw all old entries in log in event viewer and after restart Comodo start with regular loging.
GUI hangs are caused when log database is missing and since new instalation wasnât able to create this file because of special character in path name new instalation suffer with GUI hangs.
:BNC (:KWL)
bwt Last entry in my old log was from 5.2.2008 but if I remember well I waited quite a long time with upgrading to new version those days.
I hope that now when it is clear it is bug and solution is clear developers will solve this in next release.
Best regards
Jerry
Please confirm you experience issue with 3.0.20 version.
Yep. You are right⌠i can see it too in file monitor. (:NRD) Problem with directory name. I have version 3.0.20.320 It doesnt hang again after i created directory without czech character.
Version 3.0.20.320 confirmed, I made clean install just to make really sure.
Jerry