HowTo/ListProcessesInWindows

From S23Wiki
Jump to: navigation, search

Use the command "tasklist" on the normal command line (cmd.exe)

Syntax

  • tasklist[.exe] [/s computer] [/u domainuser [/p password]] [/fo {TABLE|LIST|CSV}] [/nh] [/fi FilterName [/fi FilterName2 [ ... ]]] [/m [ModuleName] | /svc | /v]


/s Computer : Specifies the name or IP address of a remote computer (do not use backslashes). The default is the local computer.

/u DomainUser : Runs the command with the account permissions of the user specified by User or DomainUser. The default is the permissions of the current logged on user on the computer issuing the command.

/p Password : Specifies the password of the user account that is specified in the /u parameter.

/fo {TABLE|LIST|CSV} : Specifies the format to use for the output. Valid values are TABLE, LIST, and CSV. The default format for output is TABLE.

/nh : Suppresses column headers in the output. Valid when the /fo parameter is set to TABLE or CSV.

/fi FilterName : Specifies the types of process(es) to include in or exclude from the query. The following table lists valid filter names, operators, and values.



OR



In Windows XP go to StartMenu , and Run... "wmic" a new type of console prompt will show up, (not the regular cmd.exe),which looks like this:

wmic:rootcli>

on this prompt type "process" and you will get a list of all running processes ,but unlike in regular Task Manager, you get FULL pathes to the actual .exe files, which is very useful, (and actually should be like this in normal TaskMan anyways..!)

You can do a LOT more with [WmIc WMIC]...


does win2k have this aswell? -KunDa

"Do you know any tricks for installing the Microsoft Windows Management Instrumentation Command-line (WMIC) tool on Windows 2000 computers?

I'm unaware of any such tricks. My understanding is that WMIC has a dependency on components that aren't available in Win2K. You can certainly use WMIC to manage any WMI-enabled computerùyou just need to run it from Windows Serve . . . "

from: http://www.winnetmag.com/WindowsScripting/Article/ArticleID/40520/40520.html



Want to KILL one of the processes now? --> HowTo/KillProcessesInWindows