The VideoLAN Forums

I had VLC 64bit v2.2.1 installed on Win7 and Secunia flagged it as NOT secure,indicating I should upgrade to v2.2.2

I prefer to not have Secunia apply the update, so I opened VLC, confirmed that I was running v2.2.1, and selected Help/Check for Updates. I was told "You have the latest version of VLC Media Player". After clicking "Recheck version", I got the same response.

However, after going to the download page for Windows VideoLAN - Download official VLC media player for Windows and clicking the drop-down arrow alongside the "Download VLC" button, then "Installer for 64bit version", I was taken to VideoLAN - Downloads where I got what I needed.

Why isn't VLC detecting its own updates?

(Secunia Advisory SA68087)
CVE Reference(s):
CVE-2015-7981
CVE-2015-8126
Vulnerability:
Where: From remote
Impact: Cross Site Scripting, Exposure of sensitive information, System access

Also, it would make more sense if the Previews here showed the URLs as they will appear when submitted, as in the Full Editor and Preview, but I suppose that's a flaw in the software on which this forum is running.

I'm having the same issue with the 32 bit version (also v2.2.1).

A quick bit of googling revealed that multiple (at least 2, but I stopped looking) bug reports on the trac website have been closed by jb with the rather surprising answer that this is NORMAL behaviour. I can't get my head around why the "check for updates" feature exists if this behaviour is considered normal for it...

LOL, sorta.

The word you want to wrap your head around is staging.

I also see the same problem in the 32bit.

A possibly related issue, is when I go to the web site to download the 2.2.2 version manually it saves it as the file name "vlc-2_2_2-win32_exe" instead of "vlc-2_2_2-win32.exe". Works fine after a renaming, but maybe the in program Check for Update... feature can't find the latest .exe at the source because it is named incorrectly? Something for VideoLAN to fix?