Jump to content

Rian Visser

Members
  • Posts

    5
  • Joined

  • Last visited

About Rian Visser

  • Rank
    Newbie
    Newbie
  1. Matt, I had a similar issue. I went to Eset's main site, downloaded their installer again and re-installed the software. It worked for me and the errors disappeared.
  2. 10.0.390. Eset keeps telling me I am up to date with this version. Edit: I downloaded the installer from Eset's website again and installed 10.1.204. Everything seems to work now.
  3. Hi everyone, mine is also giving the Firewall, Anti-Phishing and Web & Mail Protocol inactive errors. I am from South Africa and on Wednesday last week I received a notification from Microsoft about a new update coming for Windows 10. The same day the update was downloaded and I had to reboot my system. The update was done and suddenly Eset started giving this error after working perfectly for a long time. The update I had was to Windows 10, Version 1703. This is my new system information: Servicing option: Current Branch (CB) Version: 1703 OS build: 15063.138 Availability date: 4/11/2017
  4. Thank you Marcos Yes, Eset was working perfectly for some time now. I am from South Africa, running Windows 10 Professional and on Wednesday last week I received a notification of a new Windows update on the way. The same day it seems it was downloaded and I needed to reboot my system. The update was completed and right after that the Eset message I attached above started appearing. The update I had was to Windows 10, Version 1703. This is my new system information: Servicing option: Current Branch (CB) Version: 1703 OS build: 15063.138 Availability date: 4/11/2017
  5. Hi everyone Not sure if anyone else experienced the same problem, but last week Windows rolled out a new update, which I installed. After the update, Eset gives the following 3 errors: 1. Anti-Phishing protection is non-functional 2. Personal firewall is non-functional 3. Web and mail protocol filtering is non-functional The anti-phishing message says some program modules are not active, while the other two errors required a restart. Nothing works though, even after restarts. I am attaching a screenshot of the errors.
×
×
  • Create New...