Modern NVMe SSDs are incredibly fast, but their endurance still depends on one thing: how much data gets written to them over time. Windows likes to quietly perform a lot of write-heavy tasks in the background, and if you don’t rein them in, they can easily rack up terabytes of unnecessary writes over the span of years. After adjusting a handful of settings related to memory management, indexing, caching, and restore points, the write pressure on my OS drive fell dramatically, to the point where it's enough to meaningfully extend its expected lifespan.
Adjusting the pagefile
One of the most write-intensive parts of your OS
When it comes to write-intensive components of the OS, the Windows pagefile and how it behaves is a big factor in SSD longevity, and it depends heavily on your configuration. By default, Windows manages it dynamically, expanding and shrinking its size in response to memory pressure. This resizing process creates a steady flow of background writes you’ll never see, but especially on systems with lots of RAM or workloads that spike memory usage, these background writes can add up quickly.
Setting the pagefile to a smaller, fixed size eliminates the constant resizing and stabilizes how much Windows writes to it. Moving the entire pagefile to a second SSD has an even greater effect. Many people have a secondary SATA drive or older NVMe that isn’t as valuable as the primary system drive, and relocating the pagefile shifts the majority of this quiet write load somewhere far less important. Disabling the pagefile entirely removes the write load altogether, although it comes with stability risks that make it a poor choice for most users. The sweet spot is almost always a small, fixed-size pagefile on a secondary drive, usually kept to around 4 GB at the minimum, and 8 GB at the max.
5 SSD myths that are simply untrue
Don't fall for these common SSD misunderstandings.
Disabling hibernation
Responsible for a large amount of writes
Hibernation is one of the biggest write generators in Windows because the process involves storing whatever is in your RAM directly onto the SSD in a file called hiberfil.sys. That file is roughly the size of your installed memory, and every time you hibernate, Windows rewrites the entire thing. The math becomes ridiculous very quickly. A system with 16GB of RAM that hibernates five times a day is writing up to 80GB daily. Over a month, that’s more than 2TB. With 32GB or 64GB of RAM, the numbers get even scarier.
Disabling hibernation removes this entire category of sequential writes and instantly reduces the write pressure on your system drive. If you rarely use hibernate, or if you simply prefer sleep mode, this single change can have the biggest impact of everything in this article. To disable it, open a Command Prompt as Administrator and type the following command: powercfg.exe /hibernate off
5 mistakes to avoid before you decide to buy a new SSD
Choosing the right SSD isn’t just about speed. Avoid these 5 costly mistakes to ensure performance, longevity, and value for money.
Turning off indexing for specific folders
Not required
Windows Search Indexing continuously scans files and updates metadata in the background. It makes sense for documents and emails, but it’s wasted effort on constantly changing files like game libraries, VM disks, shader caches, temporary folders, and software build directories. These locations change too frequently for indexing to be helpful, and all the indexing system does is create extra writes for no real benefit.
You can disable indexing on a per-folder or per-drive basis, which is perfect for scratch disks, large downloads folders, or game directories. On machines with massive Steam or Epic libraries, this cuts down background write activity noticeably. If you work with Linux VMs, development containers, or render caches, the reduction is even more dramatic.
5 window managers that make multitasking easier on Windows
You don't have to settle for Snap Layout
System Restore size tweaks
Useful, but write heavy
System Restore is useful, but it’s also a write-heavy feature. Every restore point is effectively a snapshot of critical system files and registry states, and over time these snapshots can grow significantly. Windows will keep making new ones until it hits the space limit, and depending on how large that limit is, the write volume can be substantial.
Lowering the maximum size immediately reduces how much restore data Windows writes. If you already use a backup solution like Macrium, Veeam, File History, or a NAS-based snapshot system, you can disable System Restore entirely. Offloading system recovery to a proper backup system dramatically lowers write churn, especially for users who install a lot of software or make frequent system changes.
Why my NAS backups failed, and what I wish I’d noticed sooner
How small oversights nearly erased months of data
Windows is pretty friendly to SSDs, but you can make it even better
Drives are lasting longer than ever, but Windows still has a habit of throwing unnecessary write loads at them. By controlling the worst offenders, you preserve your SSD and can increase its usable lifespan significantly. The best defense against SSD failure, though, is maintaining best practices when it comes to your own write-heavy activities.
