“The procedure entry point SSL_get0_group_name could not be located” means Windows loaded an OpenSSL DLL that does not export the symbol expected by Apache or PHP. Finding a DLL with the correct filename is not enough; its build must match the component loading it.
Last updated: November 4, 2026.
where.exe php.exe
where.exe libssl-3-x64.dll
where.exe libcrypto-3-x64.dll
C:\xampp\php\php.exe -i | findstr /I "Architecture Thread Safety OpenSSL"
C:\xampp\apache\bin\httpd.exe -V
Get-ChildItem C:\xampp -Recurse -Filter "libssl*.dll"
Get-ChildItem C:\xampp -Recurse -Filter "libcrypto*.dll"Run the first five commands in Command Prompt and the final two in PowerShell. Record every duplicate DLL location before changing anything.
Match PHP, Apache, and their runtime libraries
The PHP manual’s Windows binary guide distinguishes x64 from x86 and Thread Safe from Non Thread Safe builds. Apache with apache2handler requires Thread Safe PHP. The PHP module, Apache process, Visual C runtime, and OpenSSL dependencies must be compatible.
Windows resolves dependent DLLs using its search rules. Apache can load an older libssl from apachein before reaching the new copy in the PHP directory. The PHP OpenSSL documentation recommends making the required DLLs available through the supported runtime layout rather than scattering copies through Windows system directories.
Upgrade the stack as one tested unit
Back up the entire XAMPP directory and application data. Prefer a XAMPP release that officially bundles the required PHP generation, or install a separate matching Apache and PHP stack. Replacing only the PHP folder can leave Apache linked to another OpenSSL generation.
Start from the new PHP distribution’s configuration template and merge required settings deliberately. Do not copy an old php.ini wholesale; extension names, defaults, and paths change. Remove stale directories from PATH, then restart the terminal and Apache service before retesting.
Verify both php -v and a temporary phpinfo() page because the CLI and Apache can load different binaries and configuration files. Continue with installing PHP on Windows, diagnosing XAMPP Apache startup errors, and checking Windows DLL dependencies.
