Email:

Phone No.

Whatsapp

Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months

  • Home
  • Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months
https://open.spotify.com/show/3Gmj15x6cGrgJEzmGnDTTj

Windows 10 Defrag TRIM Bug Still Not Fixed After Six Months

After the release of two Windows 10 feature updates and numerous cumulative updates, Microsoft has still not fixed a bug causing Windows Defrag to TRIM non-SSD drives.

In May 2020, Microsoft released Windows 10 2004, the May 2020 Update, and introduced two bugs causing SSD drives to be defragged too often and for the TRIM operation to be attempted on non-SSD drives.

The first bug prevented the Windows 10 Automatic Maintenance feature from remembering when a drive was last optimized when the operating system was restarted. The forgetting of the previous optimization date would cause drives, including SSD drives, to be defragged on every computer reboot.

Defragging a SSD drive
Defragging an SSD drive

Also Read: Going Beyond DPO Meaning: Ever Heard of Outsourced DPO?

In September, Microsoft released the “2020-08 Cumulative Update Preview for Windows 10 Version 2004 (KB4571744)” update, which fixed the Automatic Maintenance bug causing SSD to be defragged too often.

The second bug caused the Windows 10 defrag feature, Optimize Drives, to attempt to TRIM non-SSD drives. While this would not damage the drive, it does generate errors in the event log.

Today, almost six months later, Microsoft has still not resolved this bug, as shown by today’s test below.

Defrag is still trying to TRIM a non-SSD drive
Defrag is still trying to TRIM a non-SSD drive

Even though this bug has been reported extensively, Microsoft has also not officially acknowledged in the Windows 10 health dashboard that this bug exists.

Also Read: Limiting Location Data Exposure: 8 Best Practices

Leave a Reply

Your email address will not be published. Required fields are marked *

× Chat with us