"Go" WINDOWS10 analysis and solution of 80 ports under the system occupancy of PID 4 that caused Apache to fail to start

Yesterday just updated the WINDOWS10, the overall effect is pretty good, but today in the Apache server on the time but found that Apache inexplicably open, initially thought is the issue of permissions, and then use the Administrator's console to invoke command net start Apache2.4, the result is still unable to open. Manually start service error "windows can no longer start Apache on the local computer, check the system time log for more information." If this is a non-Microsoft service, contact your service vendor and refer to the specific service error code 1. "as shown:

Windows can no longer start Apache on the local computer, consult the system time log for more information. If this is a non-Microsoft service, contact your service vendor and refer to the specific service error code 1.

Seeing this, I have manual CD to Apache Httpd.exe directory, executed a bit of httpd, this reason found, as shown in:

(OS 10013) makes an attempt to access the socket in a way that is not allowed by access rights. : AH00072:make_sock:could not bind to address 127.0.0.1:80
Ah00451:no listening sockets available, shutting down
Ah00015:unable to open logs

You can see that the error is caused by a socket binding error, which can be determined that the 80 port of Apache is occupied. So use the command Netstat-ano to see exactly which program is taking up port 80, the result of Port lookup:

See 80 port by PID 4 system process Occupy, oh, I want to say a word I wipe what ghost +_+. Think carefully, the general program will not occupy 80, then use the command netsh http show servicestate to see the current HTTP service status, found that there is a problem, as shown in:

As you can see, port 80 is occupied by a defaultapppool, if you use the child shoes of IIS, this time must have thought of the reason, here we still have to go down to find the reason, the figure can be seen in the controller process ID 4640, then Just keep looking at what the 4640 process is, go to the Task Manager, find the PID4640 process, right-click on the service, and you can see the service where the current process is located:

Seeing the services in the diagram, here are the reasons why the IIS World Wid Web Publishing Service is a problem.

Solution:

Control Panel –> program –> Enable or disable Windows features –> find the Internet information Service, turn it off

Reprint Please specify: leisurely tasting»WINDOWS10 under the 80-port PID 4 system occupancy causes Apache to fail to start the analysis and solution

"Go" WINDOWS10 analysis and solution of 80 ports under the system occupancy of PID 4 that caused Apache to fail to start