How to find what is using a port on Windows
See which process is listening on a TCP port on Windows using PortPilot, plus netstat as a fallback.
On Windows, a “port in use” error usually means some process is listening on that TCP (or UDP) port.
With PortPilot
- Install PortPilot and open Ports in the desktop app (or
portpilot ports). - Find the port. Bind address matters:
127.0.0.1:3000is not the same as0.0.0.0:3000. - Open the port. You get process name, pid, executable, and a service when Windows maps one.
You can do the same from the cloud dashboard after pairing.
Without PortPilot
Administrators often use:
netstat -ano | findstr :3000Then Task Manager or tasklist /FI "PID eq <pid>". PortPilot exists so you do not have to stitch those tools together every time.