Windows calls its scheduled drive task Optimise Drives, which sounds like the old hard-drive defragmenter. For an SSD, the routine sends retrim information and can perform maintenance suited to the file system and drive. Leave the schedule enabled unless you are diagnosing a documented problem.

Quick Answer

Open Defragment and Optimise Drives, confirm Windows identifies the SSD as a solid-state drive and keep scheduled optimisation on. Use Analyse or Optimise for a manual maintenance pass after a migration if needed. Do not install a tool that repeatedly defragments every file on the SSD.

Browse Evetech's SSD catalogue and popular solid-state drives when capacity or health calls for replacement. Windows maintenance cannot repair worn NAND or a failing controller.

What TRIM Communicates

Deleting a file changes the file-system record, but the SSD also needs to know which logical blocks no longer hold useful data. TRIM, or the equivalent deallocation command on the storage path, gives the controller that information. It can prepare blocks for later writes during its own garbage collection.

The command does not wipe every deleted byte at the moment you empty the Recycle Bin. Timing and secure-erasure behaviour depend on the controller, firmware and storage stack.

Why the Old Advice Is Too Simple

An SSD has no mechanical head that benefits from putting a file's pieces next to each other, so routine manual defragmentation brings no hard-drive seek advantage. Windows still manages file-system needs and can perform operations beyond one retrim under some conditions.

That is why disabling the built-in schedule based on the word defragment is a poor fix. Let the current Windows storage service choose the maintenance for the detected media. Investigate only if the drive is misidentified or the scheduled task reports errors.

Check the Result

Confirm the media type, last run and current status in the Optimise Drives window. Keep backups separate from maintenance; a successful optimisation does not prove the SSD is healthy.

If performance has fallen, check free space, SMART warnings, temperature, interface speed and background work. Retrim cannot compensate for a nearly full cache, thermal throttling or a slow enclosure.

Let the Schedule Fit the Drive

The default weekly cadence is a reasonable maintenance trigger, not a demand that you run the task by hand every seven days. Windows can skip or reschedule work around normal use. A laptop that was asleep at the scheduled time does not need a third-party catch-up utility.

After restoring an image or cloning a large drive, one manual Optimise pass can notify the new SSD about unused ranges. Confirm backups and file-system health first. The operation is maintenance, not a substitute for verifying the migration.

FAQ

Does Windows run a classic full defrag on an SSD every week?

It uses media-aware maintenance, including retrim. Windows can perform other file-system work when required, so the one-word label is incomplete.

Should I turn scheduled optimisation off?

Leave it enabled for a normal Windows installation unless vendor or support guidance identifies a specific issue.

Does TRIM securely erase deleted files?

No guarantee. Deallocation and secure sanitisation are different processes.

Confirm Windows detects the SSD correctly, leave media-aware optimisation scheduled and diagnose health, heat and free space when performance still falls.