Chrome Enterprise & Education FAQ
GeneralHow is Chrome Browser for the enterprise different than the consumer Chrome Browser?
The Chrome Browser for the enterprise (sometimes referred to as Chrome Enterprise) is the same Chrome Browser used by consumers. The difference is in how the browser is deployed and managed. Downloading the Chrome Enterprise Bundle, IT administrators can install the Chrome Browser via MSI, and manage their organization’s Chrome Browsers via group policy to enforce over 200+ policies.
Chrome supports administration features on Windows, Mac, and Linux.
For details, see Start managing Chrome Browser.
InstallationIs there a Windows MSI for installing Chrome Browser?
Yes, To download the latest MSI, download the Chrome Enterprise Bundle.
To download the Chrome Browser for personal use, go to https://www.google.com/chrome/.
Google recommends you always use the latest version of Chrome. If you need to use a prior version:
- Uninstall your current version.
- Delete every user's saved profile data by removing the following directories:
- Windows Vista / 7: C:\Users\<user>\AppData\Local\Google\Chrome\User Data
- Windows XP: C:\Documents and Settings\<user>\Local Settings\Application Data\Google\Chrome\User Data
- Mac OS X: ~/Library/Application Support/Google/Chrome/Default
- Linux: ~/.config/google-chrome/Default
Warning: When you delete these directories, users permanently lose their bookmarks, browsing history, etc.
- Reinstall the older version.
No, older versions of the MSI are unavailable and unsupported.
The MSI only installs at the system level, so all users on the machine have access to the same instance of Chrome.
UpdatesHow often does Chrome update?
Google releases an update to the Chrome Browser and Chrome devices approximately every 6 weeks.
We publish release notes for enterprise administrators for milestone releases of the Chrome Browser. You can also follow updates on the general Chrome releases blog: https://chromereleases.googleblog.com.
Subscribe to the blog at https://chromereleases.googleblog.com to learn about security updates as soon as they are public.
Policies and SettingsHow do I check which Chrome policies are in use?
Enter chrome://policy in your Chrome address bar, and you will see all of the policies currently in effect on that browser or Chrome device.
See also View a device's current Chrome policies.
There are 200+ available for on-premise management (Windows, Mac, Linux), and 100+ for cloud-managed from the Admin console.
You can enforce Chrome policies on corporate Windows computers using Windows Group Policy, Windows Registry settings, and master_preferences.
For details, see Chrome Browser on Windows (managed on premise).
Yes on corporate-managed devices. On a user's home computer, they need to sign in to Chrome using their managed Google Account (such as G Suite) in order for the policies to work in Chrome.
SupportHow many versions back of the Chrome Browser and Chrome OS do you support?
Google only supports the most current dev, beta, and stable channel releases.
Yes, if you have a G Suite or G Suite for Education account, or if your company purchased Chrome Enterprise Support.
Please file a bug in our public issue tracker. We recommend that you use the search fields first to look for similar bugs and see if the issue is already being resolved.
Unfortunately, we can't give exact timing on when specific issues will be fixed. You can follow the public bug to see when changes are made, when it's marked as fixed, and when it's closed.
In addition to this Chrome Enterprise Help Center, get online help at:
If your users need to access websites and applications in a legacy browser (such as those relying on ActiveX, Java, or Silverlight), pre-install the Legacy Browser Support extension for your users. Test your internal applications on the Beta and Dev channels of Chrome to ensure that your systems work with the upcoming stable releases of Chrome.
If you do find issues in Chrome (e.g. pages crash, Chrome shows web pages differently than Safari, etc.), then please let us know by filing a bug.