Chrome x64 should detect if version of PepperFlash updated by component updater is x32 and if yes, then download the x64 .dll and associated manifest.

Unable to reproduce the issue on windows 7 using chrome latest stable M49-49.0.2623.110 on both X32 and X64 
Flash version:21.0.0.197
Sample webpage: http://www.dhs.state.il.us/accessibility/tests/flash/video.html

riff@ - Observed that your chrome is not updated to the latest version M49-49.0.2623.110. Could you please upgrade to latest version and check for this issue. In case is issue still persists please provide the sample URL of the webpage to test this issue from QA end.

Thanks!

Hi there:

I was able to reproduce this on a Windows 7 x64 box:

1. Install Google Chrome using MSI: x32 49.0.2623.87
2. Verify version of Flash by going to:
http://www.adobe.com/software/flash/about/ - version at this stage:
20.0.0.267
3. Update Flash to 21.0.0.197 by using component updater
(chrome://components)
4. Without uninstalling x32, install Google Chrome x64  using MSI: x64
49.0.2623.87
5. Verify version of Flash by going to:
http://www.adobe.com/software/flash/about/ - "Couldn't load plugin

The reason is because Chrome is loading the updated x32 dll from the user
data folder... and because the browser is now x64 the x32
pepflashplayer.dll from the user data folder will not be compatible.

----

However, in step 4. if I install 49.0.2623.110 x64, I am not able to
reproduce the error because Flash instead of defaulting to user data folder
loads the updated 21.0.0.197 from: C:\Program Files
(x86)\Google\Chrome\Application\49.0.2623.110\PepperFlash\pepflashplayer.dll


-----

Essentially, the "bug" is that when upgrading from the same version number
of Chrome x32 to Chrome x64, pepflashplayer.dll needs to revert back to the
default location as opposed to loading the updated x32 version from the
%localappdata% folder.

Or, should we take this to mean that when upgrading from x32 to x64 Chrome,
make sure the x64 version is n+1 of the x32 version...?

Thanks!

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot