rlcronin

Please create 2 Wireshark logs, one with http filtering enabled when the issue occurs and the other one with http filtering disabled when your router's admin pages open fine. When done, upload them to a safe location (e.g. Dropbox, Skydrive,...) and PM me the download link. Traces taken. PM sent. Thank you. -- bc

I am still having issues with web protection messing up access to my Asus RT-N66U router's admin pages (as reported in the original beta thread). I uninstalled the beta and went back to v6 (again) and all is well. This does not bode well. -- bc

Using Chrome as well with NOD32 7.0.28.0 without any issues The issues I had were with the Chrome beta channel and only happened when I went to webservers in my own subnet (e.g. to my router at 192.168.1.1) or when I put my PC to sleep, later woke it up and then tried to open Chrome. I'd get a blank window that'd never connect. The local subnet issues I solved by adding the 192.168.1.x range to the protocol filtering exceptions. The sleep/resume issues I never solved and were what led to me reverting to 6.x. I did not try to revert to the Chrome stable channel, so I've no idea if that would have helped. -- bc

I had to uninstall the beta. Too many issues with my default browser (Chrome). All the issues went away after I reverted to v6. -- bc

With all v7 settings at defaults, the web UI for my ASUS RT-N66U router (running the AsusWrt Merlin firmware) is extremely sluggish. Chrome (Version 28.0.1500.71 beta-m) is my default browser. Some pages never finish loading and the Chrome "refreshing" circle is constantly spinning. Turning off nod32's HTTP checking solves the problem. I also tried IE10 and experienced the same problem so it does not appear to be browser-specific behavior. -- bc

With the beta there is no activation email. At the end of the installation process, when asked to activate you can either choose "Activate Beta" OR if you've upgraded over v5 or v6, it will should remember your license credentials. I can confirm this worked fine. My license expiring in 2015 still shows as such in v7 beta. -- bc