WAMP, XAMPP, Apache Won’t Start on Windows 10

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, and more-so with the upgrade, now comes with several extra Services that take port 80 (HTTP) and 443 (HTTPS) that Apache needs to start.

If Apache will not start (due to the above binding/socket/port issue), than one of these two Services is running on Windows 10.

1. Web Deployment Agent Service (MsDepSvc)
2. IIS / World Wide Web Publishing Service (W3SVC)

These services can be safely disabled and are not needed for Windows functionality.

Run ‘services.msc’, select the service, click to stop it, and then change its Startup Type from “Automatic” to “Disabled”.

You’ll be able to start Apache right after that.

Share this

Fathih IT Info