Jump to content

justme12

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by justme12

  1. 8 hours ago, pcguy said:

    I just realized that this thread was not in the Eset NOD32 Antivirus section which is the product I am having this issue with. All the browsers currently installed have the same cert installed. Even Firefox release version. Yet the logs continue to get the same old warning message. One option that works is to disable adding the cert to known browsers. That is the least dangerous of the options if NOD32 is installed. It would have been extremely useful if NOD32 could provide a clue on what particular browser install is failing. I am now wondering what else maybe is not functioning properly in NOD32. I Just happened to stumble across this issue last week.

    I even took the drastic measure of running CCLeaner to remove what it felt was errorenous registry entries, rebooted and without starting any web browsers I re-enabled TLS monitoring. Within seconds I got 2 of the same errors in the logfiles. 

     

    I know it is a real PIA but maybe try a Windows Reset or a clean install.  After my initial events, clearing the residual leftovers from

    various installs seems to have worked perfectly. Running Eset on 3 pcs now and no issues.

  2. 12 minutes ago, Marcos said:

    @Justme12: In your case the problem is most likely a non-existing Comodo profile folder C:\Users\psavi\AppData\Roaming\Comodo\CSS\User Data-firefox1 which is, however, referenced in C:\Users\psavi\AppData\Roaming\Mozilla\Firefox\profiles.ini.

    Please back up profiles.ini and with Firefox closed remove the section belonging to the non-existing profile.

    Thank you Marcos.  See my previous post. Looks like Revo uninstaller removed the folder content you mentioned.

    All is fine now.

    "

    I had the same results as you yesterday when I removed FFox.  HOWEVER: today I downloaded Revo uninstaller Pro and removed way more FF reg values than the normal uninstall of FF accomplishes.  THAT seems to have done the trick. I have no more events.

    Though I don't see why one has to go through this whole process.  ESET should install regardless and if there is an issue give notice. Must say, I have lost considerable confidence in the software as from a TLS issue that may have left one vulnerable and never knowing unless looking at the logs and then google researching what they mean. "

    •  
  3. Zip the Procman files and they will be small enough to attach if you want to send to ESET tech.

    I had the same results as you yesterday when I removed FFox.  HOWEVER: today I downloaded Revo uninstaller Pro and removed way more FF reg values than the normal uninstall of FF accomplishes.  THAT seems to have done the trick. I have no more events.

    Though I don't see why one has to go through this whole process.  ESET should install regardless and if there is an issue give notice. Must say, I have lost considerable confidence in the software as from a TLS issue that may have left one vulnerable and never knowing unless looking at the logs and then google researching what they mean. 

  4. 2 hours ago, itman said:

    To begin with, I have never had FireFox installed on any Win 10 build on my PC. It currently has x(64) 1809 installed. As such, I have no old and possibly borked Firefox files and registry entries from prior versions of it, etc..

    To get to the bottom of this current FireFox baloney in regards to EIS 12.1.34, I went to the Firefox web site and downloaded and installed it. I believe the current ver. is 66. I then opened FireFox and checked what certificates were stored in its Authorities certificate store. Eset's root CA certificate was not there as expected.

    I then rebooted the PC to try to simulate the behavior posted in this thread; namely if  "AN ATTEMPT TO ADD THE ROOT CERTIFICATE TO ALL KNOWN BROWSERS FAILED"  alert/log entry would manifest. It did not.

    I then again checked what certificates were stored in its Authorities certificate store. Eset's root CA certificate was there as expected: 

    Eset_Firefox.thumb.png.9d9f6fe19f81b31dc7c9f9dceeb04392.png

    Finally, I rebooted again to see if I could see if Eset would created the  "AN ATTEMPT TO ADD THE ROOT CERTIFICATE TO ALL KNOWN BROWSERS FAILED"  alert/log entry. It did not.

    All this leads me to believe that whatever is causing this behavior on user's PC's has nothing directly to do with the Eset installation but rather, some misconfiguration issued with their current Firefox installation.

    I would advise uninstalling Firefox, clearing out all past remnants of it on your OS installation, and rebooting. Then install the current version of Firefox from the Mozilla web site and repeating the installation steps I posted above. As far as running development or beta versions of Firefox concurrently with Eset, you do so at your own peril; just like if you were running a pre-release ver. of Win 10. 

    Looks like your idea worked!  Uninstalled all ov FireFox with Revo Uninstaller Pro. Rebooted several times and nothing in event log. Reinstalled FF and noted the certificate was not there - rebooted. Certificate now loaded. Nothing in event log.

    Disabled and enabled SSL filter with reboots. Still event log not containing the topics error.

    *** Now what concerns me. Is there a simple way notifying of the event?  How often do people view their logs if they view at all. 

  5. No, just ESET and OSARMOR  of which I had no notifications and also uninstalled. I am using  64 bit FFox, Chrome, Brave ( no beta) Edge and Edge Dev. Win Pro 10. Funny thing is I have an MS Surface Pro tablet with the same setup and NO problem with ESET!!!!!

    As a last resort, I may do this weekend a clean install of Win 10.

    ESET can be complicated with advanced settings, but one should not have to go to this juncture to have the program function.

    If this fails, seriously reconsidering another suite. 

  6. 10 hours ago, Marcos said:

    In order to investigate the issue, please provide:

    - Logs collected with ESET Log Collector when the error occurs
    - A Procmon log from time when you disable and re-enable SSL filtering after a reboot. Stop logging when an error importing the root certificate pops up.

    As requested:  Also removed and reinstalled ESET - no change.  2 events occurred at 11:46:24

    procmon.zip eis_logs.zip

  7. You disabled: but does that not lower your protection and ESET is suppose to be able to provide that.  i.e.

    For SSL communication to work properly in your browsers/email clients, it is essential that the root certificate for ESET be added to the list of known root certificates (publishers). When enabled, ESET Internet Security will automatically add the ESET root certificate to known browsers (for example, Opera and Firefox). For browsers using the system certification store, the certificate is added automatically (for example, in Internet Explorer).

×
×
  • Create New...