Cause analysis of 80 port conflict:

The main reason is that WampServer's default installation port is 80, which easily conflicts with other services such as installed ISS, resulting in WampServer's failure to start.

Programs that usually occupy port 80 are: Thunder, IIS.

How to check which program is using port 80?

Methods to detect the occupation of port 80: Start-Run-Enter cmd (Enter)-Open a command prompt and enter -netstat.

-ano, you can view the opening of local ports and corresponding programs.

. As shown in the figure below:

As can be seen from the figure, port 80 is occupied by a process with PID (process identifier) of 1720. Now as long as you know the process with PID of 1720, you can release port 80.

Open the Task Manager as shown below:

The default task manager has no PID, just check the PID in the view options column.

As can be seen from the figure, the process corresponding to PID: 1720 is inetinfo.exe. (inetinfo.exe process will be explained later) If you directly end this process now, inetinfo.exe will automatically re-run, but the PID will be changed at this time. This does not completely release the port 80.

Last operation: stop.

IIS "default website. In fact, the culprit is IIS, because I have made a website before and need to install IIS. I have created a website in Control Panel-Administrative Tools-Internet.

Information service-you can see this site at the bottom of the website, just stop it, and then you can start-run-enter cmd-open the command prompt-netstat.

-ano, you can see there is no port 80. When the software is installed, everything will be fine.

Note: the process PID can be changed, that is, when the same program runs at different times, its PID number is different. The PID number of the same process of different computers is different in most cases. So the PID before ending inetinfo.exe is three digits, and it may be four digits after restarting. This does not affect the solution of the problem. I'm just curious, just take it out and say it.