gianfranco.pitta@ Could you please help us with the master_preference file for further triage.

I have attached my file master_preferences right now. As you can see I have tried to add the variable "has_seen_welcome_page": true, under "Session" but it doesn't work.

Deleted: master_preferences 1.1 KB

master_preferences 1.1 KB View Download

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue on Win2K12 with chrome #60.0.3112.101 

Replaced the provided file in comment #4 in location "C:\Program Files (x86)\Google\Chrome\Application" and launched chrome/

Observations:
Didn't see any policy displayed under chrome://policy which was mentioned in the master_preference file.

Attaching the screen-cast for reference.

gianfranco.pitta@ could you please help us with exact steps to reproduce the issue.

Thank You...

Deleted: 758572.mp4 1.3 MB

	758572.mp4 1.3 MB View Download

Hello, it's correct that you don't see any policy/settings applied. This is because you have already your settings, these settings have been created the first time that you have launched Chrome. The file master_preferences works only for the first time that users execute Chrome. 

In order to reset your settings you need to delete the Chrome profile folder, usually the path is:

C:\Users\%USERNAME%\AppData\Local\Google 

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on Skytap environment with Win2K12 as Server & Windows 10 as Client with chrome version #60.0.3112.101, followed steps as per comment #4 & #8

Attaching the screen-cast for reference.

gianfranco.pitta@ could you please look into it and confirm this is the exact issue you are facing?

Deleted: 758572-1.mp4 1.2 MB

	758572-1.mp4 1.2 MB View Download

Exactly! This is the exact issue!

Same behavior with the last version of Google Chrome 61.0.

Thank you!

We are still having this issue on 63.0.3239.132.

One thing that we have noticed: if you open Chrome *once* for the first time, open the Preferences file under %AppData%\Local\Google\Chrome\User Data\Default, and then find "has_seen_welcome_page" and change its value to true, the "Take Chrome Everywhere" tab won't appear on the second run of Chrome.

This is significant because it means that the has_seen_welcome_page *does* have something to do with the "Take Chrome Everywhere" startup page, but it's working in conjunction with something else, too, to determine if the tab should appear.  What that something is, however, I do not know.

In any case, we would really like to see this issue resolved quickly.  This issue has been open for a while.  Ideally, the "Take Chrome Everywhere" tab should just be removed, but barring that, it should at least never appear if has_seen_welcome_page has been set to true in master_preferences.

Sorry, the path of the file is not as I wrote above; it's actually in:

%USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default

Can confirm this is still an issue in 64.0.3282.140. Anyone have a workaround?
Chrome Source looks promising:
https://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/pref_names.cc?view=markup

// Boolean pref indicating the Chrome Now welcome notification was dismissed
// by the user. Syncable.
// Note: This is now read-only. The welcome notification writes the _local
// version, below.
extern const char kWelcomeNotificationDismissed[] =
    "message_center.welcome_notification_dismissed";

// Boolean pref indicating the Chrome Now welcome notification was dismissed
// by the user on this machine.
extern const char kWelcomeNotificationDismissedLocal[] =
    "message_center.welcome_notification_dismissed_local";

// Boolean pref indicating the welcome notification was previously popped up.
extern const char kWelcomeNotificationPreviouslyPoppedUp[] =
    "message_center.welcome_notification_previously_popped_up";


It looks promising BUT no luck with these values in my master_prefs file. I guess I will hold my enterprise deployment until someone gets this figured out.

Any news about this issue? Same problem with version 65.0.3325.181 @sheriffbot@chromium.org 

Hi. We added the PromotionalTabsEnabled (https://www.chromium.org/administrators/policy-list-3#PromotionalTabsEnabled) policy setting in Chrome 69 to address this.