Death, taxes, and the Windows 10 update disaster; yet another reason to wait for the Windows 10 May 2020 update

According to a post on Windows Latest, the Drive Optimizer tool (aka Disk Defragmenter tool) is acting terribly buggy for some users This is a flaw that reminds us why Microsoft was slow to roll out Windows 10 2004 to all users

Widely regarded as one of Microsoft's key pack-in applications, the Hard Drive Maintenance Tool typically runs in the background and cleans all partitions on the drive These routine infrastructure tasks are only noticed when they go wrong

And now, after updating to Windows 10 2004, users have reported that Drive Optimizer does not log the scan status and history So when you look at the app to check the history, you may see a sign that a scan was performed, but it was not It may even warn you that your storage is not optimized, even though it is not, and drive you crazy trying to fix it

But the good news about this flaw is that Drive Optimizer still appears to be running in the background We just can't confirm it

According to Windows Latest, Microsoft reported that it fixed such an issue in Windows 10 Build 19551 in January, stating, "The Drive Optimizer control panel incorrectly indicated that optimization was not running on some devices Thank you for your report that this was not the case This has been corrected in this build"

It states

We hope that fixing this issue is as easy as figuring out how it was resolved in the 19551 version and repeating that process in Windows 10 2004

As I explained yesterday in my article about the external monitor going dark after an update, the best thing you can do if you encounter a bug in the May update of Windows 10 is to roll back Windows 10 Before you dive into the Settings app to do so (and I don't think this issue is disruptive enough to require it), back up your system using one of our best cloud backup services