jclancy
asked on
Windows 10 Socket error 10013 with Firewall & Defender disabled
I have a small server process that I've run for years on XP through Win 8.1. However, when I try to run it on Windows 10 I get the subject socket error. I think I know why but I don't know how to solve it. Both the Firewall and Defender are disabled, so they are not the problem.
The server process, of course, wants to use port 80 but, unlike the other windows versions, Win 10's kernel (ntoskrnl.exe) grabs the port when booting, so it is not available. How do I resolve this? I clearly can't stop the kernel process.
The server process, of course, wants to use port 80 but, unlike the other windows versions, Win 10's kernel (ntoskrnl.exe) grabs the port when booting, so it is not available. How do I resolve this? I clearly can't stop the kernel process.
ASKER
I saw this before I posted. Look again at my subject line: both the Firewall and Defender were disabled and I still got the socket error because the kernel has grabbed Port 80.
You are likely not running anything competing for Port 80.
You are likely not running anything competing for Port 80.
ASKER
BTW, the server dies this way also when run as administrator, so it doesn't appear to be a permissions issue.
Windows 10 is much more secure. Check if you have aggressive AV installed like McAfee or Kaspersky because that can cause issues as well
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It works.
Please look at this Microsoft article below:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/socket-10013-error-when-trying-to-connect-some/2cc71cb6-24b2-4b63-8f60-32bb444eb8fd?auth=1
Quote from the article: "A socket error 10013 can be caused by antivirus or firewall software. Basically, a needed socket connection is being denied. Socket error 10013 is a message which implies that a port is blocked and/or unreachable"