New
#20
Word Man, thank you for what you suggested... it now works like a charm! I'm about to defrag my computer now, the first time in at least 3 months!
I now have the same issue (check screenshot) on my PC after running the november Windows 10 (big) update. Not only did it mess up defrag, but also tons of other things. Though I thought I had fixed most, I only discovered the defrag issue a few mins ago.
I thought MS had fixed the november update? That's why I kept postponing it.
I already ran the winsat formal command, but still didn't fix anything. I still cannot defrag my SSD partitions. :|
Any ideas?
//update 1
I also tried running defrag /C /O but that resulted in some kind of back-up warning with error 0x8900002A.
Really lame MS Windows update. (
//update 2
Well I managed to fix this by reinstalling my Intel RAID drivers. I use customised raid drivers from another site: Fernando's Win-RAID Forum (Storage Drivers - BIOS Modding). They have tons of RAID drivers and information. Still lame that MS decided to install other drivers though. Oh well problem solved!
Mike, HHawk went and used that bad word "defrag" again, eh? Note that the /O switch tells defrag to do the optimization proper for the media type.
When I run that command for my single SSD, it runs (only) TRIM on both my OS partition and my WinRE partition - that is clear from the output of the command. As long as Windows isn't confused about the media type of the disk, that should be OK.
Your warning is well taken, however.