8% is nothing to worry over. It's likely that this is as defragmented as much as possible.
You could look at the file list and attempt to defrag individual files, but you should remember one thing. Windows begins fragmenting immediately (even as it is being defragmented) thus the "holy grail" of 0% that you are trying to achieve is nonexistent. Anything less than 25% is pretty much optimized with no need to defragment.
As I said, there is no problem. The rest of the fragments are unmoveable at this time. If you wish, try to individually defragment them. It is likely that they are sharing blocks with unmovable files and/or they themselves are unmoveable.
What are some of the files listed in the files window
on my 370 gb partition of windowsdrive was my hibernationfile 6,24 GB and pagefile 8 GB fragmented and it shows me 7% or so. all others are ok. the only thing i could to was todeactivate these files (the pagefileimovedto another partitionforthe defragmentation process.), then defragment the windowsdriveand thenactivate thefilesagain. -now are these files in one piece.
perhaps also the systemrestorepoints...
have you some large other files? movies. images...
have you looked at the tab "File list" after "Analyze"?
I've used the windows tool and it defrag really good, while defraggler doesn't do it stopping at 0%. After I finished it, I tested the free space defrag (Normal, I don't know if the permission of fragment one is better or not..) of defraggler, it worked with E drive, but I had to test several consecutive times before making it work on C drive (it usually stops at 0%).
Can I ask why the exclusion of restore point and ibernation files is preferred?
Anyway I deleted all the restore point except for the last one.
On drive E, after free space defrag, all "spaces" are occupied and then all are cleaned, except for one that is after a lot of transarent "spaces". I'm curiose to know why only that file hasn't been moved.
Can I ask why the exclusion of restore point and ibernation files is preferred?
my spin on that is, why defrag the pagefile, hibernation file, swap files, restore points etc. when they are going to get frag'd as soon as you start using the PC.
those sort of files have high I/O and are in almost constant use, by their very nature, they are always fragmented, it's usually just a question of how badly.
my spin on that is, why defrag the pagefile, hibernation file, swap files, restore points etc. when they are going to get frag'd as soon as you start using the PC.
those sort of files have high I/O and are in almost constant use, by their very nature, they are always fragmented, it's usually just a question of how badly.