At the outset, let me say I'm on Windows 10.
OK, opening a port in Windows Firewall is fine. But, um, I'm not using Windows Firewall.
In Services, I have long ago stopped and DISABLED the service for Windows Firewall (MPSSVC)
In Services, I have long ago stopped and DISABLED the service World Wide Web Pubilishi8ng Service (W3SVC)
And STILL I have a monopolized port that shows up in WinInternals TCPVIEW as being opened (as a LISTEN) by some process called SYSTEM on PID 4. Now, I know I can't get rid of that (or I can, but that's a major OS move). So, what did I do wrong. Or did MS
simply but high-handedly take control of port 80 from now on. I don't use IIS. This is dumb. There must be another process to kill, Could it be that the IIS Admin Service (IISADMIN) is holding things open just in case, not simply on port 8098 or whatever it
uses, but holds open port 80 on all interfaces? That's high-handed, too. I just now stopped it, disabled it, and there's been no change. I'm hoping a restart will loosen things up. Otherwise I'll have to use a 3rd party for some of the basic services. SMTP,
FTP, etc. as it seems this all started when I added the "simple' services. I don't need this headache that can't be cured.
And I already HAVE a firewall, thank you very much.
jt