Posted: 2015-08-24 19:50:51
With everyone taking the Windows 10 upgrade, this question has been coming up often…
I recently upgraded to Windows 10, and as a result WAMPDeveloper’s Apache service won’t start. It produces the following error message:
Error (OS 10013) An attempt was made to access a socket in a way forbidden by its access permissions. :AH00072: make_sock: could not bind to address [::]:80 (OS 10013) An attempt was made to access a socket in a way forbidden by its access permissions. :AH00072: make_sock: could not bind to address 0.0.0.0:80 AH00451: no listening sockets available, shutting down AH00015: Unable to open logs
The problem is that Windows 10 now comes with several extra Services that take port 80 (HTTP) and 443 (HTTPS), which Apache needs to start.
If Apache will not start (due to the above binding/socket/port issue), then one of these two Services is running on Windows 10.
These services are not needed for Windows functionality and can be safely disabled.
Run ‘services.msc’, select the service, click to stop it, and then change its Startup Type from “Automatic” to “Disabled”.
If you are still not able to start Apache, check the bigger list of services that prevent Apache from starting.