These 5 Windows Tweaks Fixed My Slow SSD Without New Hardware

When a Windows PC starts feeling sluggish, storage is usually the first suspect. Apps take longer to launch, file copies drag on, and the system feels less responsive overall. It is easy to assume the SSD is wearing out and start planning a replacement.
That assumption is often wrong.
After seeing the same symptoms on my own system, I expected the drive to be the problem. SMART data looked fine, but performance still felt off. What actually fixed the issue were a handful of Windows-level checks and settings that quietly drift out of place over time. No reinstall. No new hardware. Just correcting things Windows relies on to keep SSDs fast.
Here is a structured checklist that explains what to look for and why each step matters.
TRIM status is the first thing to verify
TRIM is fundamental to SSD performance. When files are deleted, the data is not immediately erased. Without TRIM, the SSD does not know which blocks are free, so it has to clean them up during future writes. That extra work slows everything down, especially over time.
TRIM can become disabled after cloning a drive, restoring an old system image, switching storage controllers, or upgrading from older Windows installs.
Checking it takes seconds:
-
Open Command Prompt as administrator
-
Run:
-
A result of 0 means TRIM is enabled
-
A result of 1 means TRIM is disabled
If it is disabled, re-enable it with:
There is no reboot required. On systems where TRIM had been off for a while, performance improvements can be immediate because the SSD no longer has to clean blocks on demand.
SSD firmware controls more than most people realize
Firmware governs how an SSD handles garbage collection, caching, wear leveling, and error handling. Windows does not manage this layer, and it does not warn you when firmware is outdated.
Outdated firmware can cause subtle slowdowns or odd behavior after Windows updates, especially on NVMe drives. In some cases, vendors quietly fix performance regressions or compatibility issues through firmware updates.
The process is straightforward:
-
Use a tool like CrystalDiskInfo to identify the current firmware version
-
Compare it with the latest version offered by the manufacturer
-
Use the vendor’s official utility to update, after making a backup
Firmware updates are not frequent, but skipping them for years can leave performance on the table.
Free space still matters on SSDs
SSDs need empty space to work efficiently. When a drive gets too full, the controller loses flexibility and write performance drops quickly.
As a general rule, keeping 15–20% of the drive free gives the controller enough room to manage data efficiently. This matters even more on smaller SSDs that fill up easily.
If the drive is nearly full:
-
Uninstall unused applications
-
Clear large downloads and temporary files
-
Move archives and media off the system drive
Some SSD tools allow manual overprovisioning, but simply leaving space unused achieves a similar effect.
Write caching should usually stay enabled
Write caching allows Windows to batch small writes instead of forcing the SSD to commit every operation immediately. If it is disabled, installs, file copies, and background tasks can feel noticeably slower.
Windows can disable write caching after certain errors or driver changes without drawing attention to it.
To check:
-
Open Device Manager
-
Expand Disk drives
-
Right-click the SSD and open Properties
-
Under Policies, make sure Enable write caching on the device is checked
On laptops and desktops with stable power, this setting should almost always remain enabled.
Sometimes the SSD isn’t slow — it’s just busy
A healthy SSD can feel sluggish if something is constantly accessing it. Cloud sync tools, antivirus scans, indexing, backups, and Windows Update can all keep disk usage high in the background.
Task Manager gives a quick overview, but Resource Monitor is more useful for pinpointing which processes are actually hitting the disk. Watching sustained disk activity instead of short spikes makes it easier to tell whether the drive is struggling or just occupied.
In many cases, the fix is adjusting schedules, excluding folders from indexing, or simply waiting for background jobs to finish.
Why this matters before replacing hardware
SSDs do wear out eventually, but most sudden slowdowns are not caused by failing NAND. They are caused by Windows losing track of how the drive should be managed, especially on systems that have been upgraded, cloned, or reused over time.
Before spending money on a replacement drive or reinstalling Windows, this checklist is worth running through. Each step targets a specific performance bottleneck and takes only minutes to verify.
In my case, correcting Windows settings restored responsiveness without touching the hardware. The SSD was fine. Windows just needed a little cleanup.
People should not have to do these sorts of things!
Use cassettes, a more reliable medium.
I bless the day I decided to switch to MacOS.
Is this article written for IT professionals?
How to access TRIM? How to update SSD firmware?
Background indexing? Write-caching settings? Power management policies?
I ran the command to set it to 0, and the result said it was 0 (Disabled). I then ran the command to check the value, and again it said 0 (Disabled). So why does it say Disabled if it’s Enabled?
(This is the 3rd time I’ve put this comment in. Hopefully it will show up this time (using a different browser now).)
What command?
It’s been awhile. I assume I did:
Set: fsutil behavior set DisableDeleteNotify 0
Check: fsutil behavior query DisableDeleteNotify
I did the command to set it to 0; it said it was at 0 (Disabled). I then ran the command to check the value and got the same result. So if 0 means Enabled, why does it say Disabled?
Good question,
In Windows, the command
fsutil behavior query DisableDeleteNotify
reports whether the disable flag is set, not whether TRIM itself is on.
DisableDeleteNotify = 0 ? TRIM is enabled
DisableDeleteNotify = 1 ? TRIM is disabled
So when you see 0, Windows is saying “TRIM is not disabled”, which effectively means it’s active. Some tools or UI labels shorten this to “Disabled,” referring to the disable flag, not TRIM itself – which is what causes the confusion.
If the value stays at 0 after setting it, TRIM is already working as intended and there’s nothing more you need to do.
When you write an article, do not assume that the reader knows what you know. Even techies do not know everything.
PLEASE … have a look at some of Martin’s articles. He includes the steps to implement the required changes.
Thanks, Arthur K, I appreciate it.