Flash player inconsistently updates from v23.0.0.166 to v23.0.0.185
Reported by
cbur...@wcpss.net,
Oct 18 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 Example URL: https://i-ready.com Steps to reproduce the problem: 1. Just go to any Flash enabled website with Chrome version 54.0.2840.59 m (64-bit) that has been upgraded from a previous version (clean installs do NOT apply) 2. You are prompted to update your Flash plugin 3. What is the expected behavior? For the Flash content to load without prompting users to update their Flash plugin. What went wrong? Flash is not updating from version 23.0.0.166 to 23.0.0.185. Users are prompted to update Flash plugin when visiting Flash enabled websites. Ultimately I have to delete the C:\Users\<userid>\AppData\Local\Google\Chrome\User Data\PepperFlash\23.0.0.166 directory and restart Chrome. After doing that the problem is fixed. Did this work before? Yes 53 and prior Is it a problem with Flash or HTML5? Flash Does this work in other browsers? Yes Chrome version: 54.0.2840.59 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 If I go to chrome://components, Adobe Flash Player is listed as 23.0.0.166. Hitting update shows it downloading and applying, but then it shows the button as "Check for updates" and the Flash version stays at 23.0.0.166. Uninstalling/reinstalling Chrome does not fix the issue as the local user data (C:\Users\<userid>\AppData\Local\Google\Chrome\User Data\PepperFlash) persists after an install. Deleting that folder fixes the issue. We are using IBM Bigfix to distribute Chrome to end clients. All users have Full Control effective permissions on their AppData folder. User's home directories are redirected but the AppData folder is configured to stay local to the physical machine the user is logged into. All clients are 64 bit running mostly on Windows 7 but also some Windows 10 computers with the same symptoms.
,
Oct 19 2016
,
Oct 19 2016
Unable to reproduce the issue below are the steps I followed on Windows 7 and 10 : Test 1 : 1. Install Chrome Version 51.0.2704.103 2. Flash version 22.0.0.192 3. Open couple of Flash required websites like "http://www.adobe.com/software/flash/about/", "https://helpx.adobe.com/flash-player.html" 4. Checked for Chrome update and got updated to Chrome 54.0.2840.59 Observed behavior : 1. Straight after Chrome got updated Flash version was updated to 23.0.0.185 and everything rendered correctly. Test 2 : 1. Install Chrome Version 53.0.2785.116 2. Flash version 23.0.0.162 3. Open couple of Flash required websites like "http://www.adobe.com/software/flash/about/", "https://helpx.adobe.com/flash-player.html" 4. Checked for Chrome update and got updated to Chrome 54.0.2840.59 Observed behavior : 1. Straight after Chrome got updated Flash version was updated to 23.0.0.185 and everything rendered correctly. Test 3 : 1. Install Chrome Version 53.0.2785.143 2. Flash version 23.0.0.162 3. Open couple of Flash required websites like "http://www.adobe.com/software/flash/about/", "https://helpx.adobe.com/flash-player.html" 4. Checked for Chrome update and got updated to Chrome 54.0.2840.59 Observed behavior : 1. Straight after Chrome got updated Flash version was updated to 23.0.0.185 and everything rendered correctly. cburrus@ just curious are there any policies, Also would like to know from which version of Chrome you were updating please let us know.
,
Oct 19 2016
Prudhvi, I believe this is an issue only with M54, which was shipped with a required minimum Flash version of 23.0.0.185. (I don't know why.) Therefore, Flash 23.0.0.166 and earlier were forbidden from loading. This issue should resolve itself after the browser has been up for 6-10 minutes (assuming Flash can be downloaded and updated in 0-4 minutes), as Flash will update in the background to .185. Deleting the file, as done in the original report, will force an update as soon as Flash content is encountered, effectively accelerating this cycle. > Hitting update shows it downloading and applying, but then it shows the button as "Check for updates" and the Flash version stays at 23.0.0.166. This is very interesting. Did the status go to "component not updated" or "component updated" after downloading/applying?
,
Oct 19 2016
Upgraded mostly from Chrome version 53.0.278.143, however some of them from a previous version if they were powered off. 80,000+ computers in our environment, several thousand showing this issue. Attached is a HTML doc of our exported GP for Chrome
,
Oct 19 2016
waff@ >Did the status go to "component not updated" or "component updated" after downloading/applying? It says component updated and immediately disappears and the "Check for updates" button comes back. As soon as I delete the 23.0.0.166 folder in the PepperFlash folder and relaunch Chrome a new folder appears 23.0.0.185. >This issue should resolve itself after the browser has been up for 6-10 minutes That behavior is inconsistent from what I can see. Some are updating, others are not.
,
Oct 19 2016
,
Oct 21 2016
Unable to reproduce this issue in Windows 10. The tested procedure is (1) Installed chrome version 53.0.2785.143 with flash version 23.0.0.162 (2) goto settings page -> about page to update the chrome. (3) After update, relaunch the browser (4) Now check the Chrome version is 54.0.2840.71 and flash version is 23.0.0.185 Please look into the attached screenshot and let us know if you have observations/quires. Thank You...
,
Oct 25 2016
,
Oct 25 2016
Experiencing this issue with multiple Windows 7x64 machines. We're distributing the Chrome MSI with SCCM. Removing & Reinstalling latest version do not correct the issue. Installing the PPAPI version of Flash Player corrects the issue.
,
Oct 26 2016
I'm showing the same issue with Windows 7 x32. Adobe Flash player out of date. Go to Components, try to update Adobe. Flash Player - Version: 23.0.0.166 Status - Component not updated Tried to remove the PepperFlash folder and does the same thing. (Not sure what that was supposed to do, but tried it anyways) Running Version 54.0.2840.71 m
,
Oct 26 2016
Correction, that was with Windows 10 Anniversary edition. Win7 x32 seems to update to .205.
,
Oct 26 2016
Windows 10 just went to .205 also. Seems the new .205 fixes the update issue
,
Oct 26 2016
Don't have the big scale issue some of these folks have but I'm experiencing similar issues on a Mac. OS 10.11.6 Plugins shows: Adobe Flash Player v 23.0.0.185 ShockWave Flash 23.0r0 Location: internal-not-yet-present Type: PPAPI (out-of-process) Components shows: Status: "Downloading" v - 0.0.0.0 but it never finishes downloading, clicking "check for updates" changes status to "checking for status" but it never returns a status. One of the comments suggests that the issue should resolve in 6-10 min...I have left Chrome up for hours, it does not resolve. Please feel free to contact if you need further info
,
Oct 27 2016
There was a server-side issue on October 25th and 26th that caused the behavior described in #11/12/13, and possibly the behavior described in #10. We've addressed the problem and taken steps to prevent it from recurring. Re #14: It looks like the download is never completing for you; If you're still experiencing the problem, I'm curious to know if what you see at the following URL in Chrome: http://redirector.gvt1.com/edgedl/release2/test
,
Oct 28 2016
Waff, The link you provided takes me to a page that says "You have connectivity". Additionally when I look under components and plugins Adobe Flash shows shows version 23.0.0.205 and a status of no update. Lastly, I am now able to view flash content. Thank you!
,
Nov 2 2016
waffles@, As per comment #16 Could you please confirm if the issue can be closed.
,
Nov 2 2016
Yes, I think this can be closed. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ligim...@chromium.org
, Oct 19 2016Components: Internals>Plugins>Flash
Labels: pre-stable-54.0.2840.59 M-54 Needs-Bisect