Julian: Based on some codesearching, you should have some context about flash policies.

Adding some more people that might know what has changed.

Can you post the contents of chrome://policy on the broken Chrome instance?

This isn't from the exact device, as I restored that to 61 yesterday, but I have another same model and OS version as the report. It has the same flash issue.

Deleted: policies.json 17.9 KB

policies.json 17.9 KB View Download

I'll take a look next week, but one thing to note is that the EnabledPlugins policy is deprecated (Flash is the only third-party plugin left) in favor of DefaultPluginsSetting. Maybe that will already resolve your issue?

Thanks Bernhard, from the looks of it the policy is actually properly set (as a proxy for DefaultPluginSetting that is).

I have this same issue.  I have worked around it by adding in wildcard sites in to the PluginsAllowedForUrls setting.  Up until I updated Chrome to 62.0.3202.62 flash worked as intended, previous version was 61.0.3163.79.  My GPO's are set up virtually the same way as mentioned above.

"DefaultPluginsSetting": {
         "level": "mandatory",
         "scope": "machine",
         "source": "sourcePlatform",
         "value": 1

"EnabledPlugins": {
         "error": "This policy has been deprecated.",
         "level": "mandatory",
         "scope": "machine",
         "source": "sourcePlatform",
         "value": [ "Shockwave Flash", "Adobe Acrobat", "Shockwave for Director", "Silverlight Plug-In" ]

Hi,

I also have a customer that's also having the same issue. I have tested this in version 62 (Stable), version 63 (Beta) and version 64 (Canary). The behavior is the same to all these three Channels. Thanks in advance!

It seems that we are having a similar issue. Setting DefaultPluginsSetting to 1 or 3 (I understand 1 is deprecated) and we have inconsistent results with running Flash. Many sites fail to detect it and in the rare event users are prompted, when they choose to accept the content doesn't always load and many times they are prompted again. The allowed sites list also seems to be ignored. If we don't set DefaultPluginsSetting, everything seems to work as expected. This seems very similar to https://bugs.chromium.org/p/chromium/issues/detail?id=654072

I guess I should clarify on my above comment. Our issue is mainly that setting DefaultPluginsSetting seems to cause the Flash allow list to be ignored.

This sounds similar to  issue 779630 . Julian, can you take a look?

Indeed, can you check if the suggestion to explicitly add the hosts you need Flash to work on automatically to the PluginsAllowedForUrls policy as described in C#4 here https://bugs.chromium.org/p/chromium/issues/detail?id=779630#c4 helps in your case?

Adding the hosts (http://* and https://*) to the PluginsAllowedForUrls worked for us. Thanks!

I would recommend getting this to your enterprise support and getting the admin tools to reflect these changes. We were dead in the water until Comment #14

I have created a CL to update the documentation of the DefaultPluginsSettings policy accordingly.

https://chromium-review.googlesource.com/c/chromium/src/+/799871

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4675fd70c024dfd883ec2c378f16a3c9f0af2006

commit 4675fd70c024dfd883ec2c378f16a3c9f0af2006
Author: Julian Pastarmov <pastarmovj@chromium.org>
Date: Thu Nov 30 17:33:56 2017

Document the relationship between DefaultPluginsSettings and PluginsAllowedForUrls policies.

BUG= 775960 

Change-Id: Ic5ec7c97b18f6d0a5e24a7db6f6b14de43a3adb3
Reviewed-on: https://chromium-review.googlesource.com/799871
Reviewed-by: Georges Khalil <georgesak@chromium.org>
Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520588}
[modify] https://crrev.com/4675fd70c024dfd883ec2c378f16a3c9f0af2006/components/policy/resources/policy_templates.json

Verified fixed. The DefaultPluginsSettings policy documentation is updated (see attached screenshot).

Chrome OS: 10323.52.0
Chrome: 65.0.3325.148
Device: Robo360

Deleted: Screenshot 2018-03-08 at 12.13.10 PM.png 112 KB

	Screenshot 2018-03-08 at 12.13.10 PM.png 112 KB View Download