This is the fact that the occasional software prompts ports occupied recently, unable to start, but with netstat ano | findstr searches [port] see nothing, tcpview don't see any trace, restart the system to solve the problem, then write their own port test program, found that this phenomenon is not individual port, but a number of port is continuous ban, here are some test results:
Shortly (minutes) 1) on the test results, is not been ban the phenomenon after 4991
1582-2081, 500 consecutive
2180-2380, 200 consecutive
3790-4489, 700 consecutive
4492-4991, 500 consecutive
2) the result of the continuous boot a day or so; Actually the test early, when a 5000-10000 test only
5507-6206, 700 consecutive
6528-7227, 700 consecutive
7635-8334, 700 consecutive
8357-8856, 500 consecutive
List cannot be binding port, error message is [with a way to access is not allowed to do an attempt to access a socket,], and in the netstat shows nothing
Apparently there is a big problem, either in the virus, or a program exit no normally closed connection, but also can specify the number of times to restart
Just leaves tcpview boot, do see some some of the links, that process is svchost, but wasn't sure whether the port was ban port, and this is the service host, tcpview don't show the command line, don't know is which service
The system is 19041.508 2004 win10,
What a great god can give me a train of thought, how to program the question out??