wnm

Neither the sysinternals ProcessMonitor nor the disk activity light indicate that much disk I/O is happening. The disk activity light just blinks briefly every 2 or 3 seconds. A reasonable point. I would then wish that they'd find a way to make use of the other cores for all the computations that are seemingly occuring (if it can be done safely).

On a totally idle system Defraggler seems to top out at a constant 25% CPU usage level. This is true even if I use task manager to bump up its priority above normal. This suggests to me that the program is doing some sort of self-throttling. If that is the case, please allow the user to set the percentage-CPU-used amount to higher values.

Sorry I didn't mention this in the first post but I'm already running with the hibernation and restore point files excluded.

When started and just told to to do a full (as opposed to quick) defrag, it takes an inordinately long time to complete and once it completes or if it is stopped and restarted, the analysis numbers show a much more fragmented disk than they did one minute earlier before it stopped. If I instead just go to the fragmented file list and select all the fragmented files and tell it to defrag those, then it will fairly quickly work its way through the list defragging most and significantly improving the remaining and when it stops a subsequent analysis will show the drive more or less totally defragmented. Shouldn't the two methods be producing similar run times and results? Is there a command line switch (CLS) so I can tweak a scheduled task to just select the fragmented files and defrag those? And while I'm asking, is there a similar CLS for defragging free space?

Flash drives especially should not be shown since Defraggler "locks" them so they cannot be dismounted using the Windows "Safely Remove Hardware" option. If a utility like "Unlocker" is used to force Defraggler to let go of the flash drive so it can be dismounted using the Windows option then Defraggler freezes and the process has to be killed. Using the "Exclude drive" option in defraggler has no effect on this.

If defraggler happens to be working on my C drive (not unusual considering how slow defraggler is) when I plug in a USB flash drive, it immediately accesses and locks the USB drive against removal. Considering I never want defraggler to touch the flash drive, this is a real annoyance when I go to safely remove the flash drive. This happens even though the drive is on defraggler's EXCLUDE list. Yes I can yank the flash drive without using the safe removal option or I can break the lock between defraggler and the drive using Unlocker, but eventually defraggler notices either of these methods and gets confused by them and the GUI stops responding. My suggestion is that defraggler should not touch any drive IN ANY MANNER if it has not been invited by the user to touch that drive.