This page addresses archive extraction issues. If you have gone through the extraction and have a problem restoring your site (e.g. an error about sessions, database restoration problems, site setup issues etc) you are on the wrong page. In that case, please take a look at the ABI issues page.
Please indicate what kind of problem you have with Kickstart so that we can further assist you:
It won't run at all. For example, blank page, 500 Internal Server Error or a PHP fatal error (e.g. a T_OBJECT error)
It runs but I can see PHP errors (Warning, Notice, Strict, Deprecated, etc but NOT fatal errors)
It runs but I can't see any archive files listed in the archive selection drop-down
It won't extract the archive. For example INVALID_HEADER error, "Invalid archive type", "Could not open file README.html for writing" and other similar errors.
If you have a question not mentioned above, they are issues with Akeeba Backup Installer (ABI), not Kickstart.
First make sure that your hosting environment complies with the minimum requirements for Kickstart. You need PHP 5.3.3 or later. If your host is using one of the earlier versions please use Akeeba eXtract Wizard to extract the archive locally and upload your files, as per the instructions in our Quick Start Guide. Do note that in this case Joomla! and/or some of its extensions may not run at all.
If the extraction process does not start, i.e. you click on the button and nothing happens, please go through the client-side troubleshooting steps before doing anything else. Most likely it's an issue with your PC configuration or ISP. We won't be able to help you if you don't go through these steps!
If nothing of the above works, you may want to try downloading the latest version of Kickstart, extract the ZIP file locally and re-upload kickstart.php to your site.
If you are using Panic's Transmit 4.1.4 on your Mac, be advised that the "Mount as disk" option is buggy. If you mount your site's FTP server as disk, uploading Kickstart will result to an incomplete (corrupt) upload on most servers. Use Transmit's interface instead. This bug was fixed in Transmit 4.1.5.