pe1dnn

When a USB stick is present when Defraggler is started then the drive will be marked "in use". When someone, while defragementing C:, wants to remove de USB stick using windows "safely remove hardware" function it doesn't work because the drive is in use (by Defraggler). Defraggler needs to be closed to release the lock on the USB stick (i.e. first stop defragging of wait until it is finished). It would be nice when Defraggler would not lock any drives it doesn't work on, or respond to the request to release any file handles when an attempt is made to remove the drive. Alternatively add an unlock button or make an option to remove a drive from the view - which will need to be working while defragmenting another drive obviously.

To quote myself: I'm sorry to report that there is a problem now, the master file table (MFT) is way to big now. It looks like I have to take all the files off, reformat the drive and put them back on to get it correct again. (Unless the new Defraggler also makes the MFT smaller, but I guess not...). Bummer...

The problem is that Defraggler seems to try to defragment a file called $BadClus:$Bad which is an NTFS system file containing the drives bad sectors. I have a drive without bad sectors (check with chkdsk x: where x: is the driver letter). Most disk are free of bad sectors, at least as seen from windows. Defraggler claims the file is as big as the drive is. So the file does not fit on the drive with all the other files. Maybe a bug triggerd when the number of bad sectors is zero? The file does not show up in the file list. I found the file on the drive map, when you click on a square a tab Highlighted is openend containing the file using that part of the disk. I clicked on a large file and saw this special file with its very big size. There are other reports mentioning this file, how ever I saw in this thread it was not yet connected to this problem, I think its the cause of the problem. So it needs to be fixed. In the mean time you could select all files and defrag only the selected files. I only hope Defraggler did not make a mess of my disk by creating a faulty $BadClus:$Bad file during the defrag attempt... Addition: the $BadClus:$Bad file also shows up when clicking on an unused area since it spawns the whole disk...