Windows 10: Latest on SSD settings on Win-10

The real issue here is that MS has not officially released a KB article on why SSD defrag is a feature, why it is needed and how it is implemented. If the SSD defrag is there (as we know it is) there must exist a good explanation for why and how this feature is different from HDD defrag.

Scott Hanselman is the only one who has at least tried to provide an answer to this, but he should not be the one posting "official" info on this. That is MS storage subsystem development teams job as they are the most knowledgeable regarding this matter and the y know how they have implemented this in code.

Same goes for every issues or features Windows has. We need detailed explanations of what is going on, why it is implemented, how it works and some background info/facts on why it has been implemented in a particular way.

If MS would provide the world more information, this topic would not even exist today. Everybody could read the KB article and just realize all is working as it should, or report further bug reports for further investigation and fixing.

 

Yes - I agree.

 

I think vadim's article raises some good points that might make you worried.*Tongue

 

Same struggle Vadim seems to be having with MS (and Scott) for the past couple of years at least on this issue.

 

I just found this and tried out the Powershell command and was shocked. I had set Optimize to daily on Windows 10 because on my Linux installs, TRIM was automatically set to run daily and I figured it wouldn't hurt. After running the command I was shocked to learn that it was only Trimming the SSD's C:\ partition once a week and defragging the SSD's Recovery partition every day with my storage HDD...

 

I assume that this post represents the information from Vadim that you think would concern me.
Why Windows 10, 8.1 and 8 defragment your SSD and how you can avoid this – Вадим Стеркин

After having read it, like he states "The bottom line is that defrag won’t kill your SSD, but it’s not needed". He goes on to discuss only the side of the argument about how SSD's should not be defragmented, but he never discusses any information regarding why Microsoft believes it's a necessary evil when System Recovery is enabled. He's pretty adament that he has found a bug, but MS isn't responding that this is actually a problem.

So, no...I'm not bothered whatsoever by this information. I personally own SSD's that have lasted over 7 years running Windows 7 without any problems. And as I expected, I am moving away from that SSD because of capacity issues, it's only 80GB which is simply not big enough anymore. With 240GB drives available for around $60, it was a no brainer to upgrade.

 

I agree with @pparks1. Also in regards to the recovery partition, there won't be anything to defrag in it because i should never get written to, so when the logs say the recovery partition was defragged, I believe that is only Windows checking it and the their is no actual writing of files taking place. It looks at it, yep still there, nothing has moved, defrag complete.

 

This intrigued me to also check out my laptop that only has an SSD and I just clean installed Windows 10 Pro on it last week after I got it.
Code: TimeGenerated : 03-Feb-17 16:50:26Message : The storage optimizer successfully completed defragmentation on (C TimeGenerated : 03-Feb-17 16:50:26Message : The storage optimizer successfully completed defragmentation on Recovery[/quote] It seems as if Windows did try to actually defrag my whole SSD on my laptop the day after I installed it. The C:\ and Recovery partitions are both on a 180GB Intel SSD and that's the only installed drive.

 

Hi,

Does it really defragment SSDs ?
I do not think so for if you run a fragmentation analysis it invariably shows a percentage of fragmentation.

EDIT: I must add that in my case "System Restore" is never ON.

Oh, and while we're at it, why does W10 defragments UASP connected SSDs as if they were HDDs ??

Cheers, *Wink

 

The Recovery partition has no drive letter. Windows cannot automatically defrag it or trim it. And a user cannot with defrag.exe or any 3rd party.

 

Hi,

Sure, but what about the other partitions on an SSD ?
And I mean really defragmenting it not just running a retrim command such as "Optimize" does.


Cheers, *Wink

 

I've never seen Windows try to defrag any part of an SSD. MS is not always up to date with their vocabulary...might just be getting hung up on words. Like these:

The storage optimizer successfully completed defragmentation on (C*Smile
TimeGenerated : 03-Feb-17 16:50:26Message : The storage optimizer successfully completed defragmentation on Recovery

I believe it's simply stating that it looked at that partition, because it was there, and said "OK, I've looked at you, but nothing I can do!". It successfully completed the obligation to look at the partition, and did absolutely nothing to it. The response string in the code is out of date with the function. Just words.......

 

This is not true. Windows only need to understand the filesystem, in order to be able to defrag that particular partition. Drive letter or not, does not matter. That is just a human readable/accessible convenience.

 

Sorry, either I worded that not quite right, or there's a misunderstanding. This is what I'm referring to. Normal home user is not likely to be running defrag commands at a command line. The UI below runs defrag.exe under the covers. Clicking on Recovery or any of the root labeled partitions simply returns immediately with no action taken.

 

That is the exact command the Windows Scheduled Tasks runs. I just ran it manually in CMD. The same command will apply to all editions of Windows (Home, Pro, Enterprise, x86, x64).