Освободить порт 8080 windows 10

asked Sep 22, 2016 at 7:19

Step 1:

Open up cmd.exe (note: you may need to run it as an administrator, but this isn’t always necessary), then run the below command:

netstat -ano | findstr :<PORT>

(Replace <PORT> with the port number you want, but keep the colon)

The area circled in red shows the PID (process identifier). Locate the PID of the process that’s using the port you want.

Step 2:

Next, run the following command:

taskkill /PID <PID> /F

(No colon this time)

Lastly, you can check whether the operation succeeded or not by re-running the command in «Step 1». If it was successful you shouldn’t see any more search results for that port number.

I know that is really old question, but found pretty easy to remember, fast command to kill apps that are using port.

Requirements: [email protected]^ version

npx kill-port 8080

You can also read more about kill-port here: https://www.npmjs.com/package/kill-port

answered Jun 16, 2020 at 10:32

There are two ways to kill the processes

npx kill-port 8080

Option 02 — Most commonly used

• Step 01

  Open Windows command prompt as Administrator

• Step 02

  Find the PID of the port you want to kill with the below command: Here port is 8080

netstat -ano|findstr "PID :8080"

TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 18264

• Step 03

  Kill the PID you received above with the below command (In my case PID is 18264)

taskkill /PID 18264 /f

answered Jul 21, 2020 at 4:16

Step 1 (same is in accepted answer written by KavinduWije):

netstat -ano | findstr :yourPortNumber

Change in Step 2 to:

tskill typeyourPIDhere 

Note: taskkill is not working in some git bash terminal

With Windows 10/11 default tools:

✔ Step one:

Open Windows PowerShell as Administrator

✔ Step two:

Find the ProcessID for the port you need to kill (e.g. 3000)

netstat -aon | findstr 3000

TCP 0.0.0.0:3000 LISTEN 1234

✔ Step three:

Kill the zombie process:

taskkill /f /pid 1234

where «1234» is your ProcessID (aka PID)

*Extra tip if you use Windows Subsystem for Linux (Ubuntu WSL):

✔ Step one:

sudo lsof -t -i:3000

✔ Step two:

sudo kill -9 1234

answered Mar 18, 2019 at 10:01

If you are using GitBash

Step one:

netstat -ano | findstr :8080

Step two:

taskkill /PID typeyourPIDhere /F 

(/F forcefully terminates the process)

The simplest solution — the only one I can ever remember:

In Windows Powershell

Say we want to stop a process on port 8080

1. Get the process:

netstat -ano | findstr :8080

1. Stop the process

stop-process 82932

answered Sep 3, 2021 at 15:38

If you already know the port number, it will probably suffice to send a software termination signal to the process (SIGTERM):

kill $(lsof -t -i :PORT_NUMBER)

answered Dec 19, 2018 at 7:43

For use in command line:

for /f "tokens=5" %a in ('netstat -aon ^| find ":8080" ^| find "LISTENING"') do taskkill /f /pid %a

For use in bat-file:

for /f "tokens=5" %%a in ('netstat -aon ^| find ":8080" ^| find "LISTENING"') do taskkill /f /pid %%a

Simple CMD is working me. Easy to remember

find the port number which you want kill and run the below cmd

npx kill-port 8080

After complete the Port get stopped and getting this message

npx: installed 3 in 13.796s
Process on port 8080 killed

In Windows PowerShell version 1 or later to stop a process on port 3000 type:

Stop-Process (,(netstat -ano | findstr :3000).split() | foreach {$[$.length-1]}) -Force

As suggested by @morganpdx here`s a more PowerShell-ish, better version:

Stop-Process -Id (Get-NetTCPConnection -LocalPort 3000).OwningProcess -Force

answered Dec 8, 2017 at 15:54

Open command prompt and issue below command

netstat -ano|findstr "PID :8888"

Output will show the process id occupying the port

Issue below command to kill the PID

taskkill /pid 8912 /f

You will receive the output as below

SUCCESS: The process with PID 8860 has been terminated.

answered Mar 31, 2021 at 13:08

If you can use PowerShell on Windows you just need :

Get-Process -Id (Get-NetTCPConnection -LocalPort "8080").OwningProcess | Stop-Process

answered Oct 27, 2020 at 10:20

For Windows users, you can use the CurrPorts tool to kill ports under usage easily:

answered Dec 6, 2018 at 4:29

answered May 10, 2021 at 10:46

If you’re using Windows Terminal then the killing process might be little less tedious.
I’ve been using windows terminal and kill PID works fine for me to kill processes on the port as the new Windows Terminal supports certain bash commands. For example: kill 13300

So, the complete process will look like this-

• Open Windows Terminal
• Type the following command to show processes running on the port you’re looking to kill processes.
  netstat -ano | findstr :PORT
• Type following to kill the process.
  kill PID

For Example:

PS C:\Users\username> netstat -ano | findstr :4445
  TCP    0.0.0.0:4445           0.0.0.0:0              LISTENING       7368
  TCP    [::]:4445              [::]:0                 LISTENING       7368
PS C:\Users\username> kill 7368
PS C:\Users\username> netstat -ano | findstr :4445
PS C:\Users\username>

See when I typed the first command to list processes on the port it returned empty. That means all processes are killed now.

Update: kill is an alias for Stop-Process. Thanks, @FSCKur for letting us know.

answered May 21, 2020 at 9:55

If you use powershell 7+ this worked for me. Just add this function in your $PROFILE file.

function killport([parameter(mandatory)] [string] $uport){
    if($upid = (Get-NetTCPConnection -LocalPort $uport -ErrorAction Ignore).OwningProcess){kill $upid}
}

then simply use killport 8080

or if you prefer just the command you can try this:

kill $(Get-NetTCPConnection -LocalPort 8761 -ErrorAction Ignore).OwningProcess

answered Feb 1, 2022 at 19:19

flopcoderflopcoder

1,19512 silver badges26 bronze badges

the first step

netstat -vanp tcp | grep 8888

example

tcp4     0      0    127.0.0.1.8888   *.*    LISTEN      131072 131072  76061    0
tcp46    0      0    *.8888           *.*    LISTEN      131072 131072  50523    0

the second step: find your PIDs and kill them

in my case

sudo kill -9 76061 50523

answered Aug 25, 2020 at 19:35

harun ugurharun ugur

1,72620 silver badges19 bronze badges

One line solution using GitBash:

 tskill `netstat -ano | grep LISTENING | findstr :8080 | sed -r 's/(\s+[^\s]+){4}(.*)/\1/'`

Replace 8080 with the port your server is listening to.

If you need to use it often, try adding to your ~/.bashrc the function:

function killport() {
        tskill `netstat -ano | findstr LISTENING | findstr :$1 | sed -r 's/^(\s+[^\s]+){4}(\d*)$/\1/'`
}

and simply run

killport 8080

answered May 20, 2020 at 21:04

I wrote a tiny node js script for this. Just run it like this:
node killPort.js 8080 or whatever port you need to kill. Save the following to a killPort.js file:

const { exec } = require('child_process');
const fs = require(`fs`);

const port = process.argv.length > 2 ? process.argv[2] : ``;
if (!port || isNaN(port)) console.log(`port is required as an argument and has to be a number`);
else {
    exec(`netstat -ano | findstr :${port}`, (err, stdout, stderr) => {
        if (!stdout) console.log(`nobody listens on port ${port}`);
        else {
            const res = stdout.split(`\n`).map(s => s.trim());
            const pid = res.map(s => s.split(` `).pop()).filter(s => s).pop();
            console.log(`Listener of ${port} is found, its pid is ${pid}, killing it...`);
            exec(`taskkill /PID ${pid} /F`, (err, stdout, stderr) => {
                if (!stdout) console.log(`we tried to kill it, but not sure about the result, please run me again`);
                else console.log(stdout);
            })
        }
    });
}

answered Aug 31, 2021 at 9:11

Vatsal ShahVatsal Shah

1,33418 silver badges21 bronze badges

MyrionSC2MyrionSC2

1,2481 gold badge14 silver badges24 bronze badges

We can avoid this by simple restarting IIS, using the below command:

IISRESET