Reason 1: Port 80 is occupied

For example, IIS, and the other is Thunder. My apache server has been disabled by Thunder!

Reason two: software conflict

Installing some software will make apache unable to start, such as Dr.com. You open the network connection -> TcpIp Properties -> Advanced -> WINS tab, uncheck the lmhosts of netbios, and disable the tcp/ip netbios. Then start again It should be fine.

Reason three: httpd.conf configuration error

If the apache configuration file httpd.conf is wrong, start it in windows, it will prompt the requested operation has failed, which is rather depressing, because it will take a long time to check the error.

In fact, you can start apache in command line mode with parameters, apache will prompt you which sentence is wrong, and then you can solve it specifically, the command is as follows: httpd.exe -w -n "Apache2" -k start

There is another situation:

Even if you start this time, you may fail to start next time

Enter in running: netsh winsock reset

After a while, cmd will prompt you to restart, don't worry about it, now APACHE can start.

Is actually a winsock fix