Hey Gabriel can you please take a look at this issue?

Hi 

Has anyone had the change to look into this?

This is surprising to me : https://cs.chromium.org/chromium/src/chrome/installer/setup/install.cc?rcl=0&l=450 is responsible for this suppression and should still work.

Are other shortcuts properly suppressed? "do_not_create_any_shortcuts": true should also override this. Perhaps the JSON is malformed and everything is ignored?

Hi Thanks for the reply

The other shortcut is suppressed correctly and does not appear on quick launch bar. The JSON file has been verified using an online JSON Validator. All other options such as recover to local intranet page, language preference all get set, so the JSON file is not malformed.

Can you advise.

"distribution": {
		"msi": true,
		"system_level": true,
		"verbose_logging": true,
		"skip_first_run_ui": true,
		"show_welcome_page": false,
		"import_search_engine": true,
		"import_history": false,
		"do_not_create_desktop_shortcut": true,
        	"do_not_create_any_shortcuts": true,
		"do_not_launch_chrome": true,
		"make_chrome_default": false,
		"supress_first_run_bubble": true
	},

Can you attach chrome_installer.log (should be in %tmp%\ or the SYSTEM temp folder for system installs)

Attached is the chrome_installer.log as requested.

Deleted: chrome_installer.log 436 KB

chrome_installer.log 436 KB View Download

Per:

[0902/090110:VERBOSE1:install.cc(116)] Creating all-users Desktop "Google Chrome" shortcut to C:\Program Files\Google\Chrome\Application\chrome.exe.
[0902/090110:VERBOSE1:install.cc(116)] Creating per-user Quick Launch "Google Chrome" shortcut to C:\Program Files\Google\Chrome\Application\chrome.exe.
[0902/090110:VERBOSE1:install.cc(116)] Creating all-users Start menu "Google Chrome" shortcut to C:\Program Files\Google\Chrome\Application\chrome.exe and pinning to the taskbar.

the installer is intentionally dropping the shortcuts. So the master_preferences are not used by your installer. How are you using master_preferences? What's happening is probably that the way you're doing it results in Chrome using the master_preferences on its first run but the installer not seeing them on install (hence why preferences that apply to Chrome instead of the installer are working as you report).

Ah I see what you are saying. 

The Method of install  is batch file install and the master preferences gets copied into C:\program files (x86)\google chrome. This is then used via deployment with SCCM. So I understand what you are saying that Master Preferences files is only called upon first when.

But why does the the shortcut on Quick Launch not appear at the point of install if this is the case?

Also what is the method of deployment I must use in my scenario ?

Thanks for your help.

The Quick Launch shortcut is never created by recent versions of Chrome if I'm not mistaken (even with blank master_preferences).

For typical installs, the master_preferences file must be placed by mini_installer.exe before running it. For MSI installs however, install-time master_preferences are currently not supported, track  issue 244281  for updates on this issue (as well as a few workarounds mentioned in comments).