What does the scheduled defragmentation really do on a SSD when DisableDeleteNotify
is manually set to 1
on recent Windows versions like Win 10?
Assuming that the SSD is properly detected by defragment as an SSD it is supposed it will go ahead to trim the free space; however configuring this parameter DisableDeleteNotify
to 1
is globally documented in internet as fully disabling trim
in Windows system-wide.
A link to any related documentation of MS would help to clarify the response.
The (off topic) context on this question is this: disabling instant trim while postponing it to a weekly task, similar to Linux, allows margin to forensic recover deleted data and files from SSD as it was possible with the old HDDs (now you only get zeroes).
it is supposed it will go ahead to trim the free space
?fully disabling trim in Windows
: docs.microsoft.com/en-us/windows-server/administration/… Neither does its name hint so. Rather it pretty much implied that (only) notification (i.e. unmap/trim) upon (file) deletion will be disabled. Seems equivalent enough to thenodiscard
mount option (which does not "block"FITRIM
ioctl completely) in Linux to me.fstrim
though (i.e. without all the schedule crap).