On #2, The uninstall of 4.x needing a reboot is understood. However that leaves 2 bad options that I see.

Option 1: Suppress the reboot for 4.x uninstall. This leaves the computer in an unprotected state until the end user decides to reboot the PC allowing ver 5 to get installed.

Option 2: Leave the forced reboot for 4.x and have angry clients complain that there was no warning about a pending reboot.

So to get around this, I am pushing avast_managed.exe out via group policy on login. This way, no user has a chance to have any work open when 4.x is uninstalled. The reboot is immediate and 5 goes right in after the PC comes up. By bypassing the console deployment, I can control the time of the reboot.

It would be nice if the uninstall process had a configurable time before a forced reboot. i.e. (“your machine will reboot in 5 minutes. Save your work”) or something to that effect. Otherwise, when you deploy via job, someone may lose work when the reboot happens with no warning.