Endpoints with KES installed are automatically upgrading to AVG2015 unexpectedly

You are receiving reports from customers that AVG has been updated to 2015. This may be accompanied by reports of the machines rebooting as part of the update.
Customers may also report that the AVG GUI reports that the license is invalid

On 23-Jul-2015, something happened with the AVG Update server.

This has resulted in each AVG client, once it has checked in to the AVG update server, pulling down and installing the new version - AVG 2015

AVG have disabled this update now, so no new machines will be affected.
For machines that been affected by this already, those that are currently downloading the update, installing the update or have already installed the update, the process is underway and cannot be stopped.

Kaseya support are currently working on a solution to reverse these changes. This is a new issue, so it will take a little while to test and provide a roll-back procedure for this.

Please "follow" this article for further updates as they become available.


11:06 - AVG have identified the issue and are going to supply a root cause shortly. This article will be updated accordingly.

11:50 - AVG have identified that Business class products were incorrectly "told" to update, rather than just the Consumer class products. This has been corrected - no further clients will update.

13:50 - We have confirmed that the update has been stopped. We are currently working on a roll-back process to return the affected machines to their original state. Details to follow.

15:30 - We are working with AVG at the moment, to build an agent procedure to make these changes. The current plan is to run the AVG removal tool to remove the AVG 2015 install, then schedule an update/reinstall through the Kaseya web interface (as if you are doing a fresh install of KES to the machine). The issue is going to be the requirements regarding reboot. At the moment, this appears to require a reboot for the uninstall (removal tool) and another to do the re-install. Updates to follow.

18:30 - A KB article has been published with steps to identify the affected machines and a procedure to forcefully remove AVG2015 from the affected machines -

Please note, that although this has been tested in-house on 32 and 64 bit OS's, we strongly advise that you test this in your environment before running this en-masse, as the behaviour may differ in other environments.

Was this article helpful?
14 out of 14 found this helpful
Have more questions? Submit a request


Article is closed for comments.