I’ve noticed many times that when cloud is not connected it will stay that way for very long time. But if you restart the system, it will re-connect instantly.
So, the cloud is working fine, it’s the client that doesn’t try to get in sync with it.
Unfortunately there isn’t a sync button in the avastUI, even in the UI, Settings, Account which gives a current status connected, if you disconnect and then reconnect, it may well connect but it doesn’t sync/communicate.
My XP Pro system is my primary system and the sync to my.avast.com doesn’t seem to be an issue, but my win7 netbook which spends most of its time in hibernation is showing a last communication of 4 days ago (and I have the Update Frequency set to 30 min), yet is is one often enough for it to be up to date.
So something needs to trigger this communication and for me the logical element is the avast update after a successful update it should trigger the communication.
+1
If the user opens the interface and see the information, he/she gets disappointed.
I certainly don’t know that for sure, but my guess is that the problem is more the presentation of the info in the UI (there can be various states that are perfectly OK, but might possibly show as disconnected cause it’s not clear how to classify them) or the UI refresh, rather than the real connection mechanism.
If it were for me, I would simply remove the info from the UI… and “problem” solved.
+1
I have, rarely, caught the streaming connection not connected when opening the AvastUI and then within seconds it changed to connected. I’m getting streaming updates so I’m not at all concerned about the temporary disconnects. I will admit to a little curiosity as to what triggers the state; the server or my installation??
I believe I saw a streaming update in progress shortly after I booted earlier today, there was a period where my system was a little less responsive, I thought that I had bumped into an auto update (as I delay it for 10 minutes). Later I checked the defs folder and found that a streaming update had taken place and 3 minutes later the auto update.
So it looks like the streaming update doesn’t obey the avast5.ini [InetWD] AlwaysConnectedWaitSeconds=300 instruction.
It fine. You probably checking it too much.