I have discovered a running process with PID 26376 listening on port 9001 and 9002 as when I try to run my program(as a service) which binds to that port it fails.
B
Another option is to bounce the NIC associated with the connection. Be careful if you are doing this over RDP, you'll want to script it so the NIC will come back online or you'll lock yourself out and will need console access.
This link explains how to do it with CMD and powershell:
https://www.windowscentral.com/how-enable-or-disable-wi-fi-and-ethernet-network-adapters-windows-10
(improved from @mfck's answer)
cmd.exe
conhost.exe
You don't need Task Manager for tracking this. Just run netstat -b
which will display the exe associated with the PID..
Well, in my case killing all the conhost.exe instances owned by the same user as the initial process released the port.