I think I read that it was not needed ... :(

That is correct.Cheers, -jahman.

Thanks :( auhhh one less thing to do.....now back to MY sim :( .

Allow me to expand on why it is not necessary to defrag a SSD....(forgive me if some of this is common knowledge - it is important to know, though!) To start, it is important to know what fragmentation is: Fragmented files occur when a single file is broken up into multiple pieces, and those pieces ("fragments") are placed in different locations on the drive. This occurs for a myriad of reasons, and is a normal part of operating a hard drive. Now - why is it not necessary to defrag a SSD?(Setting: old time AM radio hissing and whining in the background, and my voice is elderly and cracking...)Back in the old days, hard drives were made out of spinning platters, and they had read/write (R/W) heads which moved over the platters. The R/W heads needed to physically move to the location on the platter in order to read the files it wanted. When a file gets fragmented, the R/W head needs to move all over the place to gather in the fragments in order to read the whole file. This process, while fairly quick to the naked eye, is extremely slow in computer terms... and when you compound this against many fragmented files, it is quite inefficient.In steps "defragmentation"! By keeping all the file chunks as close together as possible and eliminating fragments, you allowed the R/W head to go to only one location to read the file. No more darting all over the surface of the disk to get the fragmented data for the file... this speeds things up, keep things efficient. (Setting: white-washed 1970's impressionistic room of the future. I'm wearing a white jumpsuit. Synthesizer music is playing in the background, and I am speaking in low, calm tones of voice...) Today, in the modern age of computers, we use SSD drives. These drives do not contain any moving parts - all the date is held in a core of memory. If the computer needs a file, it simply calls the data directly from the location it is in. When this drive's files gets fragmented, the SSD drive simply calls the components from the locations they might be in just as it would if it was in one single location.You are not encumbered by a physical R/W head moving to all the fragments anymore - it is all instantly done via the digital control, rendering defragmenting unneeded. If you were to perform a "defragmentation" on a SSD drive, you would realize no performance or efficiency gains. It doesn't matter if your file is in one contiguous block, or broken into 15 pieces scattered throughout the drive - the controller will instantly fetch each piece without delay. (Setting: Back to normal! I'm tired of the role playing.)In fact, defragmenting a SSD drive may actually lead to a (slightly) shorter service life. Without getting too technical, a SSD has a limited lifespan, measured in the number of writes and re-writes to the memory. (Don't worry, it's a long enough time for you to get your money's worth, but do you want to test that?). Defragmenting a drive causes the drive to attempt to erase and rewrite many many cells on the drive. When you consider the process of defragging a SSD has no practical benefits, these additional erase/write cycles are wasted on the defrag, when they could be used for more practical purposes. (There are other technical reasons for not doing it too, but considering there is no practical benefit to defrag a SSD in the first place, I'll leave the discussion about TRIM and garbage collection out for this post)I hope this helps. The above post is indeed correct that you do not need or want to defrag a SSD drive - but I feel it's important to understand why!Cheers,-Greg

Thanks Greg - good read!

RyanWhile you do NOT have to "defrag" an SSD drive, if you write/change/delete a lot of data on the drive eventually it slows down (takes a long time in FSX). So to "rejuvenate" the SSD you can use a function such as "TRIM". From Wiki: In computing, a TRIM command allows an operating system to tell a solid-state drive (or "SSD") which data blocks are no longer in use, such as those left by deleted files. An OS operation such as delete generally only means the data blocks involved are flagged as not in use. TRIM allows the OS to pass this information on down to the SSD controller, which otherwise would not know it could overwrite those blocks safely. The root cause of the issue is that SSD drives do not know which blocks are truly in use and which are free. SSDs do not understand file system structures used by computer operating systems and cannot access their list of unused clusters. See http://en.wikipedia.org/wiki/TRIMMany of the newer drives have a "TRIM" or similar function to prevent too much slow-down over-time and is supported natively in Win7.RegardsPeterH

I bet it doesn't take very long to zero a drive. Are they recoverable after being wiped like magnetic drives?