Chrome Couldn 39;t Load Plugin Flash Player
Christian Erdmann
When the flash player stops loading from one day to the next, it's possible that a recent DLL update to C:\Users\\AppData\Local\Google\Chrome\User Data\PepperFlash\20.0.0.xxx\pepflashplayer.dll is the cause. The xxx can vary over time: 267, 286..
To test the DLL, hide/rename it as pepflashplayerHide.dll. Close/open Chrome, which will now use it's builtin DLL. If the player works, you've found the culprit. You can stop with the Hide workaround or try to fix the problem.
To correct the problem, delete the PepperFlash folder. Close, open Chrome: the flash player should load. If the problem reappears (after the folder auto updates), there may be permissions problem (see below).
--Details-- The DLL won't load if it's 32/64 bit-type doesn't match the bit-type of Chrome. A mismatch can occur when you switch 32/64-bit Chrome versions and there was a flash player security update lately (here 12/24/15).
The 32/64-bit conflict is being worked as bug 546017. Institutional users may see the same "Couldn't load plugin" failure, but this is related to network share permissions. See bug 572131 for details.
In versions of Chrome prior to version 57, it was possible to configure Flash via chrome://plugins however this feature has since been removed. For the newest versions of Chrome, if the browser displays the error "Couldn't load plugins" then try the following remedies:
When trying to run any SAP provided dashboard in a 9.1 cockpit I get the error "couldn't load plug in". I can run the dashboards outside of the cockpit and Crystal connects just fine. Has anyone seen this yet?
You just need to open File Explorer and go to C:Program Files (x86)GoogleChromeApplication90.0.4430.93PepperFlash. Then rename the pepflashplayer.dll file to pepflashplayerX.dll. After that, you can restart Chrome and check if it works properly.
If you are reading this, you probably got the "Couldn't load plugin" error. When you get this error, it means that some of your browser's features are not working correctly. In most cases, this error appears because of the Adobe Flash Player plug-in or PepperFlash.
Pepper Flash Player is maintained by Google, and it is newer than Adobe Flash Player. Sometimes it helps to delete the PepperFlash folder from your computer so you would not get the "Couldn't load plugin" error while browsing the Internet. To delete the PepperFlash folder, type "run" in Search and click the "Run" result.
It will open the "Local" folder for you. Follow this path to find the PepperFlash folder: "Google > Chrome > User Data". In the User Data folder, locate the "PepperFlash" folder and simply right-click on it, and select "Delete" from the context menu to delete this folder. See if the "Couldn't load plugin" error persists.
Follow this path to find the pepflashplayer.dll file: "Local Disk (C:) > Program Files (or Program Files (x86) > Google > Chrome > Application > 64.0.3282.140 (that is the version of your Google Chrome, it may be different on your computer) > PepperFlash".
Find the pepflashplayer.dll in the PepperFlash folder and right-click on it. Select "Rename" from the dropdown menu and change the file name to "pepflashplayerX.dll". Close the window and restart your Google Chrome browser to see if the "Couldn't load plugin" error persists.
Such content can be viewed in a web browser on any computer with the Shockwave Player plug-in installed. Sometimes you can fix the "Couldn't load plugin" error by stopping and restarting the Shockwave Flash.
Now that you opened the Google Chrome Task Manager, find Shockwave Flash (it can be named Plugin Broker: Shockwave Flash or Plugin: Shockwave Flash as well), select it and click "End process". Restart your Google Chrome and see if the "Couldn't load plugin" error still persists.
There will be two options available: "Ask first (recommended)" and "Block sites from running Flash". Make sure that "Ask first (recommended)" is turned on. If not, then toggle the switch to turn it on. Restart your Google Chrome and check if the "Couldn't load plugin" error still persists.
Sometimes this "Couldn't load plugin" error can appear because of the corrupted system files, and to fix this issue, you need to run SFC and DISM scans. This guide describes how to run the System File Checker tool (SFC.exe) to scan your system files and repair missing or corrupted system files.
You might need to perform a DISM scan to fix the "Couldn't load plugin" error. DISM stands for Deployment Image Servicing and Management, and it can be used to repair and prepare Windows images, including the Windows Recovery Environment, Windows Setup, and Windows PE.
Try restarting your computer after both tests and check if the "Couldn't load plugin" error is fixed. If you could not perform the SFC scan the first time, then try to run it again right after you completed the DISM scan.
The "Couldn't load plugin" error may limit your web browsing experience by not being able to see some content while browsing. We hope that one of our provided solutions in this article helped you to fix this error, and now you can browse the web with your Google Chrome browser without any problems.
Anyway when trying to run my storyline files in chrome on our network I am getting the "can't load plugin" message. It doesn't seem to happen on other networks some of our users use but is happening on my network.
I fixed the same problem just now, 'could not load plugin' in Chrome. This seems to be a Flash plugin error as it also presents itself when loading flash into Chrome from elsewhere on this one machine. Turning off Chrome extensions did not solve the problem. To get around the problem, this is what I did: In Storyline 360 I made sure that the Publish settings are set to 'HTML5 / Flash' instead of 'Flash / HTML5'. This bypassed the broken flash problem altogether by loading the Storyline content in HTML 5. I have other Windows 10 machines with Chrome here but the problem just occurred with this one machine, not sure why. I hope this gets round the problem for you! :-)
The past few days I have been having the problem with the fitbit foods page telling me it can't load Shockwave Flash. Typing "chrome://plugins" into the address line of chrome no longer produces results. In the graph box at the top right of the fitbit foods page, it will say "right click to load Adobe Flash Player", but right-clicking doesn't do anything. Why doesn't fitbit do something about this problem which has literally plagued some users for years?!! So annoying!
First and foremost, please let me know if creating a new question would be 'better' than updating this question. Anyway...I am currently running Antergos and I am experiencing the same problems. Hal doesn't seem to work and o tried installing an older version to no avail. I am interested in trying to get my 'hands' on a ChromeOS recovery so I can extract its flash player.
I upgraded to Linux Mint 17 a couple weeks ago. Prior to that, I was running on LM 16 and had an issue playing protected content on Google Chrome. I fixed that issue after installing hal and disabling Chrome's flash player in favour of Adobe's. But since I'm on LM 17, that problem reared its ugly head again. I recently installed hal and since Chrome no longer gave me the option to disable/enable specific flash plug-ins, I renamed Adobe's to libpepflashplayer and moved it to opt/google/chrome/PepperFlash. Unfortunately, the problem still persists and it's worse now since I know get the notice "Could not load Shockwave Flash."
In addition to the answers Karol S gave, note that the PPAPI flash found on ChromeBooks has DRM enabled. You can extract the libpepflashplayer.so.* files from a recovery image and substitute them for your existing ones.
To quote the author of the PPAPI-> NPAPI wrapper 'fresh player' (an alternative to pipelight that doesn't work quite as well in my experience but is farless complex to install), this is how you get the plugin library:
If you are downloading samples from developer.chrome.com its possible that your actual folder is contained in a folder with the same name and this is creating a problem. For example your extracted sample extension named tabCapture will lool like this:
The issue you are facing is as follows: Since you received a new silent upgrade in the background that jumpedyour browser version from say 20 to 21 or so, you are no longer able to use Flash properly. You receive yellowprompts at the top of web pages asking you whether you want to run Flash this one time or always. And no matterwhat you click, the Flash plugin cannot be loaded. You start fiddling with settings, options, allowing anddisallowing plugins, but this does not make a difference, either. Let's fix it.
What you need to do, under chrome://plugins is to expand details and then disable the internal plugin. As itturns out, Google Chrome can use two different versions of Flash, its own version, which comes bundled with thebrowser, and the native system plugin, which you have probably installed on your own.
I opened the Spotify Web Player but I couldn't access the web player due to 'Flash player needed'. I checked with my Chromebook and the latest Adobe Flash Player is install but somehow I still couldn't access the Spotify Web Player. Please help me. I'm currently using the latest Chrome web browser.
I have the exact same problem! I have been able to use it fine until 3 days ago and before, if the message popped up then I could refresh the page. I deleted the extension and re-downloaded it and I'm still having the same problem. My chrome book is brand new and definately has the latest adobe flash player. I am very frustrated because Spotify is my only music source.
I am having the same problem with my brand new chromebook as well. I load the pag and then the Flash Player requirement pops up and no matter what I do it doesn't go away. Spotify is my only source for music so right now I have none. Someone please help me!
Plugins are usually great and they can add new performance options to your browser such as an ad blocker, automatic translation or spelling check, video downloaders, etc. Users still need to be careful not to overuse them because a lot of plugins can slow down your browser significantly.
aa06259810