Ever since RC1, I’ve never had sounds or notifications for VPS updated. (streaming updates are fine). I was expecting this to be fixed by the final version. Has anyone else had VPS update with sound and notification.
In other words I get the VPS update somehow but don’t get the sound nor notification.
At the moment there seems a larger issue no VPS Updates yet today, so the sound isn’t going to be
The streaming updates are working away, but still waiting for VPS. Whilst typing this up I got a pop-up that promoting the avast! Mobile Security informative pop-up. No avast voiceover.
These informative/promotional toaster pop-ups appear to be piggybacked to the VPS Update Notification, so you don’t see the VPS update notification, I suspect it is this that is screwing up the avast sounds on update notifications.
No problems here.I have VPS updates with notification and sound.
I updated through GUI from version 8.0.1497 to version 9.0.2006.
BTW,I just received 131017-0 update.
Avast Free
Windows 7 SP1 32bit
No, same on my win7 32bit netbook, just got an informative popup ‘Avast Tip: FB Privacy’ in the background the VPS update was downloaded and installed, but nada update popup or voiceover.
Well 131017-1 arrived this morning unannounced on my win7 netbook, no popup or sound. Checking the ‘Show last popup message’ still shows the FB Privacy information popup as in my Reply #3. This system hasn’t been rebooted so it could well be recalling the same popup as before.
The same 131017-1 (image1) arrived this morning unannounced on my winXP Pro, no popup or sound. Checking the ‘Show last popup message’ (image2) it is greyed out. This system was shutdown last night, so confirmation no popup relating to this update.
Why would I want to do that, if I want it to work with English, unless you are saying that it would jog other languages to life (which I rather doubt).
Well 131018-0 came and went unannounced, no popup or sound, even from the pirate. The ‘Show last popup message’ just shows an ad for avast! Mobile Security. This was no doubt piggy backed on to the update and I suspect that this may be what is screwing it up.