Windows kill process listening on port

This answer was originally posted to this question. It's not ideal, but if you use Sysinternals' Process Explorer you can go to specific processes' properties and look at the TCP tab to see if they're using the port you're interested in.

It is a bit of a needle and haystack thing, but maybe it'll help someone I recommend CurrPorts from NirSoft. CurrPorts can filter the displayed results. TCPView doesn't have this feature. Process Explorer. Process Dump. Port Monitor. If you just want to know process running and threads under each process, I recommend learning about wmic.

It is a wonderful command-line tool, which gives you much more than you can know. The above command will show an all process list in brief every 5 seconds. Programmatically, you need stuff from iphlpapi. Using PowerShell You can also check the reserved ports with the command below. Hyper-V reserve some ports, for instance. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Collectives on Stack Overflow. Learn more. Ask Question. Asked 13 years, 4 months ago. Active 10 months ago. Viewed 4. Improve this question. Ben Voigt k 38 38 gold badges silver badges bronze badges. DavidJesus doesn't show process on windows Show 2 more comments. Active Oldest Votes.

Improve this answer. Tereza Tomcova 4, 2 2 gold badges 28 28 silver badges 27 27 bronze badges. Brad Wilson Brad Wilson You may have to run your command line shell as administrator, otherwise you may get an error message about insufficient privileges. Use the "Run as administrator" option when right-clicking cmd. If you have a different way than we discussed here feel free to sound off in the comments. This site uses Akismet to reduce spam.

Learn how your comment data is processed. Username or Email Address. Remember Me. Sign Up For Our Newsletter. Linux Tutorials. However, be sure that tutorial can help you solve the occupancy of any other port. When you develop long enough with Spring Boot, you know the error very well. You work on your Spring Boot application, and you use a console for running the application.

Your Spring Boot application in the running embedded in servlet container when suddenly you need to do something else. Instead of adequately terminating the embedded servlet container with your application, you detach from the servlet by a closing terminal window or switching to a different project in IDE. After that, you might, of course, start developing something else. Surprise, surprise, you cannot.

Any Spring Boot application port, by default number , is still occupied with the unterminated process of your Spring Boot servlet container. In the tutorial, we assume you are using the Spring Boot application port on default port number I guess you might be a little bit confused by all the wording describing the issue. We are aware that readers of this blog are pretty skilled in computers.

So, we will provide a brief description of what is computer process without going to further details. Every time you start a program on your computer, it requires a certain amount of resource. The above output shows the pid is 4 for the process listening on port The second method uses PowerShell command to find out process running on specific port on Windows.

Launch the PowerShell terminal and execute following command to find process name running on port You can change port number to check for other ports. In this tutorial, you have learned two methods to find process name listening on specific port on Windows system.