Checking Your Drive Read and Write Speeds on Windows — Honestly, it’s easier than you think
If you’ve ever been curious about how fast your SSD, external drive, or flash stick actually is, you probably realize it’s not always straightforward to find out. I’ve spent way too long trying to run simple benchmarks without immediately resorting to bulky third-party apps. And yeah, it turns out Windows has some built-in options that are kinda hidden or at least not super obvious at first. Once you know where to look, it’s quite manageable—though not perfect.
Using Windows Built-in Commands for Drive Performance
This is what finally worked for me: using the command line—specifically, Windows Terminal or PowerShell. It’s not the prettiest tool for benchmarks but it’s built-in and fast. Basically, you open the terminal as an administrator, run a command, and get an estimate of your drive’s sequential read and write speeds.
Before anything, double-check that your external drives are plugged into a decent port (USB 3.0, USB-C, whatever). Sometimes, even if the drive is connected, it runs slower because it’s in a low-speed port—like old USB 2.0 or a motherboard’s shared port. Connect it to the right port and make sure it’s mounted properly before testing.
Getting the Terminal Ready
You’ll need admin rights, so: Windows + X opens the quick menu. Here, select “Windows Terminal (Admin)” or “Command Prompt (Admin)”—whatever you see. If PowerShell isn’t there, you might have to update Windows or tweak a setting, but usually, it’s there.
Believe me, I’ve had to do this a couple of times, especially on older systems. Sometimes, the menu only shows the standard options. Also, on very old or tightly locked OEM systems (like some Asus or Dell machines), you might need to disable certain BIOS restrictions or enable “legacy support” — but that’s a separate story.
Running the Speed Test with winsat
Here’s where I got stuck initially—what command to run. Turns out, it’s winsat disk -seq -drive <drive letter>. Swap out <drive letter> with your target, like D: or E:. So, for checking drive D, run:
winsat disk -seq -drive DThis command kicks off a quick test of sequential read/write speeds. The Windows System Assessment Tool (winsat) estimates the MB/s speeds. The output looks kind of cluttered at first, but the key info is there. It will typically show the speed in MB/sec, which is how you tell whether your drive is performing up to spec or if it’s unexpectedly slow.
One thing I learned—be patient. The command doesn’t take forever, but on older hardware or busy systems, it can be slow to kick in. Also, note that using -seq tests sequential throughput. If you want an idea of random access speeds—like for typical use—you might look into other tools, but winsat only does basic estimates.
External Drives and Troubleshooting
If you’re testing an external drive, just plug it in before opening the terminal and running the command. Just ensure the drive is mounted properly. Also, verify in File Explorer what drive letter it has—sometimes, it’s not what you expect, especially with SD cards or multiple drives. Initially, I kept trying to check the wrong drive because I was looking at the wrong letter.
It took me a couple of tries because, frankly, the syntax is a little picky. Make sure you include the -drive parameter, and don’t forget to run as admin otherwise, the command might just give an error or do nothing meaningful. Also, if your results seem inconsistent, rebooting can help clear cached info or states.
Beyond Winsat — For More Detailed Benchmarks
Now, remember, winsat is a quick-and-dirty way. It’s useful for a rough idea, but if you’re troubleshooting performance issues or need precise data (like 4K random speeds, queue depths, etc.), then dedicated tools are better. CrystalDiskMark, ATTO Disk Benchmark, or AS SSD Benchmark—they give more nuanced info and can handle different test scenarios.
That said, in a pinch, this built-in method is surprisingly decent. It’s also nice not to clutter your system with third-party apps just to get basic data.
Heads Up & Caveats
Quick tip: sometimes, speed results can be skewed by background processes, antivirus scanning, indexing, or even drive encryption. I’ve seen my results fluctuate just because a huge Windows update was running in the background. Also, consider that your drive’s firmware, system load, or fragmentation might affect the numbers.
If it looks weird or inconsistent, try rebooting, closing background apps, and making sure the drive isn’t still indexing or being used for anything else.
Final thoughts — Why Bother With This?
Honestly, it’s nice knowing roughly how your drive stacks up without installing extra software. Plus, it’s fast and doesn’t require waiting for downloads. For quick checks, the winsat command is pretty handy if you run it as admin and remember to replace the drive letter.
Just keep in mind—it’s not perfect. Only gives sequential speeds, and results can vary depending on system load or drive state. But it’s enough for a quick sanity check before digging into deeper benchmarking.
Hope this helped — it took me way too long to figure out, so sharing this probably saves someone else from a few hours of frustration. Anyway, happy benchmarking!