Having the same issue on multiple machines at my company, Chrome is updated to the latest version, yet, webpages using flash say that flash is outdated.  Uninstall and reinstall did not work.  Had to manually install the ppapi download package from Adobe's website for the error to go away.

Re: #1 This issue is very specific to Chromebooks. I suggest filing a new issue with details (OS, Chrome version etc.) for your work machines.

Re: #2 This isn't chromebook specific. I, too am unable to update my Flash component.

Version 58.0.3013.2 canary SyzyASan
Win 10 x64.

Then please file a new issue.

after restart system the flash version is still same as before (24.0.0.221), The flash version on components page is 24.0.0.186

My beta channel samus did get the yellow button but after restart had 24.0.0.221. This needs some investigation.

ihf@, can you elaborate? Are you saying the machine component updated when you already had the most recent version of flash player?

hsiangc@, the machine will not component update if the server is not serving a most recent version of Flash player then your machine has installed. Let me see what version of Flash we are serving up for beta.

Omaha is pushing 25.0.0.113, but the question is to which branch? I am not good at reading it.
https://omahaconsole.corp.google.com/product?pid=1911

Per waffles@ we are serving 24.0.0.154 to beta.

https://omaharelease.corp.google.com/product/1911/cohorts might be easier to read.

Googlers:      25.0.0.113
Canary:        25.0.0.113
Dev:           24.0.0.184
Beta:          24.0.0.154
Everyone Else: 24.0.0.154

This all makes sense now. I can update these, but I will coordinate with Greg and Ketaki on when it is best to not cause more churn.

waffles@, thanks! That page is a lot easier to read. How do we identify "Googlers"? Our test accounts for manual testing are @gmail.com. 

A device is considered a "Googler" device if and only if it is connecting to the server from the corporate network (e.g. Google-A, not Google-guest).

waffles@, thanks! Ilja, Greg & Ketaki, can we consider making dev the same cohort as Googlers & Canary? It would simplify ToT testing for our team. 

There is a reason why Googlers and Canary get it automatically right away. So you should use a canary build for testing this. I think in the future we could consider sending the binary to dev channel as well automatically, but I think for now it is too early to do so.

Hsiang, did you have a chance to test this on dev channel today? We fixed some bugs and I upreved the binaries served on Omaha.

Yes, the issue is fixed on M-58 9331.0.0/58.0.3027.0. After update finish and flash version will updated to 25.0.0.119, both component and flash page are keeping same version flash. I will check M-57 later once the fix is on M-57

Thanks. I just verified this in M-57 Beta myself using the latest beta build from the build server, so I am glad it works on dev too.

We just branched M58, so things got a little complicated. Also we got 25.0.0.127 Flash build and we have natural alignment of release dates. So I put the binary in the image on all branches. So, there is going to be a natural race and the outcome undetermined. 

Hsiang, in other words you will see slightly strange behavior next week. I guess best to put your observation here with CrOS build number and Flash revision and I check that it makes sense for that branch.

ihf@ Have we merged this to M57 yet? We have a beta coming up this thursday. Please request a merge and merge it soon after so it makes it into this build.

It is all merged. I am just waiting for verification.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-57; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-57 label, otherwise remove Merge-TBD label. Thanks.

Joseph@, please update this thread with build number/flash version numbers (built in & CU) that you're seeing in your testing.

I just check M-58 build 9334.2.0/58.0.3029.6, both flash version in component & flash page are 25.0.0.127. I will check M-57 beta build once the build is available

ihf@ with current M-58 build 9334.3.0/58.0.3029.6, the flash version on component page always display as 0.0.0.0 after component update, is this right behavior? please check screenshot

Deleted: Screenshot -component updater.png 72.4 KB

	Screenshot -component updater.png 72.4 KB View Download

the flash version on chrome://flash display correct version as 25.0.0.127

That's expected as we are serving 25.0.0.127 to dev and canary, so it will not update unless a newer Flash is available. Thanks for checking.

Thank you, marking as verified.