Support

It's been a year or so since I last used MAMP on Windows but I don't think it's changed much (or at all). MAMP had a known bad configuration. It includes the Thread Safe version of PHP which is the wrong version to use with FastCGI (what it uses for multiple PHP versions). Because of that misconfiguration the PHP on the server will die randomly, especially when there are slightly more requests coming in e.g. when backing up and restoring a site or when you are using a post based on a complex Gutenberg template in WordPress. The simplest solution is to set MAMP to use a single PHP version throughout the entire server.

Alternatively, we can make the restoration be slow.

On Kickstart's initial page, before you click on the Start button, set "Minimum execution time" to 7 and "Maximum execution time" to 3. This is not a typo, the max is less than min. This tells Kickstart to slow down and wait. Extracting will take twice as long.

Later, inside ANGIE's Database Restoration page under Fine Tuning please set Maximum Execution Time to 3 and Throttle Time (msec) to 4000. This tells the database restoration to work for 3 seconds then do nothing for 4 seconds. Restoring the database will take about twice as long.

These delays we added make sure that the web server has enough time to replace the PHP instances it uses to serve requests instead of reusing the same one. The prevents internal PHP memory corruption which causes PHP to die unceremoniously, what you perceive as Kickstart "stopping".

That would be my suggestion, use different *AMP packages until you find one that's actually packaged correctly.

My solution was to ultimately make my own multi-PHP AMP installation on Windows but it's a bit involved. If you're curious, that's how I did it.