Timeline for Show EXE file path of running processes on the command-line in Windows
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2017 at 14:33 | comment | added | Jeroen Wiert Pluimers |
@JaredBeach it's the cmd.exe escape character; see stackoverflow.com/questions/20342828/… In this case, it ensures that the pipe is for PowerShell, not cmd.
|
|
| Nov 21, 2017 at 14:54 | comment | added | Jared Beach | What does the carrot do in the first command? | |
| May 14, 2017 at 5:21 | comment | added | barlop | @jpmc26 the file paths that the wmic command outputs, are the same as the file paths that the powershell ........ command there outputs e.g. open windows calculator and try it for calc.exe pastebin.com/raw/TK8xSPPL | |
| May 12, 2017 at 14:03 | comment | added | Jeroen Wiert Pluimers |
@jpmc26 I didn't need those, but I think you can get them via StartInfo instead of Path based on stackoverflow.com/questions/1012409/…
|
|
| May 10, 2017 at 16:34 | comment | added | jpmc26 |
Is Path the same thing as command line? What about the arguments to the executable? @barlop WMI still has a number of features that are otherwise unavailable in PowerShell.
|
|
| Jun 23, 2014 at 8:31 | vote | accept | Jeroen Wiert Pluimers | ||
| Jun 15, 2014 at 8:13 | comment | added | barlop | there is WMIC too but powershell is more modern and flexible | |
| Jun 15, 2014 at 8:12 | history | answered | Jeroen Wiert Pluimers | CC BY-SA 3.0 |