Streaming Updates appear to have halted

[aa.avast]

If you are able to try using OpenDNS for your DNS server (I can't using BT Infinity), see http://use.opendns.com/ for how to use.

To get started http://www.opendns.com/home-solutions/parental-controls/ select one of the two Free options (whichever is applicable) and click the Sign-up button.

Many thanks David.  Since reinstalling all seems ok, but have filed that link into my Bookmarks for future reference. Cheers.

[DavidR]

You're welcome.

If I could use OpenDNS with my BT Infinity HomeHub2, I would do so again in a heart beat, I used it for years before that. Not only is it a pretty fast DNS Server it has protections against DNS Poisoning, and if you use the dashboard function you can block certain category groups.

[George Yves]

Sorry, gentlemen, but I believe there is a critical bug with streaming updates that started in version 1456 and continues in version 1466.

Some times ago I noticed that my computer shuts down or reboots with the Windows "critical error" sound but without any pop-up message about the error. Today I discovered that there is no "critical error" sound if I disable streaming updates or uninstall Avast. Then I noticed that when I hear the sound, the streaming updates stop coming on next booting. I am tired of constantly repairing-rebooting-unchecking-rebooting-checking and again and again.

[aa.avast]

Sorry, gentlemen, but I believe there is a critical bug with streaming updates that started in version 1456 and continues in version 1466.
[SNIP]

I'm beginning to feel that way too.  Again, no streaming updates yet received today. :-(

[selen]

Sorry, gentlemen, but I believe there is a critical bug with streaming updates that started in version 1456 and continues in version 1466.
[SNIP]

I'm beginning to feel that way too.  Again, no streaming updates yet received today. :-(

same situation for me, and after the update to the new program version 1466 I have problem also with the normal Virus definitions update. the last one I received is the number 120821-0. Today is the 22th of august and I haven't received any new VPS update!

[aa.avast]

Exactly the same for me Selen. 

How do we get Avast to investigate/comment?  I've been very happy with Avast for quite a few years and would hate to have to ditch it now. 

[selen]

Exactly the same for me Selen. 

How do we get Avast to investigate/comment?  I've been very happy with Avast for quite a few years and would hate to have to ditch it now.

parhaps the VPS problem is related to the busy servers after the new program update 1466. About the streaming updates I don't know what to think, because I was quite sure that the new program update had solved the issue...unfortunately the problem is still here

[DavidR]

Sorry, gentlemen, but I believe there is a critical bug with streaming updates that started in version 1456 and continues in version 1466.
[SNIP]

I'm beginning to feel that way too.  Again, no streaming updates yet received today. :-(

There haven't been any updates yet today streaming or otherwise (VPS is still showing 120821-0), I don't know if that has anything to do with the new program update, but yesterday (prior to the program update release) there was a reasonable amount of streaming update activity.

[hlecter]

For your info:

The lack of new VPS-update has nothing to do with the new release of version 7.

I have Avast Pro 6 and my VPS is still showing 120821-0.

 

[DavidR]

Well I have no idea where you get that information form as you don't give any reference.

But with over 150million users a release of other updates would also put load on the update servers.

[ManyQs]

.

I will admit that the lack of udates is a bit troubling, but I have a large extra share of faith in the folks at Avast and I would bet my last euro they are hard at work to get things straight.

There is one more interesting aspect, that may be of some assistance to the engineers, or not -- as they probably already know -- but the usual popup asking that I update to 7.0.1466 hasn't shown up at all.  I really don't know when _ .1466 came out, but when the usual update lady didn't announce her presence some 12 hours or so ago was when I checked.  Two computers here have been off and on twice since then and still shows the red _ .1466 and, as others noted, the 120821-0 as the last virus definition.

Just in case any of that may be helpful.

Again, I sure ain't jumpin' ship for a long time.  This company has been getting it right for so long that I have stored up a fair bit of patience for their engineers to get things straight.  Anyway, my Net habits aren't really the kind that draws the baddies down upon me.  Usually.  Knock on monitor.

.

[hayc59]

Now def update here also?

[George Yves]

But with over 150million users a release of other updates would also put load on the update servers.

And what about the critical error sound that I have already described?

Sorry, gentlemen, but I believe there is a critical bug with streaming updates that started in version 1456 and continues in version 1466.

Some times ago I noticed that my computer shuts down or reboots with the Windows "critical error" sound but without any pop-up message about the error. Today I discovered that there is no "critical error" sound if I disable streaming updates or uninstall Avast. Then I noticed that when I hear the sound, the streaming updates stop coming on next booting. I am tired of constantly repairing-rebooting-unchecking-rebooting-checking and again and again.

For now I disabled streaming updates because I believe in reality of the bug.

[hlecter]

For your info:

The lack of new VPS-update has nothing to do with the new release of version 7.

I have Avast Pro 6 and my VPS is still showing 120821-0.

 

Well I have no idea where you get that information form as you don't give any reference.

But with over 150million users a release of other updates would also put load on the update servers.

I was confirming that this 'lack' of VPS update was not related to a bug in the new version 1466.
Avast servers, I take it for granted, can handle this...
I checked and no new VPS updates in the Virus update history either so server load can't be an issue.
 

[George Yves]

The main virus database was updated to 120822-1. Does anybody have information about streaming updates?