Skip to main content
A
Anonymous
June 6, 2017
Question

In what circumstances does Chrome use system flash vs pepperflash?

  • June 6, 2017
  • 1 reply
  • 2992 views

We are seeing some cases on Windows machines where users have an outdated version of system flash installed, and Chrome defaults to using that over Pepperflash. These are for new Windows profiles, and when you go to chrome://components its still 0.0.0.0 for Adobe Flash (Chrome version 57) and users have a banner saying 'Flash is outdated and blocked'.

I am not clear why Chrome would ever default to system flash, especially an older version? If users click on the component update button for flash, the correct Pepperflash version is installed and the problems go away.

This topic has been closed for replies.

1 reply

_maria_
Community Manager
_maria_Community Manager
Community Manager
June 6, 2017

Hi Amal,

Beginning around Chrome 50, 51, 52 (I don't recall the exact version) Chrome defaults to using the system plugin if the system plugin version is >= to the embedded version.

users have a banner saying 'Flash is outdated and blocked'.

When is the banner displaying?  Please provide exact steps to reproduce.

Please launch Chrome and navigate to chrome://flash.  Post a screenshot of the following fields: Google Chrome, OS, and Flash plugin.

I'll request/have more information after receiving this information.

Thank you.

--

Maria

A
Anonymous
June 6, 2017

Thanks for the quick response Maria!

We were are seeing contradicts this because the version of System Flash that is installed 25_0_0_127 and the latest version which Chrome installs is 25.0.0.171.

Screenshots are below, and please note that when we click on 'check for updates' the Pepperflash component version gets bumped from 0.0.0.0 to 25.0.0.171. But if a user does not manually trigger this update, then Chrome continues to use the outdated system flash version.

Windows 7/Chrome 58x

A
Anonymous
June 6, 2017

No -- this is a VM network which uses test active directory profiles. They do not have an AppData directory when they login for the first time.


FYI @Maria, in our testing we discovered that the problem fixes itself after Chrome's 6 minute window. So, clearly this is a browser bug, and I'll file an issue on Chromium and link it back here. Any insight you can add would be great.. thanks so much!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices