This article needs additional citations for verification. (September 2011) |
Microsoft Drive Optimizer (formerly Disk Defragmenter) is a utility in Microsoft Windows designed to increase data access speed by rearranging files stored on a disk to occupy contiguous storage locations, a technique called defragmentation. Microsoft Drive Optimizer was first officially shipped with Windows XP.
 | |
 Microsoft Drive Optimizer in Windows 10 | |
| Other names | Disk Defragmenter |
|---|---|
| Developer(s) | Microsoft |
| Operating system | Microsoft Windows |
| Type | Defragmentation software |
| License | Proprietary commercial software |
Defragmenting a disk minimizes head travel, which reduces the time it takes to read files from and write files to the disk.[1] As a result of the decreased read and write times, Microsoft Drive Optimizer decreases system startup times for systems starting from magnetic storage devices such as a hard drive. However, defragmentation is not helpful on storage devices such as solid state drives, USB drives or SD cards that use flash memory to increase speeds, as these drives do not use a head. Doing so may decrease lifespan for these types of devices.
From Windows 8 onwards, the program was renamed to Microsoft Drive Optimizer, with some references changed to say Defragment and Optimize Drives or simply Optimize Drives.
Early history
editAs early as the end of 1982, the IBM PC DOS operating system that shipped with early IBM Personal Computers included a Disk Volume Organization Optimizer to defragment the 5¼-inch floppy disks that those machines used. At this time, Microsoft's MS-DOS did not defragment hard disks. Several third party software developers marketed defragmenters to fill this gap. MS-DOS 6.0 introduced Microsoft Defrag.[2] Windows NT, however, did not offer a Defrag utility, and Symantec was suggested by others as a possible alternative for the utility.[3]
Initial releases of Windows NT lacked a defragmentation tool. Versions through Windows NT 3.51 did not have an application programming interface for moving data clusters on hard disks.[4] Executive Software, later renamed Diskeeper Corporation, released Diskeeper defragmentation software for Windows NT 3.51,[4] which shipped with a customized version of the NT kernel and file system drivers that could move clusters.
Microsoft included file system control (FSCTL) commands to move clusters in the Windows NT 4.0 kernel,[4] which worked for both NTFS and FAT partitions. However, Windows NT 4.0 did not provide a graphical or command-line user interface.[4]
Debut and early versions
editDisk Defragmenter first shipped as part of Windows 95 and later shipped with Windows 98 and Windows Me, licensed from Symantec Corporation. It could be scheduled using a Maintenance Wizard and supported command line switches.[5] In the version of Disk Defragmenter included with Windows 95 and 98, if the contents of the drive changed during defragmentation, the program paused, rescanned the entire drive, and then resumed the process from where it had left off.[6] This quirk was removed in the Windows Me version of Disk Defragmenter.
Disk Defragmenter in Windows 2000 was a stripped-down version of Diskeeper, licensed from Diskeeper Corporation. It uses the following techniques:[4]
- Moving all the index or directory information to one spot. Moving this spot into the center of the data, i.e. one third of the way in, so that average head travel to data is halved compared to having directory information at the front.
- Moving infrequently used files further from the directory area.
- Obeying a user-provided table of file descriptions to emphasize or ignore.
- Making files contiguous so that they can be read without unnecessary seeking.
In Windows 2000 and later operating systems, Microsoft Drive Optimizer has the following limitations:
- It does not defragment files residing in the Recycle Bin or files that are in use.[7] In particular, this includes the registry, page file and hibernation file.
- Prior to the Windows Vista release, only one volume could be analyzed or defragmented at a time and only one instance could run.[8]
- Only local volumes can be defragmented; network volumes are not supported.[8]
- The GUI version prior to Windows Vista cannot be scheduled. However, the command line utility since Windows XP and later can be scheduled.[citation needed]
- Unlike previous versions, the GUI version in Windows Vista does not display a map of disk fragmentation, nor does it display progress during defragmentation.[citation needed]
In addition, the Windows 2000 version has the following limitations which were removed in Windows XP:[8]
- Defragmenting NTFS volumes with cluster sizes larger than 4 kilobytes (KB) is not possible.
- It is not possible to perform fine-grained movement of uncompressed NTFS file data in Windows 2000. Moving a single file cluster also moves the 4 KB part of the file that contains the cluster.
- EFS encrypted files are not defragmented.
Windows XP and Server 2003
editWindows Disk Defragmenter was updated to alleviate some restrictions.[9] It no longer relies on the Windows NT Cache Manager, which prevented the defragmenter from moving pieces of a file that cross a 256KB boundary within the file. NTFS metadata files can also be defragmented. A command-line tool, defrag.exe, has been included,[10] providing access to the defragmenter from cmd.exe and Task Scheduler. In Windows XP, if the Master File Table (MFT) is spread into multiple fragments, defrag.exe and the GUI version can combine the MFT fragments during defragmentation.[11] Windows XP and later has introduced Boot Files Defragment function, this function is enabled by default and can be disabled in Registry.[12]
Windows Vista and Server 2008
editIn Windows Vista, Disk Defragmenter includes an option to automatically run at scheduled times using Task Scheduler and uses low CPU priority and the newly introduced low priority I/O algorithm so that it can continue to defrag using reduced resources (less CPU and disk read/write activity) when the computer is in use. The user interface has been simplified, with the color graph, progress indicator, disk analysis and fragmentation information being removed entirely.
If the fragments of a file are over 64 MB in size, the file is not defragmented if using the GUI; Microsoft has stated that this is because there is no discernible performance benefit since the time seeking such large chunks of data is negligible compared to the time required to read them.[13] The result, however, is that Disk Defragmenter does not require a certain amount of free space in order to successfully defrag a volume, unlike performing a full defragmentation which requires at least 15% of free space on the volume. The command line utility, Defrag.exe, offers more control over the defragmentation process, such as performing a full defragmentation by consolidating all file fragments regardless of size.[14] This utility can be used to defragment specific volumes or to just analyze volumes as the defragmenter would in Windows XP.
Disk Defragmenter is maintained by Microsoft's Core File Services. The Windows Vista version has been updated in Windows Vista SP1 to include the improvements made in Windows Server 2008. The most notable of these improvements is that the ability to select which volumes are to be defragmented has been added back.[15] Notably, the Windows Vista defragmenter is much more effective than the version included with XP.[16]
Windows 7 and later
editWindows 7 reintroduces the analyze function and showing percent complete of the defragmentation, both of which were removed in Windows Vista. It can also defragment multiple volumes simultaneously.
According to Scott Hanselman of Microsoft, Windows 7[verification needed] and later do defragment a solid-state disk (SSD) but in a completely different way. There is less incentive for defragmentation of SSDs because file fragmentation has less performance impact on them and they handle a finite number of storage cycles before their lifespan expires. However, file systems cannot support infinite file fragmentation as they reach their metadata limit. In addition, Microsoft Drive Optimizer is also responsible for performing the TRIM command on SSDs.[17]
See also
editReferences
edit- ^ "How to make a computer faster: 6 ways to speed up your PC". Microsoft at work. Microsoft. Retrieved November 7, 2011.
- ^ Wolverton, Van (2003). Running MS-DOS Version 6.22 (20th Anniversary Edition), 6th Revised edition. Microsoft Press. ISBN 0-7356-1812-7.
- ^ "How do I run Microsoft Defrag?". Computer Help. Computer Hope. Retrieved November 7, 2011.
- ^ a b c d e Russinovich, Mark (March 20, 2007). "Inside Windows NT Disk Defragmenting". TechNet. Microsoft. Retrieved December 9, 2008.
- ^ Windows 95 Defrag.exe Command-Line Parameters
- ^ Description of the Disk Defragmenter Tool in Windows 98/Me
- ^ "Disk Fragmentation and System Performance". Archived from the original on February 13, 2009. Retrieved March 17, 2008.
- ^ a b c Disk Defragmenter Limitations in Windows 2000, Windows XP, and Windows Server 2003
- ^ Russinovich, Mark; David Solomon (2005). "Memory Management". Microsoft Windows Internals (4th ed.). Microsoft Press. p. 728. ISBN 0-7356-1917-4.
- ^ "Description of the new command line Defrag.exe included with Windows XP (MSKB283080)". Microsoft. Retrieved December 9, 2008.
- ^ How NTFS reserves space for its Master File Table (MFT)
- ^ "Enable or disable boot defrag".
- ^ "Disk Defragmenter FAQs". Archived from the original on April 28, 2010. Retrieved April 21, 2007.
- ^ "Disk Defragmenter". User Guide. Windows Vista User Guide. January 27, 2007. Archived from the original on February 13, 2007. Retrieved January 27, 2007.
- ^ "Disk Defragmenter in Windows Vista and Windows Server 2008". Archived from the original on April 28, 2010. Retrieved April 21, 2007.
- ^ "21 Essential Steps to Make Your PC Better/Faster/Stronger – Page 4". Pcgamer. Future. May 28, 2009. Archived from the original on June 22, 2011.
- ^ Hanselman, Scott (December 3, 2014). "The real and complete story - Does Windows defragment your SSD?". hanselman.com. Sef-published. Retrieved December 22, 2014.