Flash Plugin will not load on new profile
Reported by
urz...@gmail.com,
Jan 12 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Example URL: http://get.adobe.com/flashplayer/about/ Steps to reproduce the problem: 1. Create a new Windows user or login to a Windows device with a user for the first time. 2. Attempt to load Flash content. 3. What is the expected behavior? The Flash plugin should load after 6 minutes or as soon as Flash content is loaded. What went wrong? The Flash plugin should load either after 6 minutes or as soon as Flash content is loaded. The plugin never loads, shows an external not yet present. Trying to update the Plugin directly through chrome://componets gives the below error: An error occurred while checking for updates: Unable to connect to the Internet. HTTP 403 Forbidden. Please check your proxy configuration. (error code 7: 0x80042193 -- system level) Attempting to check for a Chrome update yields the same error. Does it occur on multiple sites: Yes Is it a problem with a plugin? Yes Flash Did this work before? Yes It worked yesterday on the same version of Chrome Does this work in other browsers? Yes Chrome version: 63.0.3239.132 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 28.0 r0
,
Jan 15 2018
,
Jan 16 2018
Unable to reproduce this issue on reported version 63.0.3239.132 using Windows 7 and Windows 10 with steps mentioned below. 1. Navigated to http://get.adobe.com/flashplayer/about/ and clicked on plugin icon and clicked on run flash. 2. Now able to see flash content. 3. Navigated to chrome://help and observed chrome update without any error. Adding Internals>Installer label as this issue is also seen with chrome update. Could some from Internals>Installer/Internals>Plugins>Flash team please have a look into this issue. Thanks!
,
Jan 16 2018
Unable to repro with 64.0.3282.85 with these steps: - delete "%LOCALAPPDATA%\Google\Chrome Beta\User Data" - launch Chrome Beta - navigate to chrome://components - click "Check for update" beneath "Adobe Flash Player" The update arrived in a timely fashion. +waffles to chime on on the specific error seen. Do you know what this means?
,
Jan 16 2018
This was very likely the Omaha outage on Jan 12th. The server went into DoS mode and issued some 403s. It should be resolved now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 12 2018