Is there a command equivalent to 'ps' on Unix that can list all processes on a Windows machine?

14 Answers 14


Working with cmd.exe:


If you have Powershell:


Via WMI:

wmic process

(you can query remote machines as well with /node:ComputerOrIP, and there are a LOT more ways to customize this command: link)

  • 34
    you might want to pipe it to the clipboard then paste into notepad: c:\>tasklist | clip – Keith Aug 25 '11 at 21:04
  • 3
    Specifically you could try >tasklist /FI "SERVICES eq wampapache" – RiggsFolly May 1 '13 at 0:25
  • If I list tasks with tasklist, how do I then end a task from command prompt? – Kyle Delaney Mar 17 '17 at 21:59
  • If you use Powershell, it's really convenient to pipe it to Out-Gridview, like this: "Get-Process | Out-GridView" – Charles Burge Jun 1 '18 at 6:44
  • 1
    Or just pipe it directly into a text file: C:>tasklist > C:\myProcesses.txt – P.Brian.Mackey Dec 26 '18 at 13:37

There is a tool called Windows Management Instrumentation Command-line tool (wmic.exe).

You can call wmic process list to see all processes.

  • 4
    I found this s.o. thread while trying to solve the same problem, and wanted to point out that wmic worked well for me. With wmic you can choose the most appropriate output for parsing, using /format:csv or /format:rawout. Beware: wmic does not implement csv format correctly (fields are never quoted, even if they contain embedded quotes or commas), so I was forced to use xml. – JimN Jul 28 '11 at 2:05
  • 1
    @JimN - /format:rawxml and not /format:rawout – Joe Jan 24 '14 at 15:32
  • Can you filter any process using wmic ? – Kiquenet Sep 3 '15 at 5:40
  • If you need to find the command line that launched the process this is the answer – Shane Gannon Feb 15 '16 at 16:30

I wanted to mention that WMIC (pam's entry) can do a lot more. Have a look at my WMIC snippets page, which is a cheatsheet showing many of the common ways to use WMIC (with sample output shown) here

  1. Tasklist

  2. WMIC /OUTPUT:C:\ProcessList.txt PROCESS get Caption,Commandline,Processid


 WMIC /OUTPUT:C:\ProcessList.txt path win32_process get Caption,Processid,Commandline

I tried on Windows 7. The command is: TASKLIST /FI "IMAGENAME eq application_name"

Eg: c:\>TASKLIST /FI "IMAGENAME eq notepad.exe"

To show all process with port details:


Also to kill the process you can use c:\> pskill or tskill processname

Eg: c:\> tskill notepad

  • 1
    TASKLIST /FI "IMAGENAME eq explorer.exe" returns one whole line as output. Is there anyway to get just the PID itself? – Pacerier May 5 '15 at 0:03
  • for a more human-memorable command, taskkill is synonymous to tskill – Mushroom Man Dec 5 '17 at 1:24
  • On 8.1, there is no tskill only taskkill, and pskill is provided by SysInternals but not Windows. (@KiritoBepsibane) – dave_thompson_085 Jun 1 '18 at 6:59

tasklist or pslist from sysinternals. Also, get-process is amazing from PowerShell.


If you use Powershell, it has the 'ps' command (it is aliased to Get-Process)


If you running windows XP try using the 'tasklist' command. I tried it out with Vista and it seems to also work.


Use this command to see all the processes in windows machine

tasklist /svc

  • 1
    Can you filter any process using tasklist with pipe or another way ? – Kiquenet Sep 3 '15 at 5:41
  • @Kiquenet Yes you can: tasklist|findstr "firefox.exe". If this returns an errorlevel of 1 the process was found in the list of processes. – Andreas Mar 18 '16 at 6:48
  • @mrt: findstr doesn't need quotes around the needle unless it contains space or special character like & although find does, and both of them return 1 for NOT found (0 for found). – dave_thompson_085 Jun 1 '18 at 6:54
  • @dave_thompson_085 Of course you are right, but in my opinion it's a good habit to put strings into quotes. This keeps me from accidently leave them out when they are needed. Also, it makes the statement easier to read since it's instantly obvious what the search term is. – Andreas Jun 3 '18 at 15:26

To kill a process use:

TASKKILL /F /IM processname.exe

For example:

TASKKILL /F /IM firefox.exe
  • This isn't a good answer. The question is how to list processes, not how to kill them. – Rikki Gibson Sep 30 at 21:47

I had following problem on Windows 2003 SP2: Tasklist didn't return any output on stdout or stderr, when called from a process started as Windows service (even under Local Account). Tasklist returned with the (undocumented) code 128.

Called from the same program started as a normal process (not as service), it did run.

No help to change it. I couldn't find any reason or solution but use "pslist /accepteula" of sysinternal instead of it.

Same problem with taskkill: I had to replace it whith pskill.


I have done a msproject ( c source code) , archive is available at : lsproc.zip project archive

and exe file: lsproc.exe binary

this is a command line tool output:

Thierry Bremard
list binary files and driver with their local path on disks
most of code retreived from msdn site

Process ID: 0

Process ID: 4
<unknown>  (PID: 4)
    PageFaultCount             : 0x00002E4B
    PeakWorkingSetSize         : 0x00419000
    WorkingSetSize (Mem usage) : 0x0003A000 (232 ko)
    QuotaPeakPagedPoolUsage    : 0x00000000
    QuotaPagedPoolUsage        : 0x00000000
    QuotaPeakNonPagedPoolUsage : 0x00000000
    QuotaNonPagedPoolUsage     : 0x00000000
    PagefileUsage              : 0x00000000
    PeakPagefileUsage          : 0x00000000

Process ID: 764
smss.exe  (PID: 764)
    PageFaultCount             : 0x000000D6
    PeakWorkingSetSize         : 0x00082000
    WorkingSetSize (Mem usage) : 0x0006C000 (432 ko)
    QuotaPeakPagedPoolUsage    : 0x00006C34
    QuotaPagedPoolUsage        : 0x00001854
    QuotaPeakNonPagedPoolUsage : 0x000004D8
    QuotaNonPagedPoolUsage     : 0x00000280
    PagefileUsage              : 0x0002C000
    PeakPagefileUsage          : 0x00030000

Process ID: 816

Process ID: 844
winlogon.exe  (PID: 844)
    PageFaultCount             : 0x0000261D
    PeakWorkingSetSize         : 0x00B58000
    WorkingSetSize (Mem usage) : 0x0029B000 (2668 ko)
    QuotaPeakPagedPoolUsage    : 0x0001B054
    QuotaPagedPoolUsage        : 0x000185A4
    QuotaPeakNonPagedPoolUsage : 0x0000C988
    QuotaNonPagedPoolUsage     : 0x0000B6A0
    PagefileUsage              : 0x005EC000
    PeakPagefileUsage          : 0x006C6000

    PeakPagefileUsage          : 0x03277000

Process ID: 2712
lsproc.exe  (PID: 2712)
C:\Documents and Settings\LoginX\Bureau\lsproc.exe
    PageFaultCount             : 0x000000EC
    PeakWorkingSetSize         : 0x000F1000
    WorkingSetSize (Mem usage) : 0x000E4000 (912 ko)
    QuotaPeakPagedPoolUsage    : 0x000032B4
    QuotaPagedPoolUsage        : 0x000032B4
    QuotaPeakNonPagedPoolUsage : 0x00000400
    QuotaNonPagedPoolUsage     : 0x00000398
    PagefileUsage              : 0x00042000
    PeakPagefileUsage          : 0x0005C000
There are 131 drivers:
   1: ntkrnlpa.exe
   2: hal.dll
   4: BOOTVID.dll


 129: HTTP.sys
 130: hiber_WMILIB.SYS
 131: ntdll.dll

  • file not found, mister – Kiquenet Feb 13 '12 at 15:24

open windows command prompt

C:\>tasklist                       // list all the tasks

C:\>Taskkill /IM firefox.exe /F     // Kill task by name


C:\>Taskkill /PID 26356 /F           // kill task by PId

Hello if you want to list running process ID's on a Windows machine then open a cmd screen and type:

netstat -aon | more

use the Enter key to scroll.

  • That only gives processes that are accessing the network, which is NOT all processes. – dave_thompson_085 Jun 1 '18 at 6:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.