lvcdkh

I have had this occur with my Windows 7 system, with only Firefox other browsers (IE, Chrome, Opera) all work fine. It appears as if the Firefox profile will actually corrupt the ESET NOD32 installation. The way to fix this is: 1. Uninstall NOD32 completely including system restart 2. Create a new Firefox profile 3. Install NOD32 again 4. Firefox should work again ... at least it did for me. Here is what happens (I have reproduced this exact scenario twice just to make sure because it blew my mind). - open Firefox using "Profile1" - you will get the message "Your connection is not secure" ... blah blah blah - shut down Firefox - startup Firefox using a completely clean profile "Profile2" -- this can be even a fresh install of Firefox with a fresh profile, doesn't matter - you will get the message "Your connection is not secure" - try using a fresh install of FirefoxPortable - you will get the message "Your connection is not secure" - going into NOD32 and disabling web scanning does not do anything to help - at this point Chrome and IE (or even Opera) will work fine - now uninstall NOD32 completely and restart the system - create a clean Firefox profile "Profile3" - Firefox "Profile3" will work fine - Firefox "Profile1" will work fine as well - re-install NOD32 - the newest Firefox profile "Profile3" should work properly still - the FirefoxPortable profile should work fine as well - ... now here's the kicker ... - restart Firefox using the old 'bad' profile "Proflie1" - NOD32 will start blocking all Firefox traffic for any Firefox profile or installation, even newly created ones such as "Profile4" - FirefoxPortable will now have the "Your connection is not secure" message again - uninstall NOD32 - now all Firefox profiles will work again - re-install NOD32 - all Firefox profiles EXCEPT "Profile1" will work again - if you startup Firefox "Profile1" it will corrupt the ESET NOD32 installation and you will have to uninstall NOD32 and start all over again Really, this actually happens. I had to repeat it twice because I didn't believe it. I'm a Senior Software Engineer at a highly secure multinational financial firm so I'm no shmo off the street poking around with this stuff. It seems as if NOD32 flags Firefox for something in the offending Profile1 (only has 4 basic plugins installed and they work on the new profiles as well) but nothing shows up in the logs or gets flagged to the user about this .exe being blocked. Very interesting bug, that's for sure.