yeoldfart

I checked: eset certificate is kept in my FFox

the thread you're talking about should have been actualized, my experience on TP 10130 withe a clean install of NOD 32 definetely works since the devs have added up to date windows drivers. good luck

upgrade W10 to TP 10130 it should solve this issue as your W10 rls is very outdated

when a virus signatures update, a scan, a program update is running, there's only that little bouncing black dot to show th activity: it's hardly visible, making that thingy red or orange would help a lot those users with a poor vision. thank you devs

I insist on it: works fine with TP 10130, Eset not to blame, roll back to 10130, make a clean install, clear and simple.

not a single glitch with FFox 38.05

new today's release activates and updates like a charm on W10 10130 x64, clean install

new Nod 32 AV installer (clean install) worked blazing fast without a glitch, activatation and update too, stable on W10 TP10130 x64, good job devs

oh no ! smells of old time Norton !

Good idea, this is some kind of Live Grid world statistics. These statistics can be displayed in other secton not really on Home Screen. useless norton had it long before, jsut adds bandwidth use

it depends on availability of W10 rtm

I only beleieve in what I can touch and see ! why do Norton, Bitdefender, F-Secure etc. work perfectly fine with TP 10130 ? I assume they don't receive privileged infos

strange, not a glitch whatsoever here on W10 TP 10074 x64

Thx for these replies, yes my rig is behind a dsl router box. What alerted me is that neither NIS nor Avast had a single port left unstealthed.

I installed it today and tested it with shieldsup which said the test was failed because of port 80 having been left unstealthed (and open), when I had Avast ALL ports whre steahlted. Is it something to worry about ? I'm running W8.1, windows firewall says being managed by ESS.