ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

"Vulnerable" plugins are already updated. Firefox won't recognize the updates!

  • 21 ردًا
  • 3 have this problem
  • 33 views
  • آخر ردّ كتبه complainer

more options

I updated my VLC plugin to 2.1.3, the most up-to-date version of both the plugin and the software. Yet, Firefox says it's "vulnerable" for absolutely no reason. I also shut down and restarted firefox after the update, and it didn't make a whiff of difference.

Also, Adobe Reader 9.5.5 is the most up to date version of Reader 9, and is perfectly fine according to my add-on manager, but yet that's also "vulnerable" according to the plugin update checkfor absolutely NO reason. When I upgraded to Adobe Reader X a long time ago it didn't work at all with firefox as the plugin had severe issues and wasn't user friendly even outside of firefox. I therefore reinstalled 9 and never went back.

Why is it that Firefox cannot recognize updated plugins and says they're vulnerable, and yet gives zero reason why?

Lastly, if I go into the add-on manager and click on the "update now" link in that page it only brings me to the worthless page telling me the plugin was blocked, not about where to go to update it. This is a really irritating problem as you go to try to update it and you're not going to a website that will allow you to do it, it just brings you to a page that says absolutely NOTHING of value.

الحل المُختار

If you want to replace the VideoLAN\VLC\ program files that weren't updated with the win32 installer, such as npvlc.dll (and others?):

You can get the Zip Package vlc-2.1.3-win32.zip linked here, and extract the contents: https://www.videolan.org/vlc/download-windows.html

If you don't want to do that I would consider a complete uninstall of VLC media player 2.1.3 then a resinstall.

Read this answer in context 👍 0

All Replies (1)

more options

your welcome, anytime; and thanks for your help. I did the move to the desktop of the original file because if the fix didn't work, I could always move the original file back. Then I had to rename it when the extraction didn't play nice. But it was a protection in case anything screwed up, and doing those two little steps were tiny compared to the irritation I would have suffered if something screwed up and I didn't do it.

  1. 1
  2. 2