On windows 10 pro 80 the port is closed tightly by the TCP 4 protocol?

Question

Apache HTTP Server

I can’t close it and put 80 on Apache, windows 10 pro doesn’t let me go further through the settings.
There are a lot of processes on this connection, I tried to close which could have been on other windows before, it's useless. Who already knows, I did not find it on the net.
Temporarily changed the port on the server to 8080 - it works, but it needs to be 80
System
TCP
Process ID
4
Protocol
http
Local address
0.0.0.0
---------------------
Solved.
Thanks, I fixed it, only there you don’t need Dword right away, but the next one next to it with the number 64. I understood this joke, and how to avoid it for everyone else who doesn’t know how to climb the terrible register, if you don’t have Skype, like I didn’t have when installing 10 pro, install it and set port 80, when 10 is installed, feel free to change or delete skype.

Answer 1

habrahabr.ru/post/145189
Apparently, the built-in http service starts along with the system kernel. Try the following:
1) Go to the registry. Run->regedit
2) To the branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
And the difference in these methods:
3) Create a Dword type parameter with the name "NoRun" and assign it the value "1" without quotes.
or
3) We are looking for the “Start” parameter and change the value to “0” without quotes, naturally.
4) Reboot the computer.
But first, read the article, maybe in the 10th Windows some other things with the kernel can hang.

Answer 2

Assumption.
Skype uses port 80 by default. You can turn it off in Skype settings.
If Skype is pre-installed at 10 initially, this may be one of the problems.
I met with this earlier on 7ke.

Answer 3

Disabling the W3SVC service, the Web Publishing Service, just helped me. Windows 10

Answer 4

Find IIS -> Internet Services -> Security -> uncheck Request Filtering

Answer 5

Nothing helped me, the port was tightly occupied by the System SID - 4
process. I removed various software, including VMware Player, most likely it was the problem, the port was freed;)