The amount of time Defraggler takes to defrag depends on several factors, such as the size of the drive and its read/write speed, number fragmented files and number of times each file is fragmented, and the amount of free disk space that is available.
Also note that Defraggler may take a longer amount of time to complete the defrag in comparison to the amount of time that it takes for other derag utilities to do so. Find out more here.
Here are a few tips that might help speed up the process:
- Run a Quick Defrag. This isn’t as thorough as a full defrag, but it’s a quick way to give your PC a boost. Find out more at:
- Run CCleaner before using Defraggler. This will clean out unnecessary files from your system, allowing Defraggler to run faster. Furthermore, it creates more free space on the drive, making it possible for Defraggler to more efficiently organize files into a contiguous, non-fragmented, block of space.
- Stop the VSS service when defragmenting your drive. This will ensure that unneeded restore points aren’t created when performing a defrag. To do this:
- Open Defraggler > click Settings > Options...
- Click on the Advanced tab
- Check "Stop VSS when defragmenting NTFS volume" > click OK
Note: You can configure Defraggler to be minimized and run silently in the Windows System Tray. This will allow you to use your computer without any interference as Defraggler continues to re-arrange your files in the background:
- Click Settings > Options... > Advanced
- Check "Minimize to tray" > click OK > Minimize Defraggler
Additionally, you can set its Priority to "Background"; this will increase the amount of time the operation takes, but reduce the amount of system resources it will utilize during the defrag operation.
- Click Settings > Priority > Background
Note: If you decide to actively use your computer while defragging, the defrag operation might take a longer amount of time to complete, depending on the amount of system and drive resources that are being utilized. Furthermore, utilization of the computer will likely create new files, and there is a possibility that the data associated with the newly created files will be placed in a non-contiguous (i.e. fragmented) block of space, resulting in new file fragmentation, which might be recognized only after the defrag operation has already finished.