Avastclear gives error 'stub cannot run installer / updater ...'

We've had a few license warnings for Avast Business Antivirus Cloudcare recently. Usually when upgrading, eg from Cloudcare 4.2.x to 4.3.0. To fix the licence warning you usually need to uninstall the current version, reboot and reinstall the latest. Even then it doesn't always work and using avastclear, the official uninstaller program from Avast / AVG is the way to go. Note that this should be run from Safe Mode.

When you run avastclear you might see the error shown in the diagram here.

"The stub cannot run installer / updater executable 'c:\users\   \appdata\local\temp\_av_iup.tm~
\instup.exe' (code 0x10b)"

Took a while to work this out - you need to be logged into Safe Mode as the local administrator, not a domain admin account.

Then the uninstall will run and reboot.




15/10/18 Update - also seen this warning with some sort of permission issue, had to move the avastclear program to another directory, eg c:\temp or c:\windows\temp
 
 9/12/18 Update - Permission issue if you downloaded as the domain user then switched to local, try making a copy of avastclear and run that instead

3 PCs missing from AVG Avast Cloudcare Console

Strange problem at one site with AVG CloudCare v3.6.4. Only one of 3 particular PCs would ever appear in the console at once. Lets call them PC26 (Maint), PC29 (Chef) and PC31 (Accts). This week PC29 was listed, status ok, updates ok. It even had the correct label name against it showing that is was Chef's computer. I tried reinstalling PC31 which succeeded, but it appeared on the list with the name Chef rather than Accts - and PC29 dropped off the list. I relabelled it to Accts, then PC29 came back on the list instead but with the new label.

Took me a while initially to realise that all three were essentially sharing one database entry and the last change/install took precedence as far as the console list was concerned.

Also tried removing AVG CloudCare off all three PCs at once and using the AVG Remover tool, rebooting, then reinstalling each one. And the same again but with the brand new 4.0.2 release of Avast Business Cloudcare. No chance.

In the end, after 25 mins online with tech support, we used the 'setup.exe -b' command to re-register the clients to the CloudCare database and reset registry keys. This cleared the problem and all clients came up normally.

To use setup -b, start a command prompt with Admin rights. Then change to the appropriate directory, depending upon client and 32 or 64 bit, eg
C:\Program Files(x86)\AVG\CloudCare   or
C:\Program Files(x86)\AVAST Software\Business Agent\