brak

I have "Move large files to end of drive during whole drive defrag", "Move only selected files, folders and file types" and "Do not apply minimum file size to custom Files/Folders" enabled. And I have several directories defined in the Files/Folders tab. For whatever reason, this doesn't always work properly. On one of my drives everything in the specified directories is moved to the end, fragmented or not. And everything not in the specified directories is moved to the front, fragmented or not. On another drive only some of the 'Large Files' are moved to the end, even if they are fragmented. I don't typically use Defrag Freespace, but when I run it on the problem drive (with "Do not move 'Large Files' during Defrag Freespace" disabled), the 'Large Files' that get left in the middle during standard defrag get moved. It actually leaves large swaths of empty space and some fragmented files for whatever reason, which is why I part of the reason I don't bother with it, but I digress. The point is it rules out any file access issues and makes it even more strange that normal defrag doesn't move these files. Anyway, I don't think I can provide anything in the way of troubleshooting this. So what I'd like is the option for the 'Large File' settings to be honoured when doing per-file defragmentation, even if the file isn't actually fragmented. Maybe it's a hacky work-around, but at least it should produce the desired/expected results when normal operation fails to do so. ----- Additionally, I noticed that when using the built-in folder encryption (Windows 10 Pro), what I assume is metadata related to the encryption (<filename>:$EFS) doesn't get touched during defrag. This can lead to the metadata being spread all over the drive over time. If it's possible, it would be nice if this metadata could be moved along with the related file.

I've been using Defraggler for as long as I can remember. Another data point indicating I'm a harbinger of market failure I guess. :(

I ended up just deleting and re-creating the partition. Defragmentation now works properly.

I have a disk had two basic partitions. I had run Defraggler on both partitions multiple times. Today I deleted the first partition and replaced it with a striped volume. The second partition was automatically converted from basic to dynamic, but I didn't make any manual modifications to it. Now when I try to defragment the second partition, the operation hangs indefinitely at status "Defrag Started". Pressing Stop has no effect, and a Defraggler process remains after closing the window (consuming roughly 25% CPU). I'm reluctant to enable boot time defrag in case it hangs there too. I hadn't had any issues with the partition outside of Defraggler, but just in case I ran a thorough chkdsk (chkdsk /f /r /x /b) which passed without any issues. That was after rebooting. The second drive that's part of the striped volume has two additional partitions, and I was able to successfully defragment one of them. I actually have very little data on the problem partition, so I may just copy it elsewhere then delete and recreate the partition. But I was wondering if there's anything I can do to troubleshoot first. Defraggler version: 2.22.995 (64-bit) Windows Edition: Windows 10 Pro Windows Version: 21H1 OS Build: 19043.2130