I am pretty sure that was the problem.
Let's say you run a restoration, but for whatever reason do not delete the installation directory. This leaves behind the session file in installation/tmp which says "I have reached the end of the restoration script". Any further attempt to access /installation will result in its installation/index.php reading that session and take you to the final page of the restoration script. This is a deliberate failsafe. If you close the tab where the restoration script is, opening a new tab and visiting /installation lets you pick up where you left off. If you've finished the restoration, the last page either shows you instructions to delete the installation directory, or how to create a new configuration.php (if it could not be written to directly).
However, leaving behind an installation directory is not normal. If that's the case, next time you extract a backup archive, the session file in the installation/tmp directory is not overwritten. By default, Kickstart only writes new and replaces existing files with what's in the archive, it does not delete what is not in the archive. When you click Run The Installer it just opens a new browser tab to visit /installation. Because of the leftover session file – which is keyed to your browser and IP address – the restoration script now reads that it is at the end of the restoration and shows you the final page.
Makes sense?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!