Last month I renewed my annual subscription to Nod32 and updated from version 3.0.621 to 3.0.695. I carefully followed Eset's Knowledgebase instructions regarding how to uninstall and reinstall. I had no trouble. But, I am experiencing a behavior with 3.0.695 that I did not have with 3.0.621. I prefer to always disconnect my system from the network when I am done with a browsing session. With version 3.0.621, whenever I would reconnect to my wireless connection (usually after several hours), Nod32 would immediately and automatically check for a virus signature database update. But with version 3.0.695, I have to wait an hour before Nod32 automatically checks for a virus signature update. As best I can recall, my automatic update settings are the same as they were with 3.0.621. And as shown immediately below, the automatic update task should happen "as soon as possible" if the task misses a run. Nonetheless, with 3.0.695 I have to wait an hour for an automatic update to occur after I reconnect my wireless connection, and during that interim period, I see this: Does anyone have any clues why v3.0.621 would immediately and automatically check for a virus signature update when I would reconnect to my wireless network but with v3.0.695 that automatic virus signature update is delayed an hour?