Avast Mac Sierra 10.12.6 incremental update continual failure....

system · 2017-11-18T23:24:31.000Z

I have this issue since the latest program update it keeps wanting to download the full package. Is there a problem here ???
I have screen shots of the failures if required.

system · 2017-11-21T10:20:56.000Z

Just to add the message includes; Warning missing pointer to next patch. Fall back to full package download.
Is there a fix for this or does everyone assume we have unlimited download allowance ??

lukas.hasik · 2017-11-23T08:01:23.000Z

AV tries to update incrementally however sometimes it’s either more effective to download the full package or it fails in the incremental update process and goes to the latest version immediately.
What is your current “AV version”?

system · 2017-12-03T11:43:10.000Z

Thank you, I have observed with manual update that it does it every time. Version 13.2. I also have a 10.6.8 machine with a prior version and the incremental updating still works fine there.

lukas.hasik · 2017-12-03T21:28:43.000Z

screenshots might help, or the log file /tmp/avastupdate*
PM or email to hasik at avast dot com.

absmn · 2017-12-07T16:27:09.000Z

Hi Lukas,

I have the same problem with Avast for Mac 13.1 (beta channel) on macOS 10.13.1
Everytime when I start a manual VPS update, I see:

Connecting to repository http://mac-av.u.avcdn.net/mac-av/10_9/vps9 Downloading vps9.lat... Downloading vps917120700.inf... Downloading vps917120606.inf... [b]Warning: Missing pointer to next patch. Fall back to full package download.[/b] Downloading vps917120700.ful... Success: VPS updated. Version: 17120700 Package vps9 updated. Version: 17120700 Success: Updated.

So every time when I install new VPS files through a manual update, I get the warning ‘Missing pointer to next patch’.
Please let me know if you’re interested in more log files or a support package.

system · 2017-12-13T22:31:03.000Z

I have sent by email the log file I think you need.

drake145 · 2018-01-16T22:09:01.000Z

Good day all,

Was there a resolution to this issue?

I am also experiencing this issue every time I run a manual update.

absmn · 2018-02-15T23:26:32.000Z

Is there any news regarding this issue? Will this be fixed in the next version?

Announcements