Failed to read firewall configuration

[Teazle]

still have this error.

It comes the moment i try to open ESS or restart computer.
Going into options makes it come again.
Trying to edit rules makes it come yet again and lock me inside Rules dialog.
Scanning doesn't work, filtering doesn't work.

I wouldn't have minded some more assistance, but i guess i just have to stick with nod32 and not have a firewall.


for reference, see these:

http://www.wilderssecurity.com/showthread.php?t=190164
http://www.wilderssecurity.com/showthread.php?t=186601
http://www.wilderssecurity.com/showthread.php?t=187234

Had a few mails going back and forth nearly a month ago. then it unfortunately stopped.

[Teazle]

this is an extremely shameless bump to try to get attention to my problem, so that it can be fixed anytime within the closest 18 years.

[kC_]

uninstal, reboot...

and then delete these folders
C:\Documents and Settings\YOURUSERNAME\Application Data\ESET
C:\Documents and Settings\ALL USERS\Application Data\ESET

then re-instal 3.0.566.0

[GaryRW]

{QUOTE-> this is an extremely shameless bump to try to get attention to my problem, so that it can be fixed anytime within the closest 18 years. <-QUOTE}

See if this helps....

http://www.wilderssecurity.com/showpost.php?p=1116454&postcount=16

[tagwar]

i hope this working

[tagwar]

{QUOTE-> uninstal, reboot...

and then delete these folders
C:\Documents and Settings\YOURUSERNAME\Application Data\ESET
C:\Documents and Settings\ALL USERS\Application Data\ESET

then re-instal 3.0.566.0 <-QUOTE}


i try 2 times and it\s not working

[kC_]

re-instal windows. that solved the only major issue i had with ess

[jimsoar]

This appears to happen if you have installed ESS uninstalled and then installed Nod32 antivirus 3.0. Easy way to get rid of message run winsockxpfix

[Marcos]

The firewall configuration is stored in dat files in C:\Documents and Settings\ALL USERS\Application Data\ESET. It can get corrupt if the computer is shut down improperly. I had this problem once a while ago; uninstalled ESS, deleted all eset folders in the "documents and settings" folder, reinstalled ESS and since then it's been working like a charm.

[sheepeee]

I had the same problem. But after I updated the virus signaturebase (and maybe the sw-components too) the problem was solved. (I don't know the reason)