Factorio Forums

I last played factorio at version 0.11.8, and when I started it today, it was updating to the latest version.
The download went fine.
Then, it came to the point where the program says "restarting factorio"

Windows 7 popped a window over that, asking permission to run factorio.
Next, factorio closes.
Next, I get an error message saying failed to write to d:\factorio\bin\x64\factorio.exe : no permission.
(which if I understand correctly, would be because it tries to write a new updated factorio.exe before the old process is closed and the old exe deleted)

The result is: I end up with a broken install (it has no executable), which I can't run.

I tried redownloading and reinstalling.
Same thing happened when updating from 0.10.12.

I never had a problem with the updater like this before.
So somewhere in between 0.11.8 and the current version, the updater broke for me to a point where I cannot play the game

help?

Sorry for that, but a reinstall should really work. Perhaps you need to delete the installed version by hand?
And as long as it doesn't work, you can use also the zipped version.

You don't need to install 0.10.12 then update, just install 0.11.19

You can get it from http://www.factorio.com/download/experimental

Sometimes I'm with stupid. Of course, that question comes from not knowing how to download current version.
See also
https://forums.factorio.com/wiki/inde ... stallation

Thanks guys!

Just for thouroughness sake, I tried the remove manually and reinstall thing, deleted the game directory entirely, and reinstalled 10.12
Sadly, updating that still did the same thing. Windows throws an write permission denied error because the game process is trying to replace itself with a new exe before it's terminated, and I guess Windows does not allow alteration of an active process. The game process still happily deletes the exe once it's done though, leaving me with an install without factorio.exe.

Luckily, the direct 11.19 install worked flawlessly

Sorry for the problems. You probably don't have the log file from the failed update around, do you?