XAMPP: Couldn't start Apache (Windows 10)
When working with local development stacks like XAMPP on Windows 10, encountering an immediate shutdown of Apache after a configuration change is frustrating but often solvable. The specific error log you are seeingâAH00072: make_sock: could not bind to address [::]:445 followed by AH00451: no listening sockets available, shutting downâpoints directly to a binding failure rather than a general permission issue or missing dependency.
The root cause in your scenario is almost certainly the port configuration conflict between your custom settings and XAMPP's default behavior, compounded by how Apache attempts to bind to both IPv4 and IPv6 addresses simultaneously. You have successfully changed the Listen directive in httpd.conf to 122, but Apache also defaults to listening on port 443 for SSL and often attempts to listen on the standard HTTP port 80 if not explicitly restricted.
In your configuration, you set the Main port to 122 and the SSL port to 444. However, the error log indicates Apache is trying to bind to port 445. This mismatch suggests that while you edited httpd.conf, either a separate virtual host file (commonly found in the sites-enabled or conf.d directories) is still defining a listen directive for port 80 or 443, or the SSL configuration within ssl.conf or ports.conf is overriding your settings. On Windows, XAMPP sometimes ignores changes made strictly inside httpd.conf if it relies on default included files that haven't been updated to match your new port scheme.
The error (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions is a generic Windows error that appears when the port is already in use or, more commonly in this context, when the application lacks the necessary privileges to bind to specific addresses. However, since you have already uninstalled Skype and ensured no other process is holding ports 80, 443, or 122, the permission error is likely a symptom of the binding failure itself: if Apache cannot bind to its intended address, it attempts fallback mechanisms that may fail if the system security policies are strict.
To resolve this, you must ensure consistency across all configuration files. First, check ports.conf (located in xampp\apache\conf\extra\) and verify that the StartListenBacklog or any custom port definitions do not conflict with your new setup. More importantly, inspect the SSL configuration. If you are not actively using HTTPS for development, it is best practice to comment out the SSLCertificateFile and SSLCertificateKeyFile directives in the SSL config file entirely, preventing Apache from attempting to bind to the SSL port (currently set to 444 in your Service settings, but potentially trying 443).
Regarding the missing log files: Apache on Windows does not create its error log (error.log) or access log (access.log) until the server actually starts and attempts to write to them. If the startup sequence fails immediately due to a binding error (which it did in your case), the daemon exits before initializing the file handles required to create these logs. This is normal behavior for Apache on Windows; do not assume a missing error.log indicates a deeper filesystem issue.
Finally, ensure that the ServerName directive matches your Listen directive exactly. You have Listen 122 and ServerName localhost:122, which is correct. If you have any virtual host files (e.g., vhost.conf) pointing to port 80 or 443, delete or update them to point to port 122 as well. Once the configuration is consistent across all included files and Apache successfully binds to port 122 without conflicting with an SSL handshake attempt on a different port, the server should remain running. For complex local stack setups involving PHP, frameworks like Laravel often require specific directory permissions; if you plan to move beyond simple static testing, consider using Docker or switching to a Linux-based VM (like Ubuntu) via WSL2, as XAMPP on Windows can become brittle when handling non-standard port configurations and mixed IPv4/IPv6 bindings.