Current version loads Flash from the system location as long as the version is the same as or greater than the embedded version. Google changed this in early Chrome 50 versions. Older versions of Chrome do not load Flash from the system location.System location and system plugin is what we refer to as the non-embedded version and install location. The Flash Player path's I posted are the before, when Chrome was loading the embedded version from the user location, and the after, when Chrome was locating the content debugger from the system location. I installed the Pepper debugger (to confirm Google hadn't changed the behaviour again) on Windows 10 before replying. Ok but about Chrome for win 10 the problem is the pepperflash installer it says that pepperflash cannot be installedīecause it's managed by the browsers itself. Opera doesn't have a builtin Flash plugin, it uses the user installed Flash Player (release or debugger) To check where Chrome is loading Flash from, launch Chrome and navigate to chrome://flash, look for the Flash Plugin version and path While Gogole embeds Flash Player in Chrome, if the manually installed Flash Player version is equal to, or greater than, the embedded version, Chrome will load the user installed version.įor example, the embedded version is saved at C:\Users\labuser\AppData\Local\Google\Chrome\User Data\PepperFlash\28.0.0.161\pepflashplayer.dll and Chrome loads Flash from this locationĪfter installing the content debugger (of the same version), Chrome loads Flash from C:\WINDOWS\system32\Macromed\Flash\pepflashplayer64_28_0_0_161.dll Yandex isn't officially supported, as such, can't say how it handles the content debugger For Edge: At this time Microsoft does not offer the ActiveX Control content debugger for IE/Edge on Windows 10.įor Chrome/Opera, the content debuggers are available at Adobe Flash Player - Debug Downloads