Windows 10 & 11 SSD Optimization: Why You Should Keep TRIM and Scheduled Retrim Enabled

On the surface, the logic feels bulletproof. The utility is literally named Defragment and Optimize Drives, and the underlying command-line tool is still called defrag. For over a decade, conventional wisdom has dictated that defragmenting an SSD is a cardinal sin—an exercise that shuffles flash blocks around for zero performance gain while burning through your drive’s finite write endurance.

As Rob LeFebvre at MakeUseOf points out, however, turning off Windows’ scheduled optimization in Windows 10 or Windows 11 doesn't save your SSD. Instead, it disables the exact background maintenance your flash storage relies on to stay fast: scheduled retrim passes and storage-aware housekeeping. When we cross-reference this advice with Microsoft’s official Windows Server and Windows 11 command documentation, the truth becomes clear: Windows hasn't treated SSDs like spinning hard drives in a very long time, and trying to outsmart the operating system's storage stack is a prime example of solving a 2009 problem by creating a modern one.

The Ghost of Windows 7 and the Misleading Name​

Why does this myth refuse to die? Part of the blame rests squarely on Microsoft’s naming conventions. When users search defrag on the taskbar and see Defragment and Optimize Drives, their muscle memory kicks in. Traditional defragmentation was engineered for mechanical hard disk drives (HDDs), where physical read/write heads had to swing across spinning magnetic platters. Consolidating scattered file fragments into contiguous tracks meant the drive head moved less, dramatically improving read speeds.

An SSD has no moving parts. It reads data scattered across disparate NAND flash cells just as quickly as it reads contiguous blocks. Shuffling data on an SSD purely to make files contiguous only generates unnecessary write amplification.

According to MakeUseOf, the habit of manually disabling the scheduler dates back to the Windows 7 era. Even after Microsoft updated Windows in 2009 to treat SSDs differently, some early solid-state drives failed to properly identify themselves to the operating system as non-rotational media, prompting skeptical enthusiasts to turn off scheduled defragmentation entirely just to be safe. Today, modern SATA and NVMe drives report their media type clearly, and Windows routes them to a completely different optimization pipeline.

• Section Summary: The fear of scheduled optimization stems from outdated Windows 7-era hardware quirks and the fact that Microsoft still uses "Defragment" in the tool's title. In Windows 10 and 11, the operating system automatically detects solid-state media and changes what the "Optimize" button actually does.

What "Optimize" Actually Does on an SSD: TRIM vs. Retrim​

When Windows optimizes a modern SSD, its primary job isn't moving files—it is managing empty space via TRIM (known in Microsoft’s file system documentation as delete notifications or unmap).

Because of how NAND flash memory is structured, an SSD can write to an empty page directly, but it cannot overwrite existing data in place. It must first erase a larger block of pages before writing new data. When you delete a file in Windows, the file system marks that space as free in its own records, but without TRIM, the SSD controller doesn't know those blocks are actually stale until you try to write to them again.

Microsoft’s fsutil behavior documentation explains that delete notifications inform the underlying storage device of clusters freed during file deletion so the drive can clear them ahead of time. While Windows sends real-time TRIM commands whenever you delete files on an NTFS volume, MakeUseOf notes that those individual TRIM requests are merely hints—if the drive's command queue is saturated during heavy workloads, or if a driver update interrupts normal handling, those real-time notifications can get dropped.

That is where scheduled optimization steps in. Microsoft’s PowerShell documentation for the Optimize-Volume cmdlet explicitly lays out how Windows handles different media types when triggered without special overrides:

Instead of shuffling files, Windows runs a retrim. As defined in Microsoft Learn’s Optimize-Volume reference, a retrim scans the volume and generates fresh TRIM and Unmap hints for every currently unused sector on the drive. It acts as a safety net that catches any delete notifications the SSD missed during normal daily use.

Wait—Does Windows Ever Defragment an SSD?​

Here is the plot twist that catches even seasoned IT administrators off guard: Yes, Windows occasionally runs a traditional defragmentation pass on an SSD, provided scheduled optimization is enabled.

Before you reach for the power cord, look at what Microsoft’s official defrag command documentation actually specifies for the scheduled maintenance task:

1. The General Task Runs Weekly: The scheduled maintenance task typically checks in once a week.
2. The SSD Policy Runs Monthly: For SSDs, Microsoft states that "traditional optimization processes"—which include moving files to make them reasonably contiguous alongside a retrim—are performed once per month.
3. Changing the Schedule Doesn't Override the Monthly Limit: Even if an administrator changes the Optimize Drives task frequency to run daily, Microsoft’s policy documentation notes that this does not change the once-per-month cadence for traditional SSD optimization.
4. Manual Runs Reset the Clock: If you manually force a traditional defragmentation on an SSD between scheduled runs, the next scheduled run will perform analysis and retrim, but will skip traditional defragmentation on that drive.

Why would Windows ever bother consolidating file fragments on flash storage? MakeUseOf points to file system bookkeeping and volume snapshots (Volume Shadow Copy / System Restore). And while Microsoft’s defrag command page doesn't spell out the internal NTFS engineering rationale directly, Microsoft’s fsutil behavior documentation confirms a critical architectural fact under its disablefilemetadataoptimization parameter: NTFS has a strict limit on how many extents (fragments) a given file can have. If a file becomes excessively fragmented beyond what the Master File Table (MFT) record and its attribute lists can track, the file system can literally fail to extend the file.

What about the wear and tear from that once-a-month cleanup? It is a rounding error. To use the mathematical illustration cited by MakeUseOf: a 1TB Samsung 990 PRO carries a warranty endurance rating of 600 Terabytes Written (TBW). Even if a monthly optimization pass were to rewrite 5 GB of heavily fragmented metadata and files, that would equal 60 GB of writes per year—roughly 0.01% of a 600 TBW endurance rating. You are burning orders of magnitude more writes scrolling through a media-heavy web browser or downloading a single modern game patch.

• Section Summary: Windows defaults to Retrim for TRIM-capable SSDs, clearing out stale blocks without moving valid data. Once a month, the scheduled task also performs a light traditional optimization pass to keep file fragmentation within healthy NTFS limits—a process that uses a negligible fraction of a modern drive's write endurance.

How to Verify and Fix Your SSD Optimization Settings​

Checking whether a third-party "optimizer" utility—or your own past tweaking—has disabled your SSD maintenance takes less than sixty seconds. Here is the complete, verified procedure for Windows 10 and Windows 11.

Step 1: Check the Scheduled Task in Optimize Drives​

1. Click the Windows Search bar on your taskbar, type defrag, and select Defragment and Optimize Drives.
2. Look at the Media type column next to your C: drive (and any secondary flash drives). Confirm that Windows properly identifies the drive as Solid state drive.
3. Look at the bottom section labeled Scheduled optimization. If it says Off, click Change settings.
4. Check the box for Run on a schedule (recommended) and set the Frequency to Weekly. Click Choose next to Drives to ensure your SSDs are selected, then click OK.

(Note from Microsoft’s documentation: Don't panic if the "Last run" timestamp in this window looks up to a month old or shows a drive wasn't recently processed. The scheduled task intentionally skips runs if a laptop is running on battery power, won't wake a sleeping PC to run, and won't update the "Last run" time if analysis was skipped.)

Step 2: Verify That Windows File-Delete Notifications (TRIM) Are Enabled​

Even with the scheduler on, you should ensure that real-time NTFS delete notifications haven't been disabled in the registry.

1. Right-click the Start button and select Terminal (Admin), PowerShell (Admin), or Command Prompt (Admin).
2. Run the following command:
   fsutil behavior query DisableDeleteNotify
3. Inspect the output. Microsoft’s fsutil tool reports status per file system (NTFS and ReFS), and the parameter uses a double-negative name:
   • NTFS DisableDeleteNotify = 0 means delete notifications (TRIM) are enabled (this is the default and what you want).
   • NTFS DisableDeleteNotify = 1 means delete notifications are disabled.
4. If your NTFS result returned 1, re-enable TRIM immediately by running:
   fsutil behavior set disabledeletenotify NTFS 0
   Per Microsoft Learn, this change takes effect immediately on the next unmap command and does not require a system reboot or service restart.

Step 3: Trigger a Manual Retrim (Optional)​

If your scheduled optimization has been turned off for months, you don't need to wait for the weekly maintenance window to clean up dropped TRIM hints. You can force an immediate, safe retrim from your elevated terminal:

• Using PowerShell (Recommended):
  Optimize-Volume -DriveLetter C -ReTrim -Verbose
  (Replace C with the drive letter of your target SSD.)
• Using Command Prompt:
  defrag C: /L /U /V
  (In Microsoft’s defrag syntax, /L explicitly performs a retrim on the specified volume, while /U and /V print progress and verbose statistics to your screen.)

What Actually Protects Your SSD in 2026?​

If disabling Optimize Drives is a bust, what should Windows users actually do to keep an NVMe or SATA SSD healthy?

First, ditch aggressive third-party defragmenters that ignore media types and force full HDD-style consolidation passes on flash storage. Windows’ native storage stack already knows how to differentiate an HDD, an SSD, and a thinly provisioned virtual disk.

Second, watch your free capacity. Both Microsoft’s documentation and hardware reality agree that running a drive right up to the red line degrades performance. MakeUseOf notes that crowding an SSD reduces the space available for dynamic SLC write caching, causing sustained write speeds to plummet. Furthermore, Microsoft’s defrag documentation explicitly notes that a volume needs at least 15% free space to serve as a sorting area whenever file fragments do need to be consolidated.

Leave Defragment and Optimize Drives on its default schedule, keep DisableDeleteNotify set to 0, leave 15% to 20% of your drive's capacity breathing room, and let the Windows storage engine handle the boring maintenance in the background. Your SSD was built to be used—not micromanaged like a fragile relic from 2009.