Since Chrome 56 a nagging yellow strip shows up in some websites: Then I had a look at chrome://plugins Anyone know what's going on? Why it has an outdated version as it is supposed to integrate a new AFP version on every Chrome iteration.
Thanks. I already did that but just want to know what is going on. Why Chrome 56 did that. I never had to update manually ever before. Btw, does your AFP plugin is updated without doing manually?
I have AFP disabled so I wouldn't know. Perhaps you have another installation of Flash on your system and Chrome is telling you that it's out of date. Go into details in the plugins page and see if Chrome is picking up two paths for the Flash dll.
Location: C:\Users\MrX\AppData\Local\Google\Chrome\User Data\PepperFlash\24.0.0.186\pepflashplayer.dll I assume this is the right path for Chrome's AFP plugin. In addition, I have KB3202790 for Windows 8.1 x64. It gives a Flash version 23.0.0.207. So I can't figure out what's going on.
Besides the red typeface and the old version number, nothing looks out of the ordinary. Strange.... Maybe take a look at the chrome installer log file c:\Users\MrX\AppData\Local\Temp\chrome_installer.log. Windows notepad is a mess and shows a blog of text for me so I use something like notepad++. I can't tell you exactly what to look for in there but a search for "flash" wouldn't hurt. I remember when I had issues with google update failing to update chrome, the installer log was helpful.
I have not the same version as you on my Chrome 56.0.2924.87, really strange. Uhm, which package do you use exe or msi, maybe the msi package missed something. You should try to uninstall completly Chrome and his trace, and reinstall again Rules.
Thanks for your comments. Maybe next time I install a new Chrome version cause the log file is gone. You see, I've always pass Ccleaner after installing Chromes versions. Never faced an issue before.
I use the msi package, correct. I used it on April 2016 when I formatted and reinstalled Windows 8.1 x64 on that date. Afterwards, all subsequent updates are via online Chrome updater.
Ok, so you should really try the exe one, and for my concern, when a upgrade comes out, i always download the offline installer and install-it over the previous one. Why?, maybe i'm faulty but i suspect integrated SwReporter tool doing something when you clic on about chrome, but i don't care of that since i have blocked it's activity using restricted app list module in SpyShelter Fw. Rules.
If i look at my directory, i can see 24.0.0.194. But Google should update it automatically After looking in my logfiles, "pepflashplayer.dll" was updated to 24.0.0.194 on the 11th of January. Does Google have sufficient rights to write to the PepperFlash-directory? Or you can try to install a portable version of Chrome and then copy the whole PepperFlash-directory from your portable version to your user-directory.
Personally, I would disable the built in Flash Player binary because I don't like it when Chrome sometimes runs it from User directories between updates. I would disable it then install the PPAPI Flash from Adobe which will auto-update itself (often sooner than Google does) and the binaries are the same at the end of the day. They will then run from Windows directory and have more protection there. Try that it maybe it might just get rid of the outdated message as well. No idea why you are getting outdated message. If this message continues, you can get rid of it with a command line by adding the line to the target box of your Chrome shortcut. Code: --allow-outdated-plugins But regardless, it would be nice to get to the bottom of why it's referring to the binary as outdated because that is odd for sure.
idiocrazy - npapi is abandonned, but ppapi ist still used. reason for me to use opera or vivaldi: no flash inside
Thanks @all I did this yesterday in shadow mode (SD) just to test and it worked. Maybe it had something to do with the msi installer I used months ago. If I don't get any other solution even from Google company then I'll use the PPAPI Flash from Adobe.
I checked my version and also had an old one installed (.154). I navigated to chrome://components and used Check for updates and it installed latest version with no problem. I've used standalone installer to install Chrome few days back.
Here it is the PPAPI Flash from Adobe. Looks good: Now the files are located in the system space as you can see.
Good to see, makes much more sense there. Also whenever an urgent security update for Flash comes out you wont need to wait for Google to update it. There will be a Flash Updater scheduled task which you can either wait to run each day or manually run that task whenever a specific security update is available. It will happen automatically even if you forget to check.
And the advantage of installing the PPAPI-plugin is, all installed (or portable) Chromium-based browsers are using it. So they are not using the "builtin-module" if they can find one in c:\windows\system\Macromedia\Flash\...
Now I wonder whether I have to delete those files in C:\Users\MrX\AppData\Local\Google\Chrome\User Data\PepperFlash\24.0.0.186\ to stay safe and disable the built-in module within Chrome.
