Windows 10: SSD trim on an MBR install

I currently see 3 drives in 'optimize drives' as follows: C: , System Reserved which I assume has the boot tables and stuff, and what appears to be a network drive displayed \\?Volume{8ebc5064-0000-0000- etc.

In Disk Management I have the System Reserve partition and C: plus a 450 MB recovery partition.

My concern is that I can only trim the C: drive and not the System Reserved 100mb drive. Is this a thing or a non concern?

This was a fresh install after an upgrade, and my 1st SSD experience. Things right now are good and have been so since NOV. I am just worried about a corrupted boot table or something unforeseen.

:)

 

Defragment & SSD

Hi.

I have installed a Samsung SSD 850 Evo on a Windows 10 build 10.0.14393.

In the Defragment software, I saw "trimmed" instead of "defragmented".

What is trim? Is it necessary to run defragment on SSD?

Running defragment makes any problem to SSD or not?

Thank you.

 

Trim enable on new dell laptop with windows 10

Hi jmann, yes TRIM should always be enabled on an SSD for it to function efficiently

By default Windows will will manage TRIM on your SSD without any user input

To check that TRIM is enabled:

Open a Command Prompt Window and run this command:

fsutil behavior query DisableDeleteNotify

If that command returns 0, trim is already enabled on your SSD

If 0 is not returned, run this command to enable TRIM:

fsutil behavior set DisableDeleteNotify 0

 

That is standard fair. Have never been able to run optimize on the system reserved part of drive. Don't worry about it.

 

The trim command is used to wipe data from portions of the SSD that have had files stored there that have been deleted. How many files are being deleted from the System Reserved Partition on a routine basis? The answer is none. It is very, very infrequent that anything in the System Reserved Partition is changed, therefore there is no need from trim in the System Reserved Partition.

 

Thanks, I was concerned that when booting read/writes might be taking place, even if small, and build up over time. The system is basically a gaming console attached to a DLP, and is rebooted frequently.

 

It should be reading only unless you intentionally change the boot settings.

 

So overclocking the CPU with tests is not a factor?