Specifies that Google Update should roll installations of Google Chrome Dev back if the client has a higher version than that available.
If this policy is not configured or is disabled, installs that have a version higher than that available will be left as-is. This could be the case if "Target channel override" is set to a Channel with a lower version, if "Target version prefix override" matches a lower version on the Channel, or if a user had installed a higher version.
If this policy is enabled, installs that have a version higher than that available will be downgraded to the highest available version, respecting any configured target Channel and 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.