I’ve noticed that I’m no longer receiving the streaming updates. They appear to have stopped on Sept. 18th. I have version 8.0.1483 with a base file (if you will call it that) of March 26th. Is this because I need to update to 1496 or 7?
If I update to 1496 or 7, will the update clear out all those hundreds/thousands of little stream files?
avast says the latest update received 9/18/2013 at 2:15:30 PM. I’ve noticed it hasn’t been creating its little stream files in the defs folder since 9/18.
Hi, did the repair, and it did not seem to make any difference. According to the avast window, streaming updates are enabled and connection is established. Last update: 9/18/2013 2:15:30 PM. The only thing I can think of is that the streaming updates for this particular version, 130326-1, have ended. I take 130326-1 as a base file. Maybe I need to get a new one? If I get a new one (how?), will that get rid of the current crop of six months worth of stream files, assuming they’re not needed? There are hundreds, if not thousands, of little stream files.
If your last update (virus definitions) is 9/18/2013 then you have a larger problem than the streaming updates. As that is 16 days old.
What happens when you try a manual virus definitions update, e.g. are you getting any errors ?
You could also try a Manual update of VPS - avast! Virus Definitions Update - Manual Download VPS Update (virus definitions, vpsupd.exe, approx 103 MB). - Save the file to your hard disk, locate where you saved it and double click it and that should carry out the virus definitions update.
If that doesn’t resolve it then you are probably looking at a clean reinstall.
I have thhe same problem, repair did not work and I did a clean install. It worked OK for about 2 weeks and I now get the dame error again.
Avast was unable to update
No this downloads the full virus definitions database, click the link I gave (the blue text) from that avast web page download the avast! VPS update option not the other one for avast 4.8.
There is no md5 published as far as I’m aware, but the avast program should be able to validate it. The vpsupd.exe file could be updated to ensure the latest signatures are included, so only a slight change would give a different md5/sha1 hash.
I finally fix this problem. My avast stop streaming update on 4th October. After reinstall bring no result and vpsupd.exe said that everthing is up to date I click update virus definition in maintenance tab to see which files avast update, boot to safe mode, then delete all that file found in avast/setup directory. Long update after I restart windows I manage to get 131010-1 update. All left is to see if this is permanent solution.
If it weren’t the latest VPS version, then you wouldn’t be getting streaming updates for it. New versions of the VPS update clear out the old streaming updates as they are included in the next VPS update.
Slip of the tongue/keys should have been clearer as in the -1 suffix indicates the second one of the ‘day in question.’ If there had been a later VPS, e.g. one for today, then you wouldn’t be getting streaming updates relating to 131010-1 VPS.
So yes it is still the latest VPS update, none yet today, but lots of streaming updates. Strangely I’ve just started seeing streaming updates for 13101100_stream, so I don’t know if the VPS update 131011-0 was pulled.