Support

Kickstart is relaying the message from PHP, which is relaying the message from the Operating System (Windows). Check if you have enough free disk space and/or any permissions issues.

If that's not the case, I am observing that the full filesystem path to the file is rather long, 117 characters. I am wondering if you're somehow hitting the Win32 path limit (https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry) even though you're shy of 260 bytes even if I consider Unicode. The page I linked has a Windows Registry workaround to enable long paths, i.e. setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled to 1.

If none of that helps, you can always check the “Ignore most errors” option in Kickstart to tell it to skip over these files it cannot write. Since this is a temporary file it should be safe to do so.

Hello,

most likely the whole path is longer than the length allowed by Windows itself.

Please check the option "Ignore most errors" in the first page of Kickstart, that should do the trick.

Ultimately, your problem is XAMPP itself. You can extract the ZIP file with 7-Zip as a temporary solution.

They are using the non-threaded PHP SAPI as an Apache module. However, Apache needs all its modules to support threading since the default Apache MPM is multi-threaded. The discrepancy causes thread concurrency issues which manifest themselves in different ways including the inability to open files for reading or writing. The problems only happen when there are a lot of requests in a short amount of time which typically only happens if you have some kind of automation running, e.g. taking / restoring a backup, indexing article text, test sending a newsletter using a local mail server (e.g. MailCatcher or similar), and so on.

I have explained those finer points in my blog back in 2018, see Improve PHP performance on Windows. It's driving me nuts that XAMPP has not caught and fixed this problem in nearly twenty years. Argh! Every couple of months we have a client who, like you, has hit that brick wall.

For this reason I always recommend WAMPServer to our Windows users or, better yet, set up their (see IIS development server for PHP on Windows 10 for example if you want to use IIS; I have an older tutorial for Apache which is mostly okay, see Apache, MySQL, PHP server on Windows with multiple, simultaneous PHP versions).

Can you try selecting a different PHP version in WAMPserver? I am wondering if they messed something up with their PHP 8.2 build…