Out of all the built-in troubleshooting tools in Windows, Task Manager is probably the most useful tool. Almost every end-user knows what to do when an application stalls. They just fire up Task Manager using Ctrl + Shift + Esc and end the nonresponsive task. Also, Task Manager can be an extremely valuable tool to troubleshoot processes, and monitor disk I/O rates or other system performance issues.
Task Manager’s Details tab lists all running processes. By default, it doesn’t display the complete path of the running processes and the command-line arguments used by those processes.
For instance, you may see the script host CScript.exe or WScript.exe in Task Manager but not the script file name (argument) being executed. This article tells you how to enable this critical bit of information in Task Manager.
Show Command Line and File path of Running Processes
To display the full file path and command-line of running processes in the Processes tab, in the Task Manager’s Processes tab, right-click the column header and enable Command line option.
Here it is:
Show Command-line column in Details tab
In Task Manager, click on the Details tab. Right-click the column header and click Select columns
Enable Command line and Image path name checkboxes and click OK.
Note that “Command line” field would show the image file path anyway. So, enabling the Command line column alone is sufficient.
The above instructions below apply to Task Manager in Windows 8, 10 and 11. The instructions also apply to the redesigned Task Manager in Windows 11 22H2.
Task Manager in earlier versions of Windows
Task Manager user interface appears a bit different in previous versions of Windows. For Windows Vista and 7, use these steps:
Launch Task Manager. From the View menu, click Select Columns… Scroll down the listing, select the following options and click OK.
- Image Path Name
- Command Line
(Fig 1: Task Manager showing Image Path Name and Command Line)
Note: You may also use Process Explorer or any other process viewer to see a running process’s path name and command line. You’d also like to read my earlier article titled What’s the suspicious Rundll32.exe process?
One small request: If you liked this post, please share this?One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
- Pin it!
- Share it to your favorite blog + Facebook, Reddit
- Tweet it!