How to Stop Users From Installing Google Chrome

Create a software restriction policy for your Windows Vista or Windows XP machines

Unless you've been locked away in a dungeon for the past few weeks, you should be aware that Google released its first web browser, Google Chrome. While I was cruising around the office the day of its release, I noticed that some of our users had installed and were using this web browser, violating corporate policy. By default, our users don’t have permissions to write to the restricted areas that most applications write to when they're installed, so it's our policy to have administrators install applications for users.

I decided to investigate how these users were able to install Google Chrome. My initial investigation revealed that the browser is designed to bypass restricted write areas and install into C:\Users\%username% in Windows Vista and C:\Documents and Settings\%username% in Windows XP. Because standard users can write to these areas, they're able to install the browser without Admin rights.

After installing Google Chrome on my Vista machine, I found that browser installed a setup file named chromesetup.exe, an executable named chrome.exe, and Windows Installer file named gears-chrome-opt.msi in the C:\Users\%username%\AppData\Local\Google\Chrome\Application folder. (In XP, the folder is C:\Documents and Settings\%username%\Local Settings\Application Data\Google\Chrome\Application.) Armed with this information, I successfully created a software restriction policy named Block Google Chrome to disallow these three files.

Here's how you can create the Block Google Chrome software restriction policy for your Vista or XP machines:

  1. Open the Group Policy Management Console (GPMC).
  2. Right-click your domain and choose the Create a GPO in this domain, and link it here option.
  3. Name the Group Policy Object (GPO) Block Google Chrome and click OK.
  4. Right-click the policy you just created and click Edit.
  5. Navigate to the User Configuration\Policies\Windows Settings\Security Settings\Software Restriction Policies folder.
  6. Right-click Software Restriction Policies and select New Software Restriction Policies.
  7. Right click Additional Rules and choose New Path Rule.
  8. In the Path field, type chromesetup.exe.
  9. In the Security level drop-down box, choose Disallowed and click OK.
  10. Repeat steps 7 through 9 for the chrome.exe and gears-chrome-opt.msi files.
  11. Repeat steps 7 through 9 for the path C:\Users\%username%\AppData\Local\Google\Chrome\Application\chrome.exe for Vista machines or C:\Documents and Settings\%username%\Local Settings\Application Data\Google\Chrome\Application\chrome.exe for XP machines. You should include this rule in case some of your users have already installed the browser. After you implement the GPO and the Group Policy settings refresh on those users' local machines, they'll no longer be able to successfully run Google Chrome.
  12. Open a command-prompt window and run the command
    gpupdate /force
    to apply the new rules.
  13. Run the command
    gpresult /R
    in Vista SP1 or the command
    gpresult
    in XP and Vista (pre-SP1) to verify that the newly created GPO has successfully been applied.
  14. As a final test, attempt to run the installer from the Google Chrome website. If the policy is successful, you should see the error that Figure 1 shows.

With the Block Google Chrome software restriction policy, you can stop users from installing and using Google's new web browser without IT's consent. (Note that if you want some users to be able to install and run the browser, you can filter the GPO so that it won't affect them.) You can even adapt these steps to block other applications that install to user-accessible areas in the OS and registry.

—Steve Di Bias, systems administrator, Las Vegas Convention Center

Learn more from "Google Chrome Becomes Number Three Browser" and "Could Chrome Be the Next IE?"

Discuss this Article 6

r_severson
on Dec 21, 2010
Perhaps Google has updated their installation steps as I also followed the directions exactly and Google Chrome did install, however, the user was not able to launch Chrome.

I looked further into this and have found chrome_installer.exe is also being used during the install process...at least when starting the install from http://www.google.com/chrome.

So for XP I added another New Path Rule:

C:\Documents and Settings\%username%\Local Settings\Application Data\Google\Update\Download\*\chrome_installer.exe

Now after going through all the steps starting from http://www.google.com/chrome The Google Chrome Installer application displays the message 'The installer failed to start' which accomplishes the mission for my XP systems.
Frank (not verified)
on Dec 10, 2009
I followed your directions exactly. Google Chrome still unstalled (XP SP3) Server 2008 GPO But the user was not able to run Google Chrome
PDTechguru
on Oct 8, 2012
Google Chrome Home Page Group Policy http://pdtechguru.wordpress.com/2012/09/25/google-chrome-group-policy

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.