What alewis7428 posted above is true.

• Updating from VLC 2.0.7, Plugin version in Program Files version 2.0.6, Mozilla Plugins in Window registry VLC plugin version 2.0.7
• results in VLC VLC 2.0.8, Plugin version in Program Files version 2.0.6, Mozilla Plugins in Window registry VLC plugin version 2.0.8

This could be a problem with VLC installation writing an incorrect registry key (version) for the Mozilla plugin.

Here is discussion and answer on VLC forum for an earlier situation explaining (by the site admin) that the plugin version does not necessarily change with each new VLC version - http://forum.videolan.org/viewtopic.php?f=14&t=103363 .

Another post on the VLC forum for VLC 2.0.7 and plugin version 2.0.6, has a reply by a user pointing to this current Mozilla Firefox thread - https://forum.videolan.org/viewtopic.php?f=14&t=112036

• In the above VLC forum thread, the site admin confirms that VLC 2.0.7 used plugin version 2.0.6 (in the second item in the thread)

Sounds like Mozilla developers and VLC developers need to be talking to each other.

"Known issue" according to VLC forum: https://forum.videolan.org/viewtopic.php?f=14&t=113048&p=383039#p383039

I am cancelling the bug report and thanks to all for responses.

Yes, thanks to everyone. Looks like we will have to wait on the VLC people to correct this problem.

Thanks again! :-)

I also have this problem (even after restarting the computer).

This problem is discussed on VLC forum and IS NOT UNIQUE to VLC.

Please read the whole thread: https://forum.videolan.org/viewtopic.php?f=14&t=113077

My post there: https://forum.videolan.org/viewtopic.php?f=14&t=113077&p=383761#p383761

Hi affinity, thank you for the links.

The Adobe PDF plugin issue is caused by there being simultaneously 3 "current" versions, but the design of the Plugin Check site (last time I checked) was that it only could handle 1 "current" version. Therefore, for example, Windows users with the latest in the Adobe Reader/Adobe Acrobat X series (10.1.7) are always told they do not have the current version.

With VLC, I'm not sure how the Plugin Check site is getting the information the current version is 2.0.8 and not 2.0.6. Someone who works that site probably should change the version number until VLC issues an update. Failing that, users will have to trust VLC that it is as up-to-date as possible.

Okay, thanks jscher2000, but that just outlines the fact the the current plugin checker is inadequate. It isn't good enough for VLC, it isn't good enough for Adobe..... the plugin checker needs to be made accurate, reliable and trustworthy; if it is not those three things, then Firefox users will always have problems just knowing that their plugins are up to date and may even avoid using plugin checker altogether -- and that is only the ones that know about the checker in the first place, it wouldn't surprise me if 99% of ordinary users didn't even know about the plugin checker.

So, my view is that the plugin checker needs to be fixed and then it needs to autorun when possible, before each session is started as a user security protection process, that is as part of /normal/ startup of the browser. Oh and if the session has been active for quite a period of time, then silently run the checks (as an auto update process) at some interval; then, if the results vary, alert the user.

Is there any way for the plugin checker to check the actual executable file properties instead? VLC's properties shows the latest version under "Description". Just wondering.

Hi FoxyDerFox, well.... that image only shows the version "according" to the shortcut link.

It's a tough situation. What do you go by? The shortcut link, the main executable (the shortcut's target), any one (or a particular) DLL, the registry? Yes, it is tough. Any of those can be /adjusted/ by malware just for starters.

Just assuming that the version details are not tampered with in any way, the plugin checker needs to accurately determine the version and risk to the user; anything less and we have this problem.

Hi FoxyDerFox, Firefox only checks the version of the plugin DLL, not the main program. Based on what I read earlier in this thread, the 2.0.6 plugin worked fine, so the version number wasn't incremented when versions 2.0.7 and 2.0.8 of the program were released. However, the plugin check site is looking for the program version numbers. Unless something new has been released. plugin 2.0.6 is current. Hopefully this mismatch will be updated soon.

It doesn't matter if you use the Properties information from shortcut link or open the folder containing the executable and use the Properties information again. You get the same version information as shown in the image which means the shortcut link properties is using the information from the executable file. So, maybe instead of using the Registry info except for plugin being used in Fx, the correct file can be used to extract the version number.

I don't really have a problem with most reported versions, but it has been the same two for a long time that have been shown out of date when they are not. If the installed program has a way to set auto-updating, then that's what I do. Even Software Informer SoftwareInformer seems to have a problem with installed (correct) versions vs. reported (outdated) versions.

The VLC plugin included in VLC 2.1-rc2 is finally 2.1.0.0

There !! i think that answers everyone's questions on this topic .. The npvlc.dll file version is indeed 2.0.6 (as you can check on the file properties itself) but the VLC version is 2.0.8 ...

QUOTE

Re: Web Plugin 2.0.8 Not Installing Firefox

Postby Jean-Baptiste Kempf » Sun Aug 18, 2013 12:37 pm

   Voynich wrote:Or do you mean the checkmethod of Mozilla is not correct and if they check the version no warning would appear?

Yes.

The plugin is unchanged between 2.0.6 and 2.0.8. The security issues are on the libraries. Mozilla, should have contacted us, before doing things without checking... Jean-Baptiste Kempf http://www.jbkempf.com/ - http://www.jbkempf.com/blog/category/Videolan VLC media player developer, VideoLAN President and Sites administrator UNQUOTE FROM VLC FORUM https://forum.videolan.org/viewtopic.php?f=14&t=113077

I guess we just have to wait for the next version to come around before this gets fixed - meanwhile I believe it is safe to continue using VLC plugin as usual.

Writing on Dec 2013. Thread says last reply was 3 mos ago? Means issue solved? I don't think so! Have just updated VLC to 2.1.2 Rincewind, but see that my Firefox 26.0 (most recent) says in Tools Addons that my Plug in for VLC is at VLC 2.0.2.0 and is blocked. Does anybody have a nice clear process or set of steps to get the bad (old) VLC plugin off the PC and end up with the updated VLC Plugin? Mozilla blogs say it's a Windows issue, VLC says its a Firefox issue. Above, somebody says it's VLC not having an update for the Firefox plugin when you upgrade the VLC 2.1.2. Everyone's pointing at everyone else. Any techies here? My laptop, BTW with the same upgrades had the latest VLC, but the Firefox plugin there is at VLC 2.1.0.0. So that didn't update with the latest VLC d/l. Perhaps VLC is at error?

Did you install the 64 bit or 32 bit version of VLC? If you installed the 64 bit version, try installing the "normal" 32 bit version, because I assume you are using a 32 bit Firefox (there are only very few users of the 64 bit Nightly version). This should install the VLC plugin 2.1.0.0. You can still use the 64 bit VLC and have both versions installed but I think only the 32 bit version installs the correct plugin for Firefox.

Thank YOU! R1Pieces has it! Yes, had d/led the VLC 2.1.2 Rincewind 64-bit,and it didnt update the Firefox plugin. D/ling the 32-bit version (also 2.1.2) and installing it, did update the Firefox VLC plugin to 2.1.0.0.. This is the correct answer...got it fixed!

You can selectively delete any plugin you want using iobit uninstaller ver 3 and select the plugin tab.