Personal firewall initialization failure

On reinstalling ESS 4.2.40 I find I get the above error message, which seems to be a common complaint on this forum. I have tried deleting the suggested folders (the only one I found was the ESET folder in my personal Application folder). I also made sure ESET Firewall wasn't seen in Local Network Properties (it wasn't). What I have not done is the manual uninstall of ESS in Safe Mode because that utility says that can cause harm to my system. Is that all I can do at this point?

I'm considering just getting ESET without the Internet Security, as I don't use Spam controls outside what my email provider offers, and I can just use the XP built-in Firewall.

Running ESS 4.2.40 on XP SP 3.

 

http://kb.eset.com/esetkb/index?page=content&id=SOLN2160

according to the above link that error message means Eset didn't install properly, you can either try the suggestion in the link or run the removal utility is safe mode (it uses a standard disclaimer) and then reinstall Eset

 

I ended up running the manual uninstall in Safe Mode. No change. Any attempt to reinstall ESS 4.2.40 results in the infamous Personal firewall initialization failure. I have resorted to keeping it uninstalled and installing ESET AV, and using Windows Firewall here on my XP SP3 box.

 

I have run the Desktop uninstall of ESS 4.2.40, followed by deleting the ESET folders I'm supposed to delete (only found on in my Application Data folder), followed by a Safe Mode reboot and running the manual uninstall.

None of this helps. Any other suggestions before I simply resort to using NOD32 with a different firewall, instead of ESS?

 

contact customer care?
http://www.eset.com/support/contact#

 

i don't think they can help. i had a similar problem it effected every firewall except windows. i have been through every file, driver registry entry there was simply nothing left behind, seems to me something had been changed but all winsock and network resets failed to fix the problem i ended up reinstalling windows. still waiting for a solution. i don't think eset know the cause.

 

I find that Comodo installs and works just fine after uninstalling ESS and installing EAV, even though ESS can't reinstall successfully now.

 

i didn't try comodo, just outpost pro, my isp (i think is norton) kis and dr web ss pro. all these had errors on install from the firewall.

 

I did have a Windows error message after installing Comodo, but it was easily fixed. My internet connection was "limited" according to Windows. I just let Windows fix that in the Network Connections module. I think an IP address wasn't assigned to my Local Area Connection.

 

Ralvy,

You have a private message.