A plugin check is showing Shockwave Flash as v16.0.0.287 but updating it to the current 16.0.0.305 and restarting Firefox (v36.0) does not change the situation.
A plugin check is showing Shockwave Flash as v16.0.0.287 but updating it to the current 16.0.0.305 and restarting Firefox (v36.0) does not change the version number or status when rechecking plugins. Adobe's check site and the Flash control panel confirms 16.0.0.305 is installed. Any solutions to this?
தீர்வு தேர்ந்தெடுக்கப்பட்டது
I noticed in the information included in the about:plugins page under Shockwave Flash, the Path: line was showing-
<Path: C:\WINDOWS\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_287.dll,C:\WINDOWS\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_305.dll>
The .dll file for outdated version 287 was still there and listed first before the current version 305. I deleted the version 287 .dll and on restarting Firefox and checking the plug-ins again the problem appears to have been solved. Regards - Spindrift
Read this answer in context 👍 4All Replies (3)
Spindrift, For further investigation is this on the plugin check page? For reference:
If so, please clear the cache and cookies to request a fresh page to detect changes. If the version in about:plugins is up to date Firefox has recognized it.
If Firefox does not recognize the update, remove the plugin from the about:extensions page and restart the browser. (A reinstall of Flash may also be necessary)
Thanks for your comeback... Although I can get the about:plugins page up, when I try about:extensions I get the 'The address isn't valid' page so I can't remove the plugin. Any thoughts? Spindrift
தீர்வு தேர்ந்தெடுக்கப்பட்டது
I noticed in the information included in the about:plugins page under Shockwave Flash, the Path: line was showing-
<Path: C:\WINDOWS\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_287.dll,C:\WINDOWS\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_305.dll>
The .dll file for outdated version 287 was still there and listed first before the current version 305. I deleted the version 287 .dll and on restarting Firefox and checking the plug-ins again the problem appears to have been solved. Regards - Spindrift