The 'Couldn't Load Plugin' Google Chrome Error is an error associated with the Chrome browser's failure with loading a plugin. Unlike extensions, which usually are no more than source code, plugins are executable files, but philosophically, both serve similar purposes of expanding a browser's capabilities. Users encountering this error repeatedly, which often ties into Flash closely, have several remedies that require no exceptional or complicated steps.
Ordinarily, experts recommend installing the latest versions or patches as a fundamental good maintenance habit for software. In this case, however, the newest version of Chrome no longer supports plugins. Users should check for alternatives, such as extensions, which fulfill the same purpose, since using an out-of-date version of the Chrome browser is a security risk.
A first step that users might consider is checking the Task Manager. However, they should use the Chrome-specific variant of the application instead of the more-general Windows one. The Shift + Escape keyboard combination opens it, and there also is a menu selection for it under Chrome's 'More tools' section. The new window shows all Chrome tasks, including extensions, open tabs, etc. While there, look for unusual processes. Due to its high correlation with plugin errors, experts suggest that users close the Flash process by finding 'Plugin: Shockwave Flash' and clicking the 'End task' button.
Users also should check Chrome's content-specific settings for whether or not Flash is permitted. Enter 'chrome://settings/content' into the address bar and press enter. Alternately, navigate through Chrome's Settings: choose Privacy and Security, Site Settings and scroll down to the Content section. Versions of the browser with Flash support will display a Flash section here, which users can set to 'ask first' or 'block.' Set to 'ask first' toggle to blue by clicking it. Versions of Chrome without Flash support will not show this entry, although the Content section is otherwise very similar to previous releases.
Users who have a Chrome version that still supports Pepper Flash Player – Chrome's custom version of the application – might encounter file corruption issues with it. They can rename components or delete the files completely for refreshing. For renaming, navigate to Chrome's primary program folder (usually, in 'Program Files' with or without 'x86') inside the Google directory. Double-click through Application and the version number of your Chrome installation. If Chrome supports Flash, there will be a PepperFlash folder here. Double-click it and rename the 'pepflashplayer.dll' file to another name that triggers Chrome's re-acquiring it (such as 'renamedpepflashplayer.dll').
A similar, more comprehensive solution requires finding the Windows user's local appdata folder (such as by inputting '%localappdata%' in the taskbar). Double-click the following folders: Google, Chrome and User Data. Again, a PepperFlash folder will exist if the current Chrome installation supports it. Delete the entire PepperFlash folder (as with the DLL earlier, Chrome should re-acquire it automatically).
More general-purpose file-repairing options (see the System File Checker) also exist but aren't necessary for most cases. Although Flash's depreciation is for reasons of universal security, users who know what they're doing don't need to stay accountable to it. Tweaking Chrome for running old plugins can be worth it for those who understand the drawbacks and limits.