rlcronin

You might check the settings under Control Panel->Internet Options->Connections->LAN Settings and un-check "Automatically detect settings" if its checked (and you don't actually need Windows to try to figure out your proxy settings automatically). I've seen that cause delays like what you mention. -- bc

Forgive the n00b question please. I am new to Smart Security. I installed it today only to discover that I am now unable to connect to a vnc server on my local network through an ssh tunnel that I've got between my PC and the host running the vnc server. I presume I need some special rules to enable that. Can anyone help me figure out how to set that up? -- bc

I've had a similar experience with the last two Windows 10 fast-ring insider builds, although in my case it wasn't all connectivity that was lost, just https connections didn't work until I uninstalled and reinstalled. Maybe related. Maybe not. I don't expect eset to do anything about it in my case since I knowingly opted for the fast ring, so anything that breaks is my responsibility to deal with myself. -- bc

I hadn't tried to manually move the popup. I will try that, although I wish there were a way in Settings to tell nod32 to restore it. Maybe you might consider having it do that when someone clicks "Reset window layout". -- bc

The desktop notifications that popup whenever the signatures are updated used to appear in the lower right corner of the screen. Lately however they're showing up elsewhere. How do I restore the default behavior? -- bc

What am I missing here? The ESET webpage is offering the multi device security product for 6 devices for 1 year for $42.49. It seemingly includes the full NOD32 product (as well as the Firewall and mobile product). Yet if I ask for the price for a 1 year license for NOD32 for 6 devices, I am told it is $149.94. If I get the multi-device product, am I really getting the same NOD32 that I'd have to pay $149.94 for the same number of devices? How does that make any sense? -- bc

Is there any way I can download the .0 spin of 9.0.349 so I can backlevel myself to see if the problem goes away? -- bc

All of a sudden I can't get to https://www.nest.comand login to my account there anymore. nod32 (version 9.0.349.14) blocks it claiming there's some kind of problem with its certificate, but doesn't elaborate other than saying it was "blocked by PUA blacklist". Anyone else seeing this? What do I have to do to get this fixed? Thanks for any help. -- bc

I too find the new GUI jarring, but perhaps its because I don't understand the motivation for the changes. I'm curious why the changes were made. Was there some compelling reason for it, or was it just change for the sake of change? Can you provide any insight into the thought process that led to the new design? -- bc

If the past is any indication of the future, I'd expect a v9 beta in August or so and a general release in late October or early November (although that seems to have been tied more to new Windows releases that anything else, so if the rumors are true about a Fall general availability of Windows 10, perhaps it will be earlier this year). -- bc

Maybe you have a similar issue like the one discussed some time ago in another thread: Delay Update Attempt? There are also useful instructions how to test this, so maybe you should follow the instructions for the "ping test" from @Aryeh Goretsky to find out whether your assumption is true. ... an issue that was never resolved for what its worth. Sigh. -- bc

Alright, that makes sense, but what good does it do to try so quickly only to have it fail because the network card is not fully ready only to have it then not try again for the default 60 minute regular automatic update interval. A lot more could happen in those 60 minutes than would happen in the 6-8 seconds longer you'd be waiting for the network to be ready. -- bc

I can now substantiate SweX's comments with hard data. I have a System event log entry dated 08/22/2014 at 3:59:31 PM recording the PC being woken up. Then in the nod32 log file I have an entry at 3:59:33 from the Update module saying "Server not found". So nod32 is not waiting very long to make the attempt. -- bc

I tried the ping thing but didn't get any useful info. Then I thought of looking in the event log. This is the very first entry in the system event log at the time of wakeup: 09:45:42 The system time has changed to ‎2014‎-‎08‎-‎20T13:45:42.500000000Z from ‎2014‎-‎08‎-‎20T10:04:56.750426100Z. Then in the application event log I saw these two events: 09:45:48 Fault bucket -861546332, type 5 Event Name: WPNConnectionFailure Response: Not available followed by 09:45:51 Customer Experience Improvement Program data was successfully sent to Microsoft. From this I conclude that it took almost 10 seconds from wakeup time for the network to be able to successfully connect to the Internet. How's that? -- bc

I'm not sure how I'd figure that out, but I'll work on it. Thanks. -- bc