Last September, I wrote a popular blog post about sequencing Google Chrome 21 with Microsoft App-V 4.6. Google has released a couple of new versions of Google Chrome since then.

Reading through the comments of the blog post I find that applying mandatory User Preferences is the most difficult part of the package.

Let’s take a look at how to create a successful Google Chrome 25 App-V package on Windows 7 x64. I used App-V 4.6 SP2 because SP1 has some issues with OSD scripting.

In this blog I am going to describe the steps necessary to make the package work. I only describe the options to make the package work, not the complete steps to create a App-V package.


Download Google Chrome from here.

This is an Enterprise edition of the Chrome browser.

Start the Microsoft App-V 4.6 Sequencer and walkthrough the wizard.  
If the monitoring phases is started, open a command prompt and start the installation using:

START /WAIT GoogleChromeStandaloneEnterprise.MSI ALLUSERS=TRUE /QB-


After the installation, remove the folder:


Enter the command:
REG ADD HKLM\SOFTWARE\Wow6432Node\Google\Update /v AutoUpdateCheckPeriodMinutes /d 0 /t REG_SZ /f


When copying and pasting, pay special attention to the quotation marks.

Enter the command:
REG ADD “HKLM\System\CurrentControlSet\Control\Session Manager” /v PendingFileRenameOperations /d “” /t REG_MULTI_SZ /f


When copying and pasting, pay special attention to the quotation marks.

Start Google Chrome.

Change all the preferences that your prefer, like;
– The Default start page
– Proxy settings
– Etc.

Close Google Chrome.  
Open the folder:
%LOCALAPPDATA%\Google\Chrome\User Data\Default
Copy the file: Preferences to a save place.

This file contains all the settings that were changed.

Close the App-V Monitoring phase and save
the package.
Copy the Preferences file into the package directory.  
Open the Google Chrome OSD file with a text editor (like Notepad).  
Create a startup script below <DEPENDENCY>

\\server\\share\\packages\\google\\chrome\\Preferences “%LOCALAPPDATA%\\Google\\Chrome\\User Data\\Default”</SCRIPTBODY>


Change the \\server\share\package part of the script.  
Save the OSD file.  
Test the package.  


When using this way of applying mandatory settings, every time the user launches the browser the mandatory settings are applied. If you want to preserve the user’s preferences you can create a script that will only copy the file once.

Can’t get the solution to work? Contact me and let me do the trick.


No responses yet

Leave a Reply

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

26 − 18 =