Folder AVG Forums » AVG SMB » AVG Admin » 2014 Messes Up 2013 Installations
November 8, 2013 20:48 2014 Messes Up 2013 Installations #236408
Reply with Quote | Quick Reply | Top


Join Date: 8.11.2013
Posts: 2
We're a small school district with a few hundred seats of AVG, the systems are a mix of XP and W7 32 & 64 bit.

We use the AVG Admin Console to take care of business.

When we try to install AVG2013 of late using either the console or by doing it manually/locally on the target machine itself, we keep having the installer trying to switch to AVG 2014. It starts up with 2013 as the version then switches itself, presumably after a quick online interrogation of AVG's servers.

This is not exactly a good thing because 2014 and the present Remote Admin Console have no way to talk to each other.

Under Windows 7 we find that neither using an old install package nor setting the system clock back by a few months (as suggested by AVG support) works - the installer still insists on trying to switch to AVG 2014.

We have a very real need for quick and easy deployment of 2013 right now, prefereably using remote methods - does *anyone* have a usable workaround for this problem?

It's getting to the point where we're thinking of changing AV vendor.

November 8, 2013 21:15 Re: 2014 Messes Up 2013 Installations #236412
Reply with Quote | Quick Reply | Top


Join Date: 19.6.2014
Posts: 0
@ LeeSAD27

OK, Just to keep you fully in the picture.. Regarding AVG (SMB) Team forum support bear in mind that it's now the weekend [9:15pm Friday evening] in the UK.. For your further guidance/info please refer to the availability Announcement post @ the top of the Information forum area.

AVG Forums Volunteer ModeratorAVG Forum member since - Nov. 27, 2004My total posts on the Old AVG Free Forum - 27,063
How-To Articles | FAQ | Free Support
November 13, 2013 11:49 Re: 2014 Messes Up 2013 Installations #236567
Reply with Quote | Quick Reply | Top


Join Date: 27.10.2009
Posts: 953
Hi LeeSAD27,

Sorry for all the problems and for not replying sooner. The 2013 version of AVG should still be deployable using the latest installation file (avg_ipw_x*_all_2013_3426a6755.exe):


The only reason the 2013 install should try to install the 2014 version is if an out of date installation file is used. The '3426' build should be installable by script, locally and remotely.

Please let us know if this does not help.


Michael Allen

AVG Customer Services

Join the AVG community!