Any user account that uses a roaming profile that upgrades the flash plugin for google chrome from 220.127.116.11.207 to 18.104.22.168 can no longer use the plugin properly.
Websites seem to think that flash is out of date, because you get an update message. When you disable the plugin altogether, you get the message to install flash.
Here is what you get when the plugin is disabled:
Then with the plugin v22.214.171.124 enabled you get this:
When I roll back to 126.96.36.199 it is usable, however I do not want to use the version that is not secure. Affecting roughly 160 users on Virtual Machines. To clarify, I am able to use the plugin just fine on my VMs as long as the user profile is local, and not a roaming profile.
Any help would be greatly appreciated!
I have also noticed that version 188.8.131.52 was placed in the Chrome application directory, and 226 is now in the user directory:
184.108.40.206: C:\Program Files\Google\Chrome\Application\46.0.2490.71\PepperFlash\pepflashplayer.dll
220.127.116.11: \\domainlocation\user_profiles\first.last\AppData\Roaming\Google\Chrome\User Data\PepperFlash\18.104.22.168\pepflashplayer.dll
What is with this change? This is what got me in the direction of the issue being with roaming profiles in the first place.
That's a good question for the Chrome forums, but the short answer is that Chrome has a couple update mechanism (full vs. component updater), and assets seem to show up in different places depending on the mechanism used.