I wasted years optimizing my SSD for nothing — Windows was already doing it

Many Windows users have tried relocating the pagefile, disabling Windows indexing, and relocating browser caches and TEMP folders to preserve their SSDs. What they don't realize is that most of these practices were born in the 2012 era of hardware anxiety.

Exploring Windows 11 features showed me that those practices are an absolute waste of time today. You don't need to keep third-party TRIM tools or micromanage your host writes (data written by the operating system). Even as you read this sentence, Windows is optimizing your drive; stepping back can actually help your system run more smoothly.

Windows was already doing it

The moment I stopped feeling clever about my SSD

Just a few weeks ago, I opened Defragment and Optimize Drives. I wasn't really troubleshooting anything in particular; I just needed to check on things. I occasionally do this with Task Manager too.

I was surprised to see that Windows had been optimizing my drives on a weekly schedule; the last optimization was just a day ago. The exact notification from the app was: "Drives are being analyzed on a scheduled cadence and optimized as needed." Out of curiosity, I checked a few other Windows devices I own, and the results were similar.

What I hadn't realized was that native TRIM support has existed since Windows 7. This wasn't some wondrous new Windows 11 feature. SSD optimization follows a weekly schedule on Windows 10 and 11, and Windows also performs reTRIM — additional TRIM passes to catch missed blocks.

TRIM is essential because after deleting files, your SSD marks the blocks as available but doesn't instantly clean them up. TRIM tells the SSD which blocks can be internally wiped; that way, the controller doesn't have to scramble to make space during a write operation.

Windows handles native TRIM support, weekly scheduled optimization passes, and reTRIM operations; your SSD controller manages wear leveling, garbage collection, and spare block allocation. This creates a complete maintenance picture between the SSD and the OS.

Once I realized that I was only duplicating the work already split between Windows and the drive, it was clear I had to leave these tasks to the system.

The advice wasn't wrong

It just never got updated

Over the years, I've seen a lot of experts talk about moving the pagefile from the SSD. Many recommend disabling Windows Search, reducing browser cache writes, and relocating TEMP folders. This all felt logical, like something you should do if you understand your hardware.

This advice made sense between 2009 and 2012, when consumer SSD capacities mainly ranged between 60GB and 120GB and came with low TBW (terabytes written) ratings of no more than 40TB. Endurance was a real concern because NAND was expensive and drives were small. The advice was a response to real hardware limitations.

Modern hardware outgrew this reasoning:

Budget drives today can handle 10 times as many writes as those early SSDs could. You'd generally need decades to exhaust the headroom at typical daily write rates. Your PC will most likely be replaced before your SSD fails.

Some tweaks aged badly

I was trading real performance for imaginary protection

I didn't expect some of the tweaks I always used would start working against me. An example is the pagefile. Logically, moving it off the SSD should reduce writes. However, this only means virtual memory is routed through a mechanical hard drive. You end up forcing NVMe-level speed reads and writes to depend on a drive that can't match the speed. Manual intervention with the pagefile hasn't been necessary since Vista, when Windows started managing it automatically.

Another example is search indexing. Here again, we assume constant writes are wearing out our SSDs, but the write-heavy stage only happens once when the system initially builds the index. Afterward, ongoing maintenance is very light. If you disable indexing, your Start menu searches and File Explorer queries become live, unindexed scans. If you have a large file library on your device, the difference is instantly noticeable.

The pattern is consistent for TEMP folders and browser caches. Once moved, you slow down application installs, browser sessions, and update processes. You've only succeeded in moving the writes to a slower drive; they don't actually disappear. By carrying out these tweaks, my workflow became considerably slower without the drive benefiting from it.

My entire SSD routine takes about five minutes a year

My maintenance routine has been significantly simplified since I dropped most of these habits. It no longer requires scheduled tools, third-party optimizers, or manual TRIM triggers. I simply pay attention to three things.

The first is free space. I like to keep 10–15% of my drive free because the SSD controller needs headroom. This one habit directly influences the controller's efficiency.

The second is SMART (Self-Monitoring, Analysis, and Reporting Technology) health. I still open CrystalDiskInfo a few times every year because it shows remaining write estimates, total host writes, and drive temperature. The attributes you see may not be identical across all drives.

The last is firmware updates. The real-world impact of a single firmware update from an SSD manufacturer is greater than years of manual optimization. That's my new routine, and it has taken the place of babying my SSD with tweaks and TRIM tools.