Right now I have Defraggler v2.00.230 installed and running on an older Windows XP Professional SP3 laptop. In the last version of Defraggler, the program worked fine initially under both XP and Vista (both x86 or 32-bit versions), but after a few weeks began crashing whenever I attempted to defrag under Vista. I decided to save settings to an *.ini file to see if a setting was corrupting causing the crash, but what I found was something very different. I had a list of folders to be excluded, and after every crash, the folder entries for Excluded Folders would increment by +1 (variable = Excluded Folder, (Excluded Folder++)). If I had folder "E:\Excluded Folder" in the exclusion list in the *.ini file, and Defraggler crashed, the next time I reviewed the exclusion list in Defraggler, after starting it again, I would now see, "E:\Excluded Folder" and "E:\Excluded Folder" immediately below it. Three crashes revealed, "E:\Excluded Folder", then, "E:\Excluded Folder", and "E:\Excluded Folder". If there was more than one exclusion, the entries would continue to increment for every item in the list. If I deleted all entries in the Exclusion List, and Defraggler crashed again, all deleted entries not only returned, but were again incremented by +1. (The deleted entries reappearing might be caused by Defraggler not saving to the *.ini before closing, but it still doesn't explain completely the incrementation... unless Defraggler doesn't look for redundant settings and ignore/delete them upon initialization.)
I wasn't able to determine the actual cause of the crash, but I was able to isolate it to something happening, or had previously occurred in memory. The analysis function worked fine, even after crashes, but as soon as I tried to use any defragmentation function/method; other than defragmenting Checked Fragmented Files, Defraggler crashed. The longer a PC remains running between reboots, the more garbage is left in memory by programs that rely upon the OS to erase their footprints, and maybe that was what caused the crash initially. Considering Defraggler ran successfully numerous times with the same programs always running, that is the only thing that made sense to me at the time. However, maybe the following crashes were caused by the multiple identical entries, which under normal conditions Defraggler doesn't allow.
The one good thing I found out, at least for me, was that if I uninstalled Defraggler, rebooted the PC, and then reinstalled Defraggler, the crashes stopped and it was able to properly defragment once again. I might have also deleted all registry related keys and the *.ini file and its folder, but I don't remember off the top of my head.
In v2.00.230, as mentioned by at least one other person, Large Files are not being moved to the "back" of the hard drive. Initially, I thought this was due to having a folder(s) excluded, but after browsing the forum, it seems that it's not the cause. I went so far as to set the Large File Size to >||>= 1MB (greater than or grather than or equal to 1 MegaByte), just to see if the Map would reflect file movement after a second Anyalysis Pass after Defragmentation, but Analysis indicated all files were being moved to the "front" of the drive.
In v2.00.230, in the Exclusion List, I selected a folder, and unchecked recursive "searching" so that only the folder/directory was excluded, and not the "contents" within the folder. Defraggler excluded all "content" within that folder, so unchecking recursion did nothing for me.
If these features/functions are restricted for some reason in the free version, then I guess I don't have any actual bugs to report with the most recent version of Defraggler.