The command is CONTIG (also available in 64-bit as CONTIG64), and it is a Sysinternals:
You’ll want to put the appropriate binary in
C:\Windows. Run it like this, in administrative CMD, it will get all of the hiddens it can for C drive (this is 64-bit):
contig64 -nobanner -accepteula C:$Mft
contig64 -nobanner -accepteula C:$LogFile
contig64 -nobanner -accepteula C:$Volume
contig64 -nobanner -accepteula C:$AttrDef
contig64 -nobanner -accepteula C:$Bitmap
contig64 -nobanner -accepteula C:$Boot
contig64 -nobanner -accepteula C:$BadClus
contig64 -nobanner -accepteula C:$Secure
contig64 -nobanner -accepteula C:$UpCase
contig64 -nobanner -accepteula C:$Extend
Notice the distinct lack of slashes in the above!
The command is CONTIG (also available in 64-bit as CONTIG64), is a Sysinternals:
It defrags, and does it very well. It does it file by file. Here’s a command probably suitable for background operation on a whole C drive, on a 64-bit machine, quiet mode:
start /LOW contig64 -s -q C:\*
Recently acquired advice. Better speed, less wear on the drive. It is a Windows service by that name.
Found this today.
- A two-month-old laptop with a SanDisk SD8SN8U-256G-1006 SSD for its C: drive, Windows 10.
- Windows had recognized the drive as a standard hard drive, not an SSD, and the laptop had slowed down a lot very recently.
- Installed the SanDisk SSD Dashboard, ran TRIM, and scheduled weekly TRIM operations.
- Laptop much faster.
Here’s a tool. Run this once as administrator on the drive to check, wait 20 seconds and do it again, and if it says you’re good, you are.
article #930, updated 1223 days ago
We can control the autorepair facility in NTFS, with
fsutil repair. Under Windows 8/2012 it will list entries of a volume’s corruption log, initiate repair, query and set the self-healing state, query the corruption state, and wait for repairs to complete.
The command is
The following usages enhance speed. There are caveats for each.
- Don’t do this if you use compression :-)
FSUTIL behavior set disablecompression 1
- Don’t do this if you use Microsoft built-in encryption!
FSUTIL behavior set disableencryption 1
- This one interferes with some backup and file-sync systems.
FSUTIL behavior set disablelastaccess 1
- This will interfere with very old software, or software whose updates do not comply with Microsoft’s recommended practices, especially involving DOS-style short filenames.
FSUTIL behavior set disable8dot3 1
- Designates more RAM for disk cache. Only use if you have ample RAM. Default is zero, 1 is an option.
FSUTIL behavior set memoryusage 2
This one may decrease speed a tad, but should increase reliability. Does not work with system drives, it is unclear as to why.
FSUTIL resource setconsistent E:\
This one resets NTFS transaction logs at reboot, this can eliminate many issues of filesystem slowdown over time which have to do with a kind of corruption which CHKDSK does not catch.
fsutil resource setautoreset true c:\
This one reserves more disk space for file tables; can be 1, 2, 3, or 4. Makes handling of large quantities of files more efficient. Unfortunately only helps for partitions created after the setting is made.
FSUTIL behavior set mftzone 4
Here is a procedure which reportedly does a full wipe and recreate of the NTFS transaction record for a system drive. The commands below need to be run in an administrative CMD, then the machine rebooted. ‘setautoreset’ tells the system to do a smaller-scale reset at every boot, it is not known whether there is any reason to set it back to ‘false’ after the reboot is complete. The procedure appears to be able to eliminate some extremely stubborn Windows Update errors, as well as alleviating some situations where NTFS volumes become very slow in accessability. Setting setautoreset to true, all by itself with a reboot, has been seen to help quite a lot too.
fsutil resource setautoreset true %SystemDrive%\
attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
Apparently, corruption in Windows filesystem transaction support will cause many different kinds of errors, ranging from IIS not starting to scheduled task creation failing to Windows updates failing. To fix this, one can do the following in an administrative command prompt:
fsutil resource setautoreset true c:\
In some circumstances it is reportedly helpful to repeat the above for E:\ and any other NTFS drive in production.