Few screenshots

Deleted: 0 (1).jpg 187 KB

	0 (1).jpg 187 KB View Download

Deleted: 0.jpg 147 KB

	0.jpg 147 KB View Download

Deleted: 0 (2).jpg 74.9 KB

	0 (2).jpg 74.9 KB View Download

Deleted: OiCzws8Y2c5.png 99 KB

	OiCzws8Y2c5.png 99 KB View Download

This link has reports from .164, most others say .162
https://productforums.google.com/forum/#!topic/chrome/xoZJvPplm8w

The screenshots in #1 show somewhat random issues.

Yes, on this thread https://productforums.google.com/forum/#!topic/chrome/xoZJvPplm8w users tried steps to update plugin from 22 to 23..162 and now .164 but issue still persists.

When reproducing on cnn.com, I am on version 23.0.0.151 
Is there anything I can ask users to provide ? or should I ask users to visit this bug ?

Here are the big pieces of data that would be helpful:

1.) Chrome version numbers (as well as platform info).
2.) What setting do they have in chrome://settings/content for "Plugins"?
3.) What does chrome://plugins say for "Adobe Flash Player" (Location is perhaps the most interesting field)?

Looking at the referenced feedback.

Two of the reports are from XP/Vista/Chrome 49 users.  Given that we aren't supporting/testing/building for those platforms, I'd suspect that the plugin may have an incompatibility there. For those, the right recommendation would be to clear the component.  We've stopped doing Flash updates for users below 50, if they remove the component they won't get updated (and the local version of Flash will kick in).  For the time being, those likely aren't actionable reports...let's take those off our radar, so that we can start narrowing the space of problems.

The other two feedback were from Mac users likely affected by the issue w/ the .162 component packaging.  It's possible that there is an issue w/ the .162 to .164 update path that maybe blocking these users.

The screenshot is for a crash (having crash reporting enabled and a crash id would be helpful there).

All of our users in OS X running chrome beta hit this bug this week. I've tried most of the steps in the original post to no avail (so far).

Here's another thread in Adobe's forums with an Adobe staff member mentioning that "Google states the issue has been fixed, but we're still seeing some instances of the issue" and advising to uninstall chrome, delete PPAPI flash folder and reinstall chrome (which doesn't WFM): https://forums.adobe.com/thread/2205609

On my home MBP, I'm running:

Google Chrome	54.0.2840.16 (Official Build) beta (64-bit)
Revision	011cbb51fc15804af6fa14e68231617d84437c6f-refs/branch-heads/2840@{#225}
OS	Mac OS X 
JavaScript	V8 5.4.500.18
Flash	23.0.0.164
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.16 Safari/537.36

Content settings is set to "Detect and run important plugin content (recommended)."

Details from chrome://plugins:

Adobe Flash Player - Version: 23.0.0.164
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.164
Location:	/Users/[user name]/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.164/PepperFlashPlayer.plugin
Type:	PPAPI (out-of-process)
 	Disable
MIME types:	
MIME type	Description	File extensions
application/x-shockwave-flash	Shockwave Flash	
.swf
application/futuresplash	Shockwave Flash	
.spl

Screenshot of error as I see it at Adobe's flash about page.

Deleted: PPAPI flash couldn't load plugin OS X.png 126 KB

	PPAPI flash couldn't load plugin OS X.png 126 KB View Download

I'm seeing the same issue on my home machine too.

Mac OS X 10.10.5 "Yosemite"
Chrome 55.0.2853.0 (Official Build) dev (64-bit)
and Chrome 55.0.2857.0 (Official Build) canary (64-bit)

Flash version: 23.0.0.164

I tried running with a fresh profile (--user-data-dir=/tmp/flashtest), logging enabled and --v=1, and found this suspicious message:

Google Chrome Helper[62243:11968133] Error loading /private/tmp/flashtest/PepperFlash/23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer:  dlopen(/private/tmp/flashtest/PepperFlash/23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer, 262): no suitable image found.  Did find:
/private/tmp/flashtest/PepperFlash/23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer: code signature invalid for '/private/tmp/flashtest/PepperFlash/23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer'
No PPP_GetInterface in plugin library
Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService

Any idea what "code signature invalid" could be?

Big thank you Dominic!  That's an excellent lead.

Hey Yuzhu/ Brett, do either of you happen to know the code path that would trigger the loading / validation logic?

(I don't know much about Mac code signing.)
Looking at comment#9, it seems the binary may not be signed properly? Could anyone verify?

Hey Mark,

You may have the best perspective on code signing issue for OSX.  Looking at comment #9, do have a sense for how we could validate this?

There’s a missing file.

First, I ran

codesign --verify --verbose=6 [/path/to/]PepperFlashPlayer.plugin

I saw:

PepperFlashPlayer.plugin: invalid Info.plist (plist or signature have been modified)
In architecture: x86_64

Then, I ran:

codesign --display --verbose=99 PepperFlashPlayer.plugin

That shows a bunch of stuff, but the part I’m focusing on here is:

    -3=6c1894a7fdad9b4525d50ff71a9d0e015f168129
    -2=600bb207f835937eac4a833151f2a44e9f7f6356
    -1=a17466320376c83b9f552b1c16750ca10c820583

Special slot -1 is for an Info.plist. (Look at the “Special hash slot values” enum in http://opensource.apple.com/source/Security/Security-57337.60.2/OSX/libsecurity_codesigning/lib/codedirectory.h). The Info.plist must be present and have a SHA-1 hash a17466320376c83b9f552b1c16750ca10c820583. In our copy of the plug-in, there is no Info.plist. If the Info.plist were expected to be missing, the hash from codesign --display would show up as all zeroes.

We do have the Info.plist file in the copy of PepperFlashPlayer.plugin that I see in an internal checkout, but that file is evidently not making it to the component-updated copy. Since we’ve got it, we’ve just got to figure out what’s building or distributing the component and fix it to include the Info.plist.

Should we drop the non-Mac from the OS field now? If there are other problems on other OSes, they’re certainly different from this Mac-specific one.

P.S. Sounds like we should get Joshua involved.

Current serving 23.0.0.166 on canary with the correct Info.plist file.

Can you show me (privately, if necessary) where this is set up?

It does look like I'm missing Info.plist:

~/Library/Application Support/Google/Chrome/PepperFlash
> find .
.
./23.0.0.164
./23.0.0.164/manifest.fingerprint
./23.0.0.164/manifest.json
./23.0.0.164/PepperFlashPlayer.plugin
./23.0.0.164/PepperFlashPlayer.plugin/Contents
./23.0.0.164/PepperFlashPlayer.plugin/Contents/_CodeSignature
./23.0.0.164/PepperFlashPlayer.plugin/Contents/_CodeSignature/CodeResources
./23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS
./23.0.0.164/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer

Copying a "good" 23.0.0.164 directory fixes it for a new profile, but not an existing profile. When I run with an existing profile I see the same "code signature invalid" message in the logs.

Thankfully a fresh profile seems to work...

Also, Adobe's "about flash" page says "You have version 23,0,0,162 installed", which is odd - does the internal version not match the external?

I'm still a little puzzled why we didn't see the "couldn't load plugin" across all of MacOS, due to the missing Info.plist file.  There seemed to be some randomness, even on the most modern installs of MacOS.

That being said, the non-policy related MacOS ("couldn't load plugin") issue appears to be under control... now to fix the blocking policy problem.

I manually updated the component and got version 23.0.0.166, and now Flash is working fine! Please push it out to all users!

Adobe's page still says the version is 23.0.0.162, FWIW.

Does the inconsistency have anything to do with Chrome being installed for all users vs one user? I have multiple active users on my home computer.

Adobe provided only one binary 23.0.0.162. All other versions discussed here are spoofed to satisfy the Chrome component updater to overwrite bad installs.

Same issue for me here. Shockwave keeps crashing. I check for updates for the components and i'm still seeing  23.0.0.164 flash .

Google chrome is latest version: Version 53.0.2785.116 m
Windows 8.1

persius, this sounds different. Best if you file a detailed new issue for the crash with repro instructions (about:flash data, websites affected).

This issue was primarily about a packaging issue w/ the Flash component for MacOS, which has been resolved (the reason for the dupe).

There is a separate open issue  crbug.com/641028  that presents similarly "Movie not loaded."   The issue unfortunately is restricted, however we have identified the issue (a specific change that happened before M54 branched) and are working on a patch (https://codereview.chromium.org/2349443003/).  Should be fixed on Canary by early next week.

I have this this exact same issue on Chrome 54.0.2840.59 and Flash 23.0.0.185 and have tried all of the above same techniques for making it work to no avail.

To clarify... 99% of my 200+ users are on MacOS 10.10.5 network home folders with up to date Chrome 54.0.2840.59 and Flash 23.0.0.185.  My mac is on 10.11.6 (same Chrome and Flash versions and a network home) and I've tried copying it to the others users on our network and deleting/replacing their Pepper Flash in ~/Library/Application Support/Google/Chrome/ with my PepperFlash folder that is working for me and while it's not generating the invalid code signature on my system it's not working at all for my users.  I copied via CLI on our server and reset the ownership permissions after the copy too.

Is this still not fixed?  What's the problem?

This JUST started today for us.  Windows 10, Chrome Version 54.0.2840.71 m (64-bit).  Both chrome and flash saying up-to-date, but still receive alerts that flash is not.

On Windows 7 Chrome "Version 54.0.2840.71 m (64-bit)" the Adobe Flash Player is Version: 23.0.0.166 and in chrome://plugins/ it's prompting to Download Critical Security Update for it but in chrome://components/ it's refusing to update it, after clicking on Check for update it comes back with Status - Component not updated, Chrome itself is up to date.

On another machine Windows 7 Chrome "Version 54.0.2840.71 m" (note no 64-bit) the Adobe Flash Player is Version: 23.0.0.205 and it's working without issues.

We are seeing a different variation of this issue for some of our customers. We have not been unable to reproduce it on any of our VM's. 

Chrome version is 54.0.2840.71 PepperFlash is 23.0.0.185, OS is Windows 7. This only seems to be reproducible for new Windows profile. We write educational software, and our customers are often creating new profiles because their students move from machine to machine.

Step to reproduce bug:
For a new Windows 7 profile, when Chrome launches a site with Flash content for the first time, we get a message that Flash is out of date. (the PepperFlash component version at that time is 0.0.0.0).
 
Going to a new tab and loading a site with flash content, fails the first time, but works on the first refresh. The version is no longer 0.0.0.0, but its 23.0.0.185. Now, going back the original tab and refreshing the original page works without a problem.
 
This has been very problematic for us because we are unable to reproduce this issues on any of our VM's. We are not sure why the first load of Flash content seems to fail when there are new Windows profiles. 

Any help or feedback would be appreciated. 

We have 100+ users from MacOS 10.10.x to MacOS 10.11.6 with network home folders and up to date Chrome 54.0.2840.71 (64-bit) and Flash  23.0.0.205.  I've 
  - Tried deleting/replacing their Pepper Flash in ~/Library/Application Support/Google/Chrome/
 - Tried re-installing chrome. 
 - Tried rebooting
 - Tried clearing cache, history, profile
 - Tried Disabling/Enabling via chrome:plugins
 - Tried Disabling/Enabling via chrome:components
 - Killing Extension: ShockwaveFlashPlayer from Task Manager in Chrome. 

to no avail.

For Enterprise deployments, where network shares/ roaming profiles are being used, I'd recommend setting policy to disable component updates(1) and deploying an Enterprise distribution build of Flash Player (2).

For consumers, where network shares are an issue, it should be possible to use a System level Flash Player installation, which can also be downloaded from Adobe (3).

(1) - https://www.chromium.org/administrators/policy-list-3#ComponentUpdatesEnabled
(2) - https://www.adobe.com/products/flashplayer/distribution.html
(3) - http://www.adobe.com/go/chrome/

Ok. Followed the 1-3 steps.

Originally I had this message in chrome://plugins, which caused a Flash error on every player or page using Flash:

Adobe Flash Player - Version: 23.0.0.166 Download Critical Security Update
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.166
Location:	C:\Users\Me\AppData\Local\Google\Chrome\User Data\PepperFlash\23.0.0.166\pepflashplayer.dll
Type:	PPAPI (out-of-process)
 	Disable


I made sure the box for (always allowed to run) was checked, downloaded the Flash player from link-

https://www.adobe.com/products/flashplayer/distribution.html

Now I see this:

Adobe Flash Player - Version: 23.0.0.205
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0 System
Version:	23.0.0.205
Location:	C:\WINDOWS\system32\Macromed\Flash\pepflashplayer64_23_0_0_205.dll
Type:	PPAPI (out-of-process)


The download critical updates message and disable warning under the PAPI section is now GONE.  It does still have the same version of Flash and it does still state "(out-of-process)".  

But this does seem to have solved the issue. I hope it solves it for others. I do not know if it will last, or if this is an enterprise level solution, but as an individual corporate user with Admin rights, it worked for me.

Hi,
For the Mac OS and network shares and roaming profiles, I have tried comment 34 suggestions and installed PPAPI from (3) link and followed (1) instructions provided in the link. Added preference name: ComponentUpdatesEnabled and disable it in ~/Library/Preferences/com.google.Chrome.plist by setting it to <key>ComponentUpdatesEnabled</key>
	<false/>

Restarted Chrome to no avail.  Tried this on two network accounts.  The issue persists.
"Couldn't load plugin" 

I've been having issues with Flash Player within my Chrome browser for many versions now.  So tired of deleting folders, etc.... Version 54.0.2840.71 m (64-bit)

Any updates on this issue?
We have a good number of Mac OS X users having the same issue still. We are waiting for a fix.  Previous versions of Chrome including 52 used to work without problems.  

The security concerns with network file systems are great enough that the current thinking of the team is that users (on any OS) using a user-data-dir in a network location will have to install Flash on the local disk by using one of the Adobe-published installers. Unfortunately, this is broken for many users in M54, due to a detail about how Chrome breaks ties between multiple sources of Flash binaries.

There is a CL landed in M55 that is expected to fix any cases where an up-to-date Flash has been installed on the system (i.e. by an Adobe installer, not just by Chrome).

There is mixed support for merging that change into M54 (stable).

It would be helpful if you could confirm that you don't experience the issue in the current beta version (55.0.2883.35).

Thanks for the update.
Adobe Flash Player latest version downloaded from http://www.adobe.com/go/chrome/ both PPAPI and NPAPI versions are installed on local disk by a local admin.  I also have installed the Chrome Beta version 55.0.2883.35 which is also in local disk using a local admin account.  

The issue persists as network users with their home directories in the network still get "Couldn't load plugin" in Chrome's Beta version.  We are seeing this issue on OS X 10.10.x

However to provide insight in the development of future releases, and if it helps with the troubleshooting, when I have created a symlink for the following directories 

~/Library/Application\ Support/Google/Chrome  
and 
~/Library/Application\ Support/Google/Chrome\ Canary 

to the local disk, the issue is resolved regardless of Chrome version and Adobe Flash Player version. 

Again just to emphasize that we never have to do this before and we certainly do not want to do this for all our users.

Hm. If you're willing, I would like to know what happens if you do the following:

(1) Install Chrome Beta, if you have since removed it.
(2) Install Adobe Flash (PPAPI) via https://get.adobe.com/flashplayer/otherversions/ if you have since removed it.
(3) Delete ~/Library/Application\ Support/Google/Chrome.
(4) Launch Chrome Beta.
(5) Confirm that when you navigate to chrome://chrome you see version 55.0.2883.35.
(6) Navigate to chrome://plugins, press "+ Details", and report the "Version" and "Location" for Adobe Flash Player.
(7) Navigate to http://www.adobe.com/software/flash/about/ and confirm that you still get "Couldn't load plugin".
(8) Navigate to chrome://components. Confirm the version of Flash reported there is 0.0.0.0. Click "Check for Update" next to Flash, and confirm that the version changes to 23.0.0.207.
(9) Navigate to chrome://plugins and report the Version and Location of Flash.

I'm interested in what you see for the version and location of system Flash in steps 6 and 9.

@waff via Comment#42

Step 5 yes confirmed version of Chrome Beta at 55.0.2883.35

step 6:
Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name:Shockwave Flash
Description:Shockwave Flash 23.0 r0 System
Version:23.0.0.207
Location:/Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin
Type:PPAPI (out-of-process)

Step 7 played the the bouncing cube flash video on Adobe's site

Step 8 yes flash in components is 0.0.0.0

Step 9 yes it moved to 23.0.0.207 and now shows this in plug-ins, no
mention of the "in-process" component version:
Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 23.0 r0 System
Version: 23.0.0.207
Location: /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin
Type: PPAPI (out-of-process)

steps 1-4 done

(5) version 55.0.2883.44 (64-bit)

(6) 
Adobe Flash Player - Version: 23.0.0.185
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.185
Location:	internal-not-yet-present
Type:	PPAPI (out-of-process)


(7) Yes we still get "Couldn't load plugin".

(8)Adobe Flash Player - Version: 23.0.0.207
Status - Component updated

(9) Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.207
Location:	/home/username/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.207/PepperFlashPlayer.plugin
Type:	PPAPI (out-of-process)

Re #43, thanks; looks like this will be working for you in M55+, then. If you need it merged into M54, I suggest starring or chiming in on  issue 651945 , since this one is actually closed as a duplicate of another pathology.

Re #44, it looks like Chrome is not detecting the system installation of Flash that you did in step (2). Do you have a file at /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin ? Did anything unusual occur with the installation? I'm not sure how to debug the Adobe installer itself.

Do you have a file at /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin ? 
** NO

Did anything unusual occur with the installation?
** NO, it was pretty straight forward.  Downloaded the DMG, mount it, run the installer, went through the installation wizard and installation completed successfully.


Repeated the steps again from #42:
(5)Version 55.0.2883.44 beta (64-bit)
(6)
Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.207
Location:	/home/username/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.207/PepperFlashPlayer.plugin
Type:	PPAPI (out-of-process)


(7) Yes we still get "Couldn't load plugin".

(8)Adobe Flash Player - Version: 23.0.0.207
Status - Component updated

(9)Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0
Version:	23.0.0.207
Location:	/home/username/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.207/PepperFlashPlayer.plugin
Type:	PPAPI (out-of-process)

Thanks. Can you figure out where the Adobe installer placed PepperFlashPlayer.plugin?

Thanks. That is the answer!

My test machine is an OS X 10.10.3 
When I installed PPAPI from https://get.adobe.com/flashplayer/otherversions/ I do not have this file /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin

I installed PPAPI on OS X 10.10.5 and I have /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin there.

I installed PPAPI on OS X 10.11.6 and I also have /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin there.

So I copied /Library/Internet
Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin from the 10.11.6 installation and placed it in the 10.10.3 which had Chrome Beta version 55.0.2883.44 (64-bit) for testing.

This time http://www.adobe.com/software/flash/about/  loads fine without plug-in issues on the OS X 10.10.3

This is a doable work around for us.
Thanks.

Now step 9 shows:
Adobe Flash Player - Version: 23.0.0.207
Shockwave Flash 23.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 23.0 r0 System
Version:	23.0.0.207
Location:	/Library/Internet Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin
Type:	PPAPI (out-of-process)

So I just noticed when following along here.  When pepper flash 23.0.0.205
from adobe is installed and I remotely update to .207 via the adobe system
administrator package for mac the file
/Library/Internet Plug-Ins/PepperFlashPlayer/manifest.json does not get
updated with the correct version on line 4 of that file.  It still said it
was .205

Hm, that seems bad. If the /Library version remains out of date, Chrome will try to use the newer version in ~/. You might consider filing a bug with Adobe.

+Adobe folks, specifically regarding the last set of comments (appears there might be an issue w/ the updater from the Adobe site).