Specifies that Google Update should roll installations of Google Chrome Beta back to the version indicated by "Target version prefix override".
This policy setting has no effect unless "Target version prefix override" is set.
If this policy is not configured or is disabled, installs that have a version higher than that specified by "Target version prefix override" will be left as-is.
If this policy is enabled, installs that have a version higher than that specified by "Target version prefix override" will be downgraded to the highest available version that matches the target version.
To make sure that users are protected by the latest security updates, we recommend that they use the latest version of Chrome Browser. If you roll back to an earlier version, you will expose your users to known security issues. Sometimes you might need to temporarily roll back to an earlier version of Chrome Browser on Windows computers. For example, your users might have problems after a Chrome Browser version update.
Before you temporarily roll back users to a previous version of Chrome Browser, we recommend that you turn on Chrome sync (https://support.google.com/chrome/a/answer/6309115) or Roaming User Profiles (https://support.google.com/chrome/a/answer/7349337) for all users in your organization. If you don't, users will irrevocably lose all browsing data. Use this policy at your own risk.
Note: You can only roll back to Chrome Browser version 72 or later.
This policy is available only on Windows instances that are joined to a Microsoft® Active Directory® domain.