Magento 2.4.7 on Windows 2022 Server running XAMPP - using OpenSearch 2.12.0 - Install fails at 458

[5dec59fa0bf50]

Installing Magento 2.4.7 OpenSource community edition on a new Windows 2022 Server running XAMPP, I have had several issues and have been able to research and move past them.  The last issue I had failed at this same point giving an error notification of the Gd2.php at line 70, I found the code snippet to replace for the private function validateURLScheme that added local C to the allowed_schemes and then another modification also made it pass where adding an extra condition to the if statement (&& !file_exists($filename)) but seem to resolve the issue at line 70. Now my new problem is at line 111 of Gd2.php given that the lines are a little off I'm not sure if they are talking about the protected function _isMemoryLimitReached() or the protected function _getImageNeedMemorySize(file)?  When working with the error on line 70 the actual line was not 70 but 22 lines after that around line 92.  This leads me to believe that even though it says line 111 its probably further down like the other one even line 125.  Has anyone else has an error on line 111 of the Gd2.php?

[ziddihoon23b54]

For your Magento 2.4.7 installation issue on Windows 2022 Server with XAMPP and OpenSearch 2.12.0 failing at line 111 of Gd2.php, the error likely stems from the _isMemoryLimitReached() or _getImageNeedMemorySize() functions, possibly due to PHP memory constraints or file handling quirks on Windows. Since you’ve already adjusted validateURLScheme() and added && !file_exists($filename) to bypass the earlier Gd2.php error, the new issue at "line 111" (potentially line 125+ due to offset) suggests a memory limit check failing. Increase your PHP memory_limit in php.ini to at least 2G (e.g., memory_limit = 2048M), restart XAMPP tool, and ensure the GD extension is enabled (extension=gd). If the error persists, add a debug line before line 111, like var_dump(memory_get_usage(), $this->_getImageNeedMemorySize($file));, to pinpoint the memory issue, then adjust server settings or optimize image processing accordingly. This should resolve the install hang at 458.

[5dec59fa0bf50]

I used the system requirements per Magento 2.4.7 and set the Memory Limit to 4G and Max Execution Time to 18000 in the php.ini file that belongs to the current php version. I also had the idea that maybe it didn't like the format so I tried changing it to M and not G by multiple by 1024 so I even tried setting it to 4096M instead of 4G.  I have seen in earlier installs of Magento 2.3.3 that .htaccess is added to the pub folder (magento2/pub/.htaccess) and in it they have set the memory limit and max execution size amongst many other things. Logged in as the Administrator using the command line with Admin privileges I call the php info () function and it tells me that my Memory Limit and Max execution time are set correctly. But, I was thinking that maybe since the php.ini file is behind the Magento public folder then it cannot see it, that is the only thing that I can think of in response to your help. Do I need to do anything to make Apache take the .htaccess settings or is it an automatic override.  Thank you for taking to the time out of your day to reply back to my question and thank you for helping me! 

############################################

.htaccess 
## Adjust memory limit

php_value memory_limit 756M
php_value max_execution_time 18000

#########################################