opti1

Sorry, my bad. I forgot to include that all three PCs are running Windows 7 Home Premium SP1 64-bit.

On March 8 Firefox 58.0.2 started to not load pages most of the time on all three of our PCs that are running ESET NOD32 11.0.159.9. Before that all three PCs had been humming along just fine for a long time. Shortly before I began to notice this problem I began seeing TLS messages from Firefox in the lower left corner where it shows you what it is doing as it loads the page. I have temporarily disabled ESET and I have temporarily turned off TLS protection but neither fixed this problem. Was there an update on or around March 8 that may have caused this problem or is it just me? Thanks for any insight, suggestions, or help you can provide!

NOD32 just gave me a message that an update to 9.0.425.0 was ready to install. I went ahead and let it install and reboot and everything appears to be fine. I have searched the ESET site and support community but I cannot find anywhere that says what this update to 9.0.425.0 is about. Does anyone know? I'm running Windows 7 Home Premium SP1 with Windows Updates current through the December 2017 rollup. Thanks!

Thanks for your response. The pop up window I got was much bigger than the one you show above. It had a link, but I was reluctant to click on it for fear of starting the installation process. I would like to confirm what version it wants to install. I will investigate when it pops up again.

I received a pop up notification that there is a new version of NOD32 antivirus available to me. How can I find out what version this is that is waiting? Also, what is the current most stable version of NOD32 AV for Windows 7 Home Premium 64-bit? Thanks!

Given that alternative I prefer to stick with NOD32 v9.0.349 which is newer. Since it seems I cannot get NOD32 v9.0.381 to work with Malwarebytes products on my ThinkPad X230 I'm wondering how much I lose by not upgrading NOD32 to v9.0.381 or v9.0.386 or v9.0.386 (which was pulled yesterday). Or I can stay with v9.0.349 and wait for v10 which it sounds like is imminent. Very strange, though, that v9.0.381 works fine with all the same Malwarebytes products on our two desktops, all running Win7 Home Premium 64-bit . . .

I seem to have a conflict between ESET NOD32 v9.0.381 and the premium versions of Malwarebytes Anti-Exploit and Anti-Malware on my ThinkPad X230. On two desktops with all the same software and versions as the laptop I do not have this conflict, they work fine. Both desktops and the laptop are running Win7 Home Premium. On the ThinkPad, when I run NOD32 v9.0.349 everything works fine. But when I upgrade to v9.0.381 neither Anti-Exploit nor Anti-Malware will auto start at startup and Anti-Exploit will not run when I try to manually start it, although Anti-Malware will. I also can no longer open any software that is protected by Anti-Exploit, such as browsers (Firefox, MSIE) and Acrobat Reader. If I restore the laptop to a date when I was still running NOD32 v9.0.349 everything is fine again until I update NOD32 to v9.0.381. Then the problem is back. How should I proceed with trying to get NOD32 working again with these Malwarebytes products on the ThinkPad?

Good news. I updated from 9.0.349 to 9.0.375 and the failure to add root certificate warning no longer appears. I was about to manually download the upgrade since I wasn't getting it through the Check for Updates button in ESET, but one more try found the update.

Thanks for confirming. Unfortunately this did not resolve the problem for me. I still get the warning message on each reboot\logon on my standard account. However in the meantime I noticed that I do not get the warning on my Administrator account nor on the two other standard accounts on this PC. Therefore it appears there is something different about my standard account that is triggering this warning. I did check and I see that both Firefox 45.0 and IE11 show the ESET certificate with a date of 02/28/2016 which I think is the date I upgraded from v8 to v9. Looks like I will have to find the time to follow Marcos's instructions and send him what I find.

Just so I understand . . . is this correct? 1. put SSL / TLS filtering into interactive mode 2. reboot PC (not just restart ESET NOD32) 3. accept all the scan questions as they come up after reboot PC 4. wait about 5 minutes, then reboot PC again (not just restart ESET NOD32 again) 5. put the SSL / TLS filtering mode back to automatic Thanks!

Having the same issue here on a Dell Studio XPS 8100 with a fresh install of NOD32 9.0.349 over NOD32 8 on Win7 Home Premium SP1 64-bit. I got the error during the installation of v9 and now also at each start up. I'm running Firefox 44.0.2 and IE11 with all the latest updates, no other browsers. On a Thinkpad X230 I also upgraded v9 over v8 and I'm running the same browsers and versions and do not get this error. EDIT - I should add that I'm running No Script in Firefox on both the Dell and the ThinkPad, I get the error on the Dell but not on the ThinkPad.

Ok, great. Thanks Arakasi and SweX for your quick responses!

Sorry to ask what should be answered in a FAQ (if it isn't already, although I couldn't find it anywhere). I am about to install NOD32 2014 on a Windows 7 Home Premium PC that currently has MSE 2, MBAM 2, and I'm using the Windows built-in firewall. I know that I need to uninstall MSE before I install NOD32, but what about MBAM and Windows firewall? Is it enough to turn off real-time protection in MBAM or should I uninstall it then reinstall after I install NOD32? Should I turn off the Windows firewall and then turn it back on after I install NOD32? Oh, and what is the differencew between NOD32 2014 and NOD32 7? B) Thanks!