Page MenuHomePhorge

PowerShell
Updated 104 Days AgoPublic

PowerShell is a hilariously verbose command environment, both in terms of every damn command and also in terms of what it spits out at you when something is wrong---at least, at the times where it doesn't just refuse to say anything at all. Unhelpfully verbose or unhelpfully taciturn seem to be its only two modes! However, PowerShell is necessary in many scenarios thanks to being more featureful and modern than Windows' vestigial cmd.exe environment.

So here are some important things, presuming you already know how to use normal shells on #Linux or such. And if you don't, stop reading this and learn to be comfortable there first; it's a much less user-hostile place to be, far fewer lines of red error text suddenly thrust upon you. Seriously, it's generally far less of a hassle even on Windows to just use the Windows Subsystem for Linux! (You can even pipe to it, ex dir | wsl grep -i SomeFilenameIAmLookingFor.)

Running normal commands with quoted command or argument paths

When using quoted arguments or even just commands, PowerShell goes "oh hey strings" because fucking everything's an object in PowerShell and so suddenly it's thinking you're trying to do string operations when you're just trying to run a damn command with a space in it or something.

The trick is to prepend & to the start of the command. Ex.

& "C:\path\to\someplace some asshole put space\something.exe" "D:\Silly Path\"

Basic Equivalents

Posix-y commandPowerShell equivalentDocumentationNotes
catGet-Contentss64, Microsoft
grepSelect-String -Patternss64, Microsoft
head / tailit's complicatedsee below
lsls / dir / Get-ChildItemss64, MicrosoftActs like ls -l, no easy equiv of just ls
pushdpushd / Push-Locationss64Works in DOS too, less annoying than cd there in fact since it'll traverse filesystem boundaries
tail -fGet-Content -WaitEasily chokes on bad characters and if it does so it actually won't wait, so in practice often just doesn't work
topsee belowsee belowsee below
treetree /FMicrosofttree looks fine on screen, but attempts to grep or FindStr fill the output with ????s. By default only prints folders, print files too with /F. This is a basic EXE, it is NOT an alias for a PowerShell equivalent.
unzipExpand-Archivess64, Microsoft
wgetInvoke-WebRequestss64, MicrosoftIn fact running wget will already get you Invoke-WebRequest, which saves the content to an object in memory rather than defaulting to file output like wget does, making this a surprising alias. You'll need to run, say, wget url://etc -OutFile filename.exe.

Alternatives and complexities

head and tail

You can use Get-Content -Last 10 / Get-Content -First 10 (documentation: ss64, Microsoft) but only for text files.

Things in PowerShell tend to be objects, which is cool I guess but makes everything more awkward too. So for example for ls -ltr | tail you'll have to do something like Get-ChildItem '..\path\' | Sort-Object -Property LastWriteTime | Select-Object -Last 10.

top

You almost just have to grab some equivalent compiled for Windows (for example bottom aka btm is a nice cross-platform atop-like program). Install with winget install Clement.bottom.

The best you can really do natively in PowerShell is crazy one-liners like for example:

While(1) {  $p = get-counter '\Process(*)\% Processor Time'; cls; $p.CounterSamples | sort -des CookedValue | select -f 15 | ft -a}

less and cat

For a nicer equivalent of the less and cat commands, bat aka batcat is the way to go. winget install sharkdp.bat.

Environment variables

Access normal environment variables with $env:VARIABLENAME, ie. instead of %USERPROFILE% for Windows' equivalent of $HOME it's $env:USERPROFILE. Contain in curly braces to avoid ambiguity in parsing, ex. ${env:USERPROFILE}.

Examples

# Get the current state of scheduled tasks with the string "T401" in their name
schtasks | Select-String -Pattern "T401"
# See if anything with "notepad" in the executable name are running
tasklist | Select-String -Pattern "notepad"

# Get all the version info on all the EXEs in the local directory
Get-ChildItem "*.exe" | % {$_.VersionInfo} | Select *
# Get only some info
Get-ChildItem "*.exe" | % {$_.VersionInfo} | Select OriginalFilename,FileVersionRaw

External links for other problems

Last Author
keithzg
Last Edited
Mar 8 2024, 4:51 PM

Event Timeline

keithzg edited the content of this document. (Show Details)
keithzg published a new version of this document.
keithzg edited the content of this document. (Show Details)
keithzg edited the content of this document. (Show Details)