This site is only for Avast Business products. For articles on AVG Business products, see AVG Business Help.

Understanding Updates and Reboots

This Article Applies to:

  • Avast Business CloudCare

Agent updates

The CloudCare agent is responsible for the main installer, installing services, proxy settings, device detection, remote deployment, communication with the back-end, etc.

Agent updates can be performed in several ways:

  • New downloads: new installer downloads will always receive the latest Agent
  • Manual updates: clicking Update on the Device Details page or one of the Update Available links on the Devices list will send a command to download and install the latest Agent
  • Scheduled updates: updates are made available to devices starting 1-2 weeks after a release, and are not sent all at once to throttle the number of devices updating at the same time. Scheduled updates must be enabled in the CloudCare Agent Settings section of Policies

Updating the Agent also updates any installed services (such as Antivirus, Content Filtering, Cloud Backup, etc) to the latest version.

Antivirus updates

The Antivirus service receives updates regularly, and a reboot is usually required due to driver-level changes. We strongly recommend working around reboots when they are required to ensure you have the latest Antivirus updates.

Antivirus updates are controlled in the Antivirus section of Policies. The default setting is Automatic. For servers, we recommend creating a separate policy with program updates set to Manual.

Restart options

To make handling reboots easier, you can configure restart options in the CloudCare Agent Settings section of Policies. This feature can notify end users of required restarts that are necessary for an update of the Agent or one of the services. If enabled, you should receive fewer “Restart required” alerts.

The first two restart options will force a restart if no user is logged in, which is often the case for servers; therefore, the default setting is “Do not alert user, do not force a restart.”

  • Alert user, perform action when user logs off: A message about the upcoming restart will show on the end device. Then, when the user logs off the device, it will restart automatically.
  • Alert user and force restart: A restart will occur any time a patch or program update is executed. A message about the upcoming restart will show to the endpoint user a selected number of minutes before the restart. You can choose to allow the user to extend the time-out by a certain number of minutes, or even cancel the restart if desired.
  • Do not alert user, do not force a restart: You will have to restart manually either from the console or on a physical endpoint device. No restart will occur. This could affect future patch deployments if there is a restart pending on the Windows operating system.

Recommendations for servers

If you want full control over Antivirus updates on your server device(s), we recommend the following settings in Policies:

  • set the Program updates to Manual in AntivirusGeneral Settings
  • disable CloudCare Agent updates in CloudCare Agent SettingsUpdate Schedule by unchecking the box beside Enable this task.

If you do this, no updates will occur to the CloudCare Agent or the Antivirus client unless you manually force an update. You will still regularly receive virus definition updates.

The recommended setup is a separate policy for servers, as well as maintaining a regular maintenance window in which you manually force an update of the CloudCare Agent. This will ensure full control over your server(s) with no unexpected reboots.

Regularly update the Agent and, by extension, the Antivirus client so that your protection remains current.


You can configure an alert for when a restart is required in the Alerts section of the portal.

Utilizing the “Alert user, perform action when user logs off” or “Alert user and force restart” options will automatically suppress any “Device needs restart” alerts that have been configured (at master or customer level).

With the “Do not alert user, do not force a restart” option, the “Device needs restart” alerts will be enforced for every device selected, therefore devices within that policy will each send an alert when a restart is required.