Sequence Google Chrome v36 with App-V 5 SP2 HF4

Sequencing Google Chrome 36.0.1985.125 with App-V 5.0 SP2 HF4





My personal lab setup-


Windows Server 2008 R2 SP1 – fully patched as of 7/25/14

App-V version: 5.0 SP2 HF4

Non-domain joined


Windows 8.1 – fully patched as of 7/25/14

App-V version: 5.0 SP2 HF5



Download Google Chrome for Business – The IT manager (MSI) download

You should now have GoogleChromeStandaloneEnterprise.msi


Installation steps:

PVAD: C:\Dummy

If you want to use Microsoft best practices, here is the default installation directory: C:\Program Files (x86)\Google


Run – GoogleChromeStandaloneEnterprise.msi

The only way you will know the install is complete is by the new Google Chrome icon on the desktop.


Disable the following services:

  • Google Update Service (gupdate)
  • Google Update Service (gupdatem)


Save and deploy your sequence.

8 thoughts to “Sequence Google Chrome v36 with App-V 5 SP2 HF4”

  1. How to disable Google Update (gupdate & gupdatem) from virtual services during the sequence? I disabled the service from services.msc and then saved the package. Hope it work the way it should.

  2. During sequencing process, I did change Home Page that should open when you run Chrome – Unfortunately the sequence process did not take that into account. How can, I incorporate custom home page site and not the default site as the home page.

    By the way you can ignore above post with regard to gupdate service. I looked at the client system where google chrome (virtual app) was installed – there is no gupdate service in services.msc.


    1. I’m fairly certain the custom home page is stored in local appdata, which is excluded from sequences by default. But I would recommend using group policy to control preferences with Chrome so you don’t clutter up your sequence. Google has vastly improved their GP templates over time. You can find them here.

      1. Find the master_preferences file located next to chrome.exe and put in your home page as required eg :
        “homepage” : “http://******myhomepage/default.aspx”,
        “homepage_is_newtabpage” : false,
        “browser” : {
        “show_home_button” : true,
        “check_default_browser” : false,
        “window_placement”: {
        “bottom”: 1000,
        “left”: 10,
        “maximized”: false,
        “right”: 904,
        “top”: 10,
        “work_area_bottom”: 1010,
        “work_area_left”: 0,
        “work_area_right”: 1680,
        “work_area_top”: 0
        “bookmark_bar” : {
        “show_on_all_tabs” : true
        “sync_promo” : {
        “user_skipped” : true
        “distribution” : {
        “skip_first_run_ui” : true,
        “show_welcome_page” : false,
        “import_search_engine” : false,
        “import_history” : false,
        “create_all_shortcuts” : false,
        “do_not_launch_chrome” : true,
        “make_chrome_default” : false

  3. While following your instructions, I encountered a warning while sequencing which detected a DCOM subsystem. The Chrome browser appears to launch fine but this is in a test environment without internet access. Has anyone else experienced this? If so, have you been able to locate a solution? Our department needs to know before we go live with our App V 5 environment. Thanks

    1. Kevin,

      I don’t recall if that warning came up when I last sequenced Chrome, but we had no issues with it running virtualized.

      1. Chrome appears to be opening without any issues in our test environment as well. I was just checking to be sure in case if we do decide to modify our current environment with App V 5. Thank You for your reply.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.