Does defrag run erroneously on SSDs under Windows 8+ ?

[EyepodI]

I have heard conflicting reports that under Windows 8 / 8.1 defrag has been erroneously set to run on SSDs.

I am not sure if it was this forum but someone stated that this was not true and Windows 8 was correctly recognising SSDs and not defraging.

But then I read this article and it appeared that my SSD (Samsung SSD 840 Pro) was being defragged on regular scheduled maintenance tasks (clean install of 8.1).

Anyone know the definitive answer on this I am little confused??

 

[wazza300]

mine doesn't on 8.1

just look in the schedule and see its disabled or try to defrag the ssd it simply wont let you

 

[EyepodI]

In the "Optimise Drives" dialog i.e Windows-R "dfrgui", invoking an Optimise on the SSD and it performs a "TRIM" but doesn't seem to try to defrag.

Running defrag.exe from command line and it does seem to attempt defragging as it stated 3% defragged when I first ran this before the text below which now reports only 2% defragged. So I assume it tried some defragging before I stopped the operation

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>defrag c:
Microsoft Drive Optimizer
Copyright (c) 2013 Microsoft Corp.

Invoking defragmentation on Windows (C...


Pre-Optimization Report:

Volume Information:
Volume size = 232.54 GB
Free space = 150.91 GB
Total fragmented space = 2%
Largest free space size = 103.03 GB

Note: File fragments larger than 64MB are not included in the fragmentat
ion statistics.


Cancelling operation...

The user cancelled the operation. (0x89000006)

C:\Windows\system32>

Also the task scheduler is set to run the command : %windir%\system32\defrag.exe -c -h -o -$

The -c argument = perform operation on all volumes
The -o argument = perform operation on all media types
The -$ arguments is not actaully documented.

Soooo.... I am still a little confused

 

[Rroff]

Windows 7 will also sometimes incorrectly identify an SSD and schedule degragging on it - guessing same issue exists on Windows 8+ to.