In Chrome 54, there is an additional policy that was rolled out. It's called ComponentUpdatesEnabled. You can find more information about the policy here:

https://www.chromium.org/administrators/policy-list-3#ComponentUpdatesEnabled

You need to enable it so that components can be updated, either automatically or manually. 

Matt, FYI - maybe better documentation is required here?

I figured out the issue. Symantec EP is blocking the download of pepflashplayer.dll

thanks all!

I would like to better explain the actual problem, which is rekated to SEP anti-virus. The file (crx) is downloaded OK. It is extracted OK. Chrome then tries to move the file to the user directory. SEP at the same time has a lock on the file, making tge move fail.

While SEP is somewhat the root cause here, Symantec had indicated that there is no quick fix and makes us wait for a new version.

Chrome is best placed to overcome this issue: if you add a simple check for this and/or try a copy to avoid the lock, millions of enterprise users will no longer suffer from this issue.

Easiest solution is deploying chrome Papi to all machines and enable auto
update flash player service. This way both version of flash will update
together once you configure the mms file to auto update.

That requires an additional rollout, close follow-up, release schedules, ... while we are trying to move to a more "out of the box" situation. Also, this probably affects the other components as well.

For reference, Symantec has a support article on the issue here: https://support.symantec.com/en_US/article.TECH236173.html

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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