Kevin160967 0 Posted November 16, 2015 Share Posted November 16, 2015 System is Windows 10 x64. Was previously using the latest version Eset 8 without any problems. Upgraded today and rebooted. First sign something was wrong was that the Eset GUI did not appear for about 5 minutes, at which point I got a messge from windows saying neither ESS or the windows firewall was active, and would I like to switch one one. I said yes to ESS. I then opened event viewer to see if I could see any issues. It opened okay, but hung when I tried to drilldown on a category. After about 30 seconds I got a HIPS message saying that MMC was trying to access a registry location. I okayed it, and said to create a rule. Both the ESS GUI and the event viewer were now hanging. After about three or four minutes I got a message saying ESS was unable to create the rule. ESS was still frozen. I reset the computer and tried again, but got the same delay on startup. I've tried disabling HIPS but that hasn't helped. I'm also getting freezes opening web browsers, and using GForce Experience to do a driver update. Any troubleshooting suggestions before I downgrade to v8? Kevin Link to comment Share on other sites More sharing options...
Administrators Marcos 5,241 Posted November 16, 2015 Administrators Share Posted November 16, 2015 You wrote that you got a message from HIPS asking you to deny or allow a registry operation. Please uninstall v9 and install it from scratch while using default settings, ie. without switching HIPS to other than the default automatic mode and without any custom rules. Link to comment Share on other sites More sharing options...
Kevin160967 0 Posted November 17, 2015 Author Share Posted November 17, 2015 Hi, I ended up uninstalling and reinstalling v9 because my system was essentially unusable. On uninstalling the freezes were no longer occurring, but the firewall component failed to start. I tried uninstalling and reinstalling again (with resets in between), but got the same. There was nothing in the ESS logs to indicate what the problem was, just a message under events that the firewall service couldn't start. There wasn't anything in the windows event logs either. I ended up reinstalling ESS 8 which is working perfectly except that somewhere along the way I lost all of my firewall settings and (my fault) I can't find a recent backup of them. Feeling a bit frazzled by the whole process to be honest. If I try again later in the week, where should I be looking for more information on what is causing the firewall to fail to start? I'd rather go into it knowing what I'm looking for. Kevin Link to comment Share on other sites More sharing options...
ESET Staff Gonzalo Alvarez 66 Posted November 17, 2015 ESET Staff Share Posted November 17, 2015 Hi @Kevin160967, Your system behavior is not the normal users ones I saw. I suggest you try this hxxp://support.eset.com/kb2289/, removing the ESET firewall from adapters first, save network config and later, do the ESET Uninstaller on Safe Mode. While on SafeMode, delete temporal files. Link to comment Share on other sites More sharing options...
Recommended Posts