This has long bugged me. after upgrading to Windows 8, i already cannot run my XAMPP server without using ports other than port 80, since a process called "NT Kernel & System" is using it. It's a system process so I cannot disable it. I don't have any IIS or Web Server installed so I am pretty frustrated how to use that Port 80.
If anyone of you who knows how to change the port "NT Kernel & System" uses, that would be great!
Thanks!
I ran into this problem after installing just Apache 2.2.22 on Windows 8. What I'm strongly convinced of after scouring many forums for information is that the most common cause of this issue on Windows, which produces the "make_sock could not bind to address 0.0.0.0:80" error, is that IIS is running. Stopping the World Wide Web Publishing Service is what finally enabled Apache to start for me as well.
I ran into the same problem with NT Kernel listening on port 80 when I wanted to get my own application listening on that port.
After stopping
- IIS
- World Wide Web Publishing service
- IIS Admin Service
- SQL Server Reporting services
the NT Kernel was still listening on port 80
It was finally when I stopped the "Web Deployment Agent Service" that it stopped listening on 80.
Note: use netstat -bano in an elevated command prompt to see what apps are listening on which ports.
a whole bunch of services might have grabbed port 80:
http://lordamit.blogspot.de/2012/06/windows-7-windows-8-apache-errorport-80.html
it's hard to say which one caused your system to do it, i had to disable the "World Wide Web Publishing Service".
In addition to World Wide Publishing, I had to stop the Web Deployment Agent Service, which kicked off the HTTP Service.
stopping the w3svc service worked for me - just write in an elevated command prompt (VS2017 command prompt started as administrator):
sc stop w3svc
来源：https://stackoverflow.com/questions/12492025/windows-8-nt-kernel-and-system-using-port-80