Support

This is actually a bug in WAMP (and XAMPP) on Windows. They are using the wrong thread safety binary. I've explained all that in https://www.dionysopoulos.me/improve-php-performance-on-windows.html under "PHP versions, bits and thread safety".

You can try to change the timing parameters in Kickstart. They are at the bottom of the page, under fine tuning. Set the minimum execution time to 7 and the maximum execution time to 3. If this solution doesn't work any more let me know. I can try to sacrifice my tertiary Windows setup to WAMP's wonky server implementation to try and come up with a better solution.

In any case, if you can use the CLI to extract the archive you can keep doing that. Just rename .htaccess to htaccess.bak and access the /installation folder through a web browser. The restoration will work just fine and it will let you remove the installation folder (and rename htaccess.bak back to .htaccess) at the end of the restoration as long as you have set the correct permissions on the extracted files and folders. IIRC WAMP runs everything under your own user account and doesn't need permission changes but I might be mistaken. It's been 3 years since I last used WAMP or XAMPP on Windows.

This is really weird. I've tried reproducing that with XAMPP on two physical Windows machines and even on Windows 10 Sandbox (which is slow as molasses, especially on my slowest, 7-year-old, physical Windows machine) to no avail.

Is it possible that you are using an antivirus which might be falsely detecting Kickstart, your backup archive or the extracted files as malicious? Even Windows Defender (or whatever it's called this month) could do that. My advice is disabling virus scanning for the web root of your local server. It won't just prevent false positives from screwing up your sites, it will also make your local sites respond drastically faster. I've made that point in the blog post I linked you to in my previous reply.