Silent update doesn't update NPAPI pluggin

[Guest]

Hi,

We have a corporate environment with only a couple of Win7 Prof computers. Because Flash wasn't updated on a regular basis I decided to flip the switch and use

SilentAutoUpdateEnable=1

AutoUpdateDisable=0

in the mms.cfg file on those computers so that critical updates are automatically installed. This seems to work as the Active X pluggin was silently updated not long after the setting was applied. However, the NPAPI pluggin doesn't get updated and stays at the old version. We use both IE and Firefox browsers so both the pluggins need to be updated.

Does anyone have any idea why the NPAPI doesn't get auto silently updated? I noticed there's no scheduled update task for Flash in the task scheduler but I assumed that shouldn't be a problem since the Active X pluggin did get updated without any interaction from my side (other than enabling the previously mentionted settings).

[ridhij42083560]

Hi,

Which version of NPAPI Flash Player is installed in your machine? Could you add SilentAutoUpdateVerboseLogging=1 in mms.cfg file and try triggering the update service on your own. For the same, if you are using 64 bit win 7 go to C:\Windows\SysWOW64\Macromed\Flash and run the FlashPlayerUpdateService present in the folder as administrator. If the machine is 32-bit you will find the update service at location C:\Windows\System32\Macromed\Flash.

Before running the update service delete the FlashInstall.log file present at the same location as update service. Once you have run the update service, share the FlashInstall.log generated. To share the file you can go through How to share a document. Once you have uploaded the log file please share the link to the log file here.

Thanks!

[Guest]

@ridhijain

Thank you for your extensive reply. I left the computer on and logged in to give it some time and I just checked now, the NPAPI pluggin is also updated now without any interaction from me needed. So I guess problem solved

[_maria_]

Hi firstl86740110

Silent AutoUpdate updates Flash Player ActiveX first and then when it runs again (about an hour later) it'll update the NPAPI plugin.  It's possible you checked prior to the one hour time-frame had lapsed.  If you see it take more than one hour to update the NPAPI plugin after the ActiveX Control has been updated there may be an issue with the system and we could investigate further with verbose logging enabled to capture the Silent AutoUpdate activity.

--

Maria