ADB resolution when ADB server is out of date

The reason for the error is that the ADB port is occupied by other programs ' processes, so what to do is to find and kill the process. Steps:

1. Execute ADB nodaemon server in cmd, see what the ADB's port number is, and generally 5037 (why?) I don't know, maybe the port number used by the software is fixed.

2, re-execute Netstat-ano | Findstr "5037", you will see a similar scenario as follows:

A little explanation here is that the left-to-right meaning is the connection type (TCP), the local address and port, the external address and port, the connection status, and the PID number of the process. Here are two processes occupy 5037 ports, one occupies the local 5037 port, the other occupies the external 5037 port, to kill the local PID is the port of 240!

3, Ctrl+alt+del call to serve the manager. Click Process, now looking for a PID of 240 process. Sometimes you may find that the Task Manager does not have the process PID information display, this time just click on the task Manager's view--and select the column, then the PID check. At this time to review the current process of the PID, the PID 240 process kill can be.