Tired of clunky Windows monitoring? A Senior DevOps Engineer shares how to bring the power of Linux’s htop to your PowerShell terminal with pstop, ditching clumsy Get-Process loops for good.

htop for Windows? You Bet. Taming Your Servers with PowerShell and pstop

I still remember the 3 AM alert. It was a classic: CPU utilization on prod-db-01, our primary SQL server, was pegged at 100%. RDP was crawling, barely usable. I finally got a PowerShell remote session open, and what did I have? A blinking cursor. I typed Get-Process | Sort-Object CPU -Descending, waited, and got a static snapshot of what was hammering the box at that exact second. To see it again, I had to press the up arrow and hit enter. And again. And again. It felt like trying to fix a running engine by taking a polaroid of it every 30 seconds. In that moment, I’d have given anything for the simple, beautiful, real-time clarity of running htop on a Linux box.

The Root of the Pain: Snapshots vs. Streams

Let’s be clear: PowerShell is incredibly powerful. The problem isn’t that it’s incapable. The problem is a difference in philosophy. Native PowerShell cmdlets like Get-Process are designed to grab data, turn it into an object, and pass it down the pipeline. They give you a perfect, high-fidelity snapshot in time. This is fantastic for scripting and automation.

However, when you’re troubleshooting a live performance issue, you don’t want a snapshot. You want a live stream. You need to see which process is spiking right now, how memory usage is fluctuating, and which service is suddenly spawning a dozen child processes. The default tools force you into clumsy loops that are slow, flicker like crazy, and are a pain to type when you’re under pressure.

Three Ways to Un-Blind Yourself on Windows

Over the years, we’ve developed a few ways to deal with this. Here’s the breakdown, from the quick-and-dirty to the truly elegant solution.

Solution 1: The Old-School PowerShell Loop (The ‘Good Enough’ Fix)

This is the trick every Windows admin learns eventually. You wrap the command you want to run in a while($true) loop, clear the screen on each iteration, and pause for a second. It’s ugly, but it works in a pinch on any server with PowerShell, no extra tools required.

while ($true) {
    Clear-Host
    Get-Process | Sort-Object CPU -Descending | Select-Object -First 15 | Format-Table
    Start-Sleep -Seconds 2
}

The Catch: This is a hack. The screen flickers, it chews up a surprising amount of CPU on its own, and it isn’t interactive. You can’t easily scroll, kill a process, or sort by a different column without stopping the script and rewriting it. It’s a blunt instrument.

Solution 2: The Real Deal – Installing pstop (The ‘Right’ Fix)

This is what we’ve been waiting for. A developer by the name of Michael T. Lombardi created a module called pstop, and it’s a game-changer. It’s a proper, real-time, interactive Text-based User Interface (TUI) for processes, built right inside PowerShell. It’s our htop.

First, you need to install it from the PowerShell Gallery. You only need to do this once.

Install-Module -Name pstop -Scope CurrentUser

Pro Tip: If you get an error about execution policies, you might need to allow scripts for your current session. You can do this safely by running: Set-ExecutionPolicy RemoteSigned -Scope Process. This change only lasts as long as your PowerShell window is open.

Once installed, just run the command:

Show-Process

And what you get is pure magic. A full-screen, color-coded, continuously updating view of your processes. You can sort by CPU, memory, or any other column by pressing a key. You can select a process and kill it (F8) right from the interface. No flicker, no clumsy loops. Just clean, actionable data.

Solution 3: The GUI Heavy Hitter (The ‘Sysinternals’ Option)

I have to mention the granddaddy of all Windows process tools: Process Explorer (procexp.exe) from the Sysinternals Suite. If you have an RDP session, this is arguably the most powerful process analysis tool on the planet. You can see DLL dependencies, handle counts, thread activity—everything.

The Catch: It requires a GUI. For modern DevOps and cloud infrastructure, we’re often living in remote PowerShell sessions, SSH, or other command-line interfaces. Spinning up an RDP session just to see what’s eating CPU is slow and often not an option on tightly secured servers like Core installations. Process Explorer is a surgeon’s scalpel for deep forensics; pstop is the paramedic’s multi-tool for fast, effective triage.

My Take: Just Install pstop. Everywhere.

Look, if you’re a DevOps engineer, SRE, or sysadmin managing Windows servers, do yourself a favor. The next time you provision a new server or build a new base image, make Install-Module pstop part of your standard setup script. The first time you’re chasing down a rogue w3wp.exe process at 2 AM, you’ll thank me. It bridges a critical gap in the Windows command-line toolkit and brings a little of that Linux terminal zen to our world.

Stay sharp.

– Darian

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions