Jump to content

spotter4me

Members
  • Content Count

    20
  • Joined

  • Last visited

Everything posted by spotter4me

  1. Hello Gonzalo and Marcos: I resovled the issue. I uninstalled NOD32 and manually deleted all Eset files on my drive. I also maually went through the Registry and deleted all Eset keys. Interestingly, when I was trying to deleted all Eset files on my drive I could not delete some files. Windows said the files could not be deleted and were corrupted. So I ran Checkdisk and many repairs were implemented on my C drive. I then reininstalled NOD32 v349 and the taskbat icon appeared at boot up. No delays. Everything runs fine now. It looks like to me that NOD32 was trying to access corrupt files
  2. Hello: Recently, I have noticed that the NOD32 system tray icon does not appear at boot up even though it is set to do so. After several minutes, it finally launches and the NOD32 program window strangely pops up on my monitor. In the past, when things were working correctly, the Icon would just appear at boot up and that was it. No program window would launch unless I clicked on the icon in the system tray. Furthermore, a Windows error reporting icon on the system tray tells me that the program is not running after boot up. Once the NOD32 icon appears on the system tray and the NOD32 pro
  3. Hello Marcos: I am having the same problem. EGUI.exe does not load right away at startup with Windows 7 64 Bit. Ekrn.exe is running though. It does eventually startup, but many minutes later. Well...............interestingly after just upgrading to latest version 9.0.349.0, EGUI.exe now loads properly at startup, and the NOD32 icon now immediately appears on my Windows 7 taskbar.
  4. Hello Marcos: I am having the same problem. EGUI.exe does not load right away at startup with Windows 7 64 Bit. Ekrn.exe is running though. It does eventually startup, but many minutes later.
  5. First of all, if one is having issues with a specific software and does not want to provide the vendor with logs because of insufficient trust, he or she cannot expect the issue to be looked and eventually fixed. Providing logs is the most essential things that ever vendor requests when tackling technical issues. The fact that you had never had issues with SSL scanning until recently can be caused either by the fact that SSL scanning had been disabled by default before v9, a software clashing with ESET's protocol filtering was installed in the mean time or a sort of bug was introduced in a r
  6. First of all, if one is having issues with a specific software and does not want to provide the vendor with logs because of insufficient trust, he or she cannot expect the issue to be looked and eventually fixed. Providing logs is the most essential things that ever vendor requests when tackling technical issues. The fact that you had never had issues with SSL scanning until recently can be caused either by the fact that SSL scanning had been disabled by default before v9, a software clashing with ESET's protocol filtering was installed in the mean time or a sort of bug was introduced in a r
  7. This is a known issue of the current v9 that will be addressed in the upcoming v9 service build soon. The issue should go away shortly after the operating system has been loaded and all dependent services started. This should be indicated by turning the protection status from red to green. It's just a cosmetic (gui) issue that doesn't affect any functionality. As for the problem opening secured websites, we'll need you to do the following: - temporarily enable advanced protocol filtering logging (APF) under Tools -> Diagnostics - download, install and run Wireshark - start capturing net
  8. Well, I just tried to sign into Ebay and the secure page could not be displayed. The Protocol Filtering issue is still present even after switching to regular updates and Internet Protection Module 1226.2 20151127. I guess that is why I was still getting the Protocol Filtering warning message at boot up. Eset needs to look into this. This still appears to be an Internet Protection Module issue?
  9. OK, so you're on Pre-release updates. If you decide to revert to Regular update, you'll have Internet protection module: 1226.2 (20151127) which seems stable and works fine. Ok, I will switch to Regular updates and report back with my results. Thanks OK, I just switched over to Regular updates, everything seems to work as far as accessing web sites and secure websites. The only thing left of concern is that the notification message still appears when I boot up each time. It states that "Protocol Filtering Problem............An error ocured while starting proxy server. Analysis of appli
  10. OK, so you're on Pre-release updates. If you decide to revert to Regular update, you'll have Internet protection module: 1226.2 (20151127) which seems stable and works fine. Ok, I will switch to Regular updates and report back with my results. Thanks
  11. Windows 7 64 Bit, and the Internet Protection Modue I have is 1238 dated 11-24-2015. The SSL Problem appears to occur with Firefox 42 and the latest IE 11. Slimjet browser which is a Chrome based browser does not appear to be affected. For instance, I cannot sign into this Eset forum site using Firefox and IE, but I can with Slimjet.
  12. Hello Marcos: I tried your fix and it did not work. However, after playing around a bit I found I can browse sights with Protocol Filtering Checked and SSL/TLS UNCHECKED. If I check SSL/TLS I can enter some secure sites, but not others. As an example, I cannot log into my AMEX account. I get the following message: The connection to the server was reset while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. UPDATE: OK, Un
  13. Please Note: In my last sentence above, I meant to say: "With this being UNchecked, I cannot engage the Internet Protection options of Web Access Protection and Anti-Phishing Protection." Thanks for your reply Marcos. I will try your suggestions later today, and report back tonight or tomorrow.
  14. Hello All: It appears that the Internet Protection Module in NOD32 Antivirus 2016 is once again affecting web pages using Firefox 42 (have not tried other browsers). When Protocol Filtering is checked, secure websites are not displayed. When I uncheck this, everything works correctly. As I recall, this was the same thing that occurred soon after the release of the last version of NOD32 (2015 v8.0). The cause was the Internet Protection Module. It was eventually corrrected by Eset. Does anyone know when the current Internet Protection Modue issues will be corrected? With this being
  15. Hello Gerix: I too had some update nags (for New Signatures) and confirmation messages after virus signatures were updated. Click to Open NOD32 9 and then click the SETUP tab on the Left. In lower left of NOD32 window click on ADVANCED SETUP. Now click on the UPDATE tab on the Left. Click "+" Button for BASIC and uncheck "Disable Display Notification After Sucessful Update." Under BASIC you will see UPDATE MODE. Click "+" sign to open this and UNCHECK "Ask Before Downloading Update." Signatures are now Automatically updated in the background with no over
  16. Hello NOD32 Support Representative: I just started getting this warning today 13 DAYS out from expiration. The taskbar icon is now a triangular orange with an exclamation point in it, and there is a BIG "Eset NOD32 Requires Your Attention" in LARGE lettering at the top of the Home window. I NOW have to endure this NAGGING for 13 days. This kind of NAGGING is NOT NECESSARY given that one sees the License expiration under the Basic Overview heading in the HOME window when one opens NOD32. PLEASE remove this renewel nag and stop treating people like IDIOTS that need to be herded like shee
  17. Hello Peter: I am not sure what Eset did here recently, but the issue has finally been resolved with the latest version of NOD32 released on May20 (v7.0.317.4) and/or the latest Internet Protection Module v1130 dated 6/5/2014. Firefox and other browsers now work with Internet Protocol Filtering checked! And I do not even have to exclude the browsers. Works just like NOD32 6 did! Guess I can now try to see if scanning SSL Protocol will work, although I never had that checked in previous versions. I also noticed that moving around the GIU is quicker with less latency, expecially when
  18. Hello Again Peter: Automatic updates finally installed Pre-Release Internet Protection Module 1097 today. Unfortunately the problems with browsing web pages persists in all 3 browsers as described above. 1097 did not fix the issue so it's back to the drawing board. Any other suggestions would be appreciated. S.
  19. Hello Peter: Thanks for your reply. For some strange reason I still only have Internet Protection Module 1094 installed. I do have Pre Release Updates checked but 1094 was never updated automatically. Is there a way to manually install this? Do you have a link? I will get back to you to see if 1097 solves the web browsing issue once I can install and test 1097.
  20. Since installing the latest version of NOD32 Version 7, I am unable to enter most secure web sites. On the rare occasion I do get in, subsequent pages on the secure site do not display properly. This also generally occurs with most unsecure web pages. Web pages do not display properly, or do not display at all. This occurs in all 3 browsers that I use (Firefox 26, Chrome 31, and IE 10). When I uncheck Protocol Filtering and reboot, everything then works normally in all 3 browsers. And YES........I have "Do not Scan SSL Protocol" checked. Additionally, HIPS option is checked. The issue
×
×
  • Create New...