Port 80 is being used by SYSTEM (PID 4), w

Question

I am trying to use port 80 for my application server, but when I perform netstat -aon I get:

TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4

When I look up the process in task manager, it shows PID 4 is SYSTEM, that's it. No extension... nothing. Just "SYSTEM". What's going on here?

I'm afraid to end this process, what do I do?

---

UPDATE:

I've solved this through another Stack Overflow question, which had the solution to get IIS to stop listening on port 80 for a specified IP address.

Answer 1

This Process works for me:

1. Right click on My Computer.
2. Select Manage.
3. Double click Services and Applications.
4. Then double-click Services.
5. Right click on "World Wide Web Publishing Service".
6. Select Stop
7. Restart XAMPP

Answer 2

I just went to service and stopped web deployment agent

Answer 3

type netstat -a -n -b -o |more

if stopping World Wide Web Publishing Service helps

then in IIS manager review each site's bindings settings, by selecting a site and on the side panel click on binding. then change port 80 to something else if required.

Answer 4

I had the same problem and it was because of IIS running on the server, you can stop it using IIS Manager if it is the case for you.

Answer 5

None of these worked for me. I had to go to a superuser question: https://superuser.com/questions/352017/pid4-using-port-80.

---

If it is a System Process—PID 4—you need to disable the HTTP.sys driver which is started on demand by another service, such as Windows Remote Management or Print Spooler on Windows 7 or 2008.

There is two ways to disable it but the first one is safer:

1.

Go to device manager, select “show hidden devices” from menu/view, go to “Non-Plug and Play Driver”/HTTP, double click it to disable it (or set it to manual, some services depended on it).

Reboot and use netstat -nao | find ":80" to check if 80 is still used.

---

This is the one that worked for me!

Answer 6

If you are running Windows Server 2012 R2 then make sure to get rid of Work Folders: http://blogs.technet.com/b/filecab/archive/2013/10/15/windows-server-2012-r2-resolving-port-conflict-with-iis-websites-and-work-folders.aspx Removing Work Folders feature under File Server worked for me.