DevKill1.1.0

DevKill finds orphaned development-server processes occupying ports and lets you terminate them, resolving conflicts caused by abandoned local services. It detects listening processes through native Windows APIs rather than parsing netstat output, and automatically identifies servers such as Node, .NET, Python, PHP, Vite, and others. The dark Fluent UI presents the discovered processes, while individual or bulk controls let you stop one process or several at once. Automatic polling refreshes the process view every three seconds as port activity changes.

Search and filtering narrow results by port number, process name, or PID, and smart grouping places recognized development servers in a dedicated Dev Servers section. The system-tray mode keeps DevKill available with a quick-kill context menu, and an optional registry setting can start it with Windows. Developers can also run devkill 3000 from the command line to free port 3000 without opening the graphical interface. Classification relies on a whitelist containing node, dotnet, php, iisexpress, python, python3, ruby, java, deno, bun, uvicorn, gunicorn, nginx, httpd, apache, hugo, caddy, and vite.

It suits developers switching among projects, restarting local APIs, or cleaning up servers left behind by closed terminals. Andy Bochmann publishes DevKill as open-source software for Windows in the System Tools category. Version 1.1.0 supports x64 systems running Windows 8 or later and Windows Server 2012 or later. Administrator privileges are required to enumerate and terminate all processes.