The VideoLAN Forums

How do you download this update? Everytime I try to do it, it fails saying "Failed to open "C:\blah blah blah" for writing". What does this mean and how do I fix it?

Do it by hand using the .exe on our website.

First : thanks and congratulations for VLC dev. team, I am very glad to use the product.
I usually installed new versions as soon as available ... but for the newest 1.0.1 (XP SP3 & Vista, I 'll try with Ubuntu), I experienced the same problem as Amethyst


I did as you said : download "by hand" ; but after 1.0.0 uninstall
... the "error writing " occurs when installing 1.0.1

Result : VLC was totally removed from my computer, I 'll re-install 1.0.0 hope install works

Thanks for any explanation or solution

Daniel Arzur [retired old IT]
---------------------------------------------

During VLC upgrades, all web browsers and VLC processes (even zombies) must be halted, otherwise you are prone to overwrite file errors. Depending on your system and account privileges, you will be requested a privilege elevation used to access either program files of the registry.

"By hand" sands for using http://www.videolan.org/vlc/ to upgrade from 1.0.0 I think.
You can retry 1.0.1 install ensuring %PROGRAMFILES%/VideoLAN/VLC is clean after 1.0.0 uninstall.

Thanks Thannoy and all !

Closing Firefox allows sucessfull install of 1.0.1 ... that is obvious but I forgot.
A little warning in install menus could be usefull for crazy users.

Daniel
----------------------------------------------------------------------------------------------------

Hello all.

Same thing happens to me. Cannot possibly update here, even with Firefox closed. Had to workaround downloading the update via Firefox in order to successfully update without the error message displaying. It is as though my hard drive is write protected to VLC! Strange, isn't it?

It would be nice to know how this issue arose, whatever the conflict is (assuming it does not happen on every system).

same problem here.
Windows 7 Ultimate x64

We are working on a vastly improved update checker for the next major release (aka VLC 1.1), which will address these issues on Windows. Additionally, we will use a completely different framework on Mac OS X, which isn't win32 compatible.

Nice! So this bug will probably be fixed.

N.B.: for your information, the bug seems to be absent from v0.9.9, but present in v1.0.0.