This happened to me, apparently another application (VideoStream in my case) used the same port as adb. To fix this, use PowerShell (with elevated permissions) to find the process using the port where you get the error message:
Get-Process -Id (Get-NetTCPConnection -LocalPort portNumber).OwningProcess
You will know the PID because it is displayed in the Id column.
Then open the task manager and right-click on the toolbar at the top (Name, Status ...) and enable the PID to view the process ID. Then find the PID you got during the search and kill it.
This fixed it for me.
user8812119 Jan 15 '19 at 10:04 2019-01-15 10:04
source share