Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Took the plunge and installed Windows 7 on my computer. Even better, I installed it on my new Intel x25m (got to love that SSD goodness.)

Vista was known to thrash, throttle, and otherwise wear out an SSD. Apparently Windows 7 addresses some of the more serious issues.

However, I am more concerned that maybe Windows 7 is not using those optimizations. I am paranoid, but at the cost of the SSD (ouch!!), I want to get as much life out of it as possible.

Is it possible to confirm that Windows 7 is using all of the cool new SSD optimizations? That it has properly confirmed that your drive is an SSD?

UPDATE

Thanks for your feedback. Contrary to the Q & A, Superfetch IS running on this system. And given the answer to the command line I was given, I think that Windows 7 is NOT using optimizations. VERY ANNOYING. Is there something I can do to make Windows 7 treat my drive like the SSD that it is.

Also, what is this talk of the drive "alignment"? Is there a way to confirm that as well.

Also, disk defragging WAS enabled. I disabled it.

FYI, the Windows Experience Index for the system is 7.8 for the drive.

share|improve this question
    
You can get the alignment info using wmic partition get startingoffset quite what you do with the numbers that gives you I'm not totally sure. – GAThrawn Nov 28 '09 at 16:30
    
Don't dismiss defragging an SSD too quickly; see: superuser.com/questions/13668/what-does-a-defrag-actually-do/… – Leftium Apr 18 '10 at 11:44
up vote 20 down vote accepted

If you open a command prompt window (as an admin) and type the following command, Windows 7 will tell you if it's detected that your drive supports the TRIM command and thus has set Windows to use the full range of SSD optimizations automatically:

fsutil behavior query disabledeletenotify

You should get something back like "DisableDeleteNotify = 0" if your drive is being treated as an SSD.

The full Q&A that the Windows 7 Engineering Team posted about SSDs is here.

share|improve this answer
    
GA, You are making very glad I asked the question. When I typed the command that command I got the answer DisableDeleteNotify = 0. Which means Windows 7 is NOT treating my disk as an SSD. Is there anything I can do to turn on optimizations? Seth – Seth Spearman Nov 28 '09 at 14:57
    
I will read the Q & A when I am able. Thanks for the link. Seth – Seth Spearman Nov 28 '09 at 14:58
2  
If DisableDeleteNotify = 1, this means that Windows 7 has turned TRIM off. So this would be undesirable if the SSD supports TRIM. – sblair Dec 7 '09 at 0:20
3  
Ah **** you're right, right command but I had it the wrong way round, don't know what happened there. Will edit my answer to correct it. Sorry if I've mislead anyone, really didn't mean to. – GAThrawn Dec 7 '09 at 14:42
1  
This command only shows if TRIM support is disabled in Windows. The "0" result doesn't even mean you have an SSD installed. Source. – i3v Jun 10 at 18:44

"the cool new SSD optimizations" are largely eyewash, hardly 'cool' and certainly not new. MS certainly did not reinvent the wheel here.

When a solid state drive is present, Windows 7 will disable disk defragmentation, Superfetch, ReadyBoost, as well as boot and application launch prefetching.

as you can see, these are just some basic tweaks known to owners of solid state disks for a long time.

the only notable advancement in Windows 7 is support for the Trim command, which deals with the way that data is written to NAND memory.

the real 'killers' (to sound a bit scary :) are virtual memory and temp folder usage which Microsoft has not addressed at all. you will have to take care of your SSD yourself if you really want to have 'cool optimizations'.

here are some links for you:

SSD Windows Registry Tweaks

NTFS Performance Hacks

also make sure to align the partition of your SSD and make proper use of a RAM disk.

share|improve this answer
    
But above 2 links are relevant for Windows XP. – Boris_yo Aug 26 '12 at 16:54

I think what you're looking for is a program called Intel SSD Toolbox, but it doesn't look like you can download it currently because it has some bugs. I wouldn't worry too much though. Wearing out an SSD takes a very long time (I've read that in normal use cases, a good SSD will generally outlast a normal hard drive).

share|improve this answer
    
You can write several gigs a day before reaching the listed write lifetime on a current consumer SSD. Since SSD failure is caused by a slow progressive increase in write times it's actually easily detected by SMART tools allowing the firmware to move data to healthy parts of the SSD. Also an article I read indicated that those numbers are pessimistic and that only a few percent of the total capacity had to be removed as bad sectors at that point with most lasting significantly longer. – Dan Neely Nov 24 '09 at 20:19
2  
downloadcenter.intel.com/… this is the Intel SSD Toolbox, it's fully working atm. – Raveren Jan 13 '11 at 16:06
1  
@BrendanLong AFAIU, you are talking about this method. But, firstly, It may not work in some cases, e.g. through my "LSI SAS3 3008 Fury" RAID controller on Dell 7910. Secondly, AFAIK, it only shows if your SSD supports TRIM - it still might be not working due to OS or controller issues. – i3v Jun 11 at 12:55

To my knowledge, currently there's no simple method, that would cover to all possible cases.
Still, in most practical cases, it should be enough to check the following:

  1. As mentioned here fsutil behavior query disabledeletenotify should be 0, otherwise TRIM is disabled in your OS.
    Still, this does not mean that OS recognizes your SSD.

  2. If OS recognises your SSD drive, Windows7 should remove it from the defragmentation schedule, (Win8 and Win10 explicitly show "Media type=SSD" in their "Defragment and Optimize Drives" tool). If this part is OK, this means that your OS do recognize your SSD. And do send TRIM commands.
    Still, this does not mean that SSD receives them.

  3. Next, check word 169, bit0 in your drive information. This could be done, for example, using Intel SSD toolbox or hdsentinel tool (trial version is enough). Probably, there are more tools to do that. This bit should be "1" if your SSD supports TRIM. (Most modern SSDs do support it.)
    Still, this does not mean that the TRIM commands, sent by your OS are properly passed to your SSD, e.g. your RAID controller might not pass them properly.

  4. (Actually, it’s OK to start from this point.) There are few experimental methods to see the evidence, that TRIM is actually working. The most simple & automated way is to use the TrimCheck tool. Sidenote: disk compression, disk encryption, and write-cache buffer flushing should be off.
    However, there’s still one more caveat here – the DRAT / DZAT features. Too check, if your SSD support DZAT, take a look at word 69, bit14 & bit5 (once again, the “Intel SSD toolbox” should be able to show them, in most cases).

    • If both DRAT / DZAT bits are "1" – you’re lucky - the tool should give you "TRIM is working" almost immediately (if it’s actually working). Still, you might need to reboot your PC, and/or launch the "disk optimization" (if you're using Windows 8/10).
    • Otherwise, things got more difficult. The tool may give you CONCLUSION: TRIM appears to be NOT WORKING (or has not kicked in yet) for a few weeks. And then Data is neither unchanged nor empty <...> CONCLUSION: INDETERMINATE, but this does not actually mean that your TRIM is not functioning.
      On the other hand, there's still a chance, that you would get CONCLUSION: TRIM appears to be WORKING! one day. Try leaving your PC idle overnight (as well as rebooting and launching the "disk optimization"), to let SSD's built-in garbage collector do his work. If TrimCheck shows TRIM appears to be WORKING!, this almost certainly means just that (unless some ridiculous 3rd party tool was intentionally writing zeros here and there, and, placed zeros above the test data as well). For those who interested, some technical details (as far as I understand them) are here.
  5. The developer of the hdsentinel tool, claims that his tool uses a different approach, based on DEVICE_TRIM_DESCRIPTOR. And that this method alone should do the job. And that it won't even give a "false positive" if RAID controller is not passing TRIM commands correctly.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .