Until November we were using a production console EXE compiled with the 2020 version of exeoutput, with no problems (in use on Windows 7, 10, 11).
When recent Windows updates broke that version, we noticed on your site that the 2024 version should be used for Windows 11 compatibility, tested 2024.1 and got the error message “Could not load PHP DLL in memory”, saw that this was a known issue with these new Windows updates, and waited for you to release 2024.2 as a fix for the issue.
When 2024.2 came out, we started a general production release with a 2024.2 generated EXE (except for Windows 7 PCs: due to the loss of the required VC++ for Windows 7 in the 2024-generated EXE, we’re now maintaining a parallel production EXE generated with the 2020 compiler).
2024.2 makes a console EXE that works on many PCs where 2024.1 did not.
However, when doing a general update, our 2024.2-built EXE sometimes results in the same type of error message. One PC makes a good example:
Microsoft Windows 10 Pro
10.0.19045 N/A Build 19045
Result:
Exception(2024.2.0): Could not load PHP DLL in memory
On this PC, our previous production EXE (made with the 2020 compiler) works. However, an EXE compiled with 2024.1 does not (!) in the same way.
Since this is an issue with both 2024.x versions (not a new problem introduced in 2024.2) I’m not putting this in the thread for the 2024.2 release, and since this example is on Windows 10 I’m not putting this in the thread for the 2024.1 Windows 11 update incompatibility. So I’m making this as a new thread.
Are there any known issues that would cause this error message (besides what was fixed in 2024.2) on 2024.x that would not have affected 2020?
9 posts - 2 participants