Defraggler says no fragmented files Diskeeper disagrees!

[ectotropic]

I have been using defraggler for a while now and have been pretty happy with it so far, but when my page file became fragmented I was forced to turn to Diskeeper (trial install) since it seems that it is about the only defragmenter able to fix that issue for Windows 7. Will I was playing around with it I happened to notice that on drives that defraggler said there were no fragmented files Diskeeper often listed one or more fragmented files (and not files that were locked or otherwise inaccessable), which it was then able to defragment.

 

I realise that different software can have different criteria for certain things, but fragmentation would seem to be a fairly black and white issue (either a file is fragmented or it isn't).

 

For the record I'm using Windows 7 x64 with multiple SATA drives (2 data drives, 3 drives in RAID 0 - split into 2 partitions).

 

I can happily provide any more information needed!

[Uranus One]

Hi! While you are logged into Windows, the pagefile is in use and files in use can not be defragmented.

• View documentation:

Understanding the Drive Map

It's not a bug, Defraggler does not have an offline mode.

 

Greetings!

[ectotropic]

I think you have misunderstood what I was talking about - I should probably have made it clearer, sorry.

 

I realise that the page file is in use while running windows and so can't be defragmented - the only reason I mentioned it was to explain why I was also using diskeeper (since it is one of the few apps available that can defragment the page file in Windows 7 x64).

 

The bug is not related to the page file, but to other files not currently in use.

 

How the bug occurred:

• Closed all open programs and stopped all services able to be stopped (via services.msc)
  
• Defragmented all drives with defraggler till it told me no files were fragmented (excluding non-defragmentable files; page file, $MFT, etc)
  
• Opened diskeeper and analysed all drives
  
• Noticed that diskeeper said several files were fragmented
  
• Defragmented all drives with diskeeper (which defragmented several files)
  
• Analysed all drives with both defraggler and diskeeper
  
• Both now say no fragmented files (again excluding non-defragmentable files; page file, $MFT, etc)
  

Note that on some drives defraggler listed no fragmented files at all (including non-defragmentable files), yet diskeeper told me there was files that were fragmented on the drive (which is was able to defragment).

 

The bug, then, is simply that diskeeper apparently found and was able to defragment file that defraggler did not.

 

I hope that makes more sense!

[Uranus One]

Now, if that makes sense. Well, Windows 7 is an operating system 6 months, very new.

--

And x64 is the bane of every programmer who uses always x86, especially the Windows registry. In 64-bit Windows systems, we have a x64 Windows Registry and other x86 Windows registry. As with the Windows registry, you have apps (x86 and x64) and processes (also x86 and x64). x86 applications, only see x86 Windows Registry, and x86 Services.

Exemplifying the problem: On Windows x64, if for example you run Regedit.exe, only see the x64 Windows Registry, and no such branch CCleaner settings (HKEY_CURRENT_USER\Software\Piriform\CCleaner), because Ccleaner is a x86 application and its settings are in the x86 Windows registry.

The services are recorded in the Windows registry. You see the issue is complex ... And, at the programming level not imagine. There may be a bug in the relevant environment detections

--

 

Returning, it could be that as you good say, the method of Diskeeper is more efficient.

Another possibility may be that Defraggler, is excluding the file paths in the application code (for example, has not yet been tested). Maybe I can be a matter of minimum amount of fragments in a file, or also by file size or by file type.

 

Another common cause of failure, or rather of omission, is not having permissions on the file. Diskeeper is more robust (install services) and reliably, every time you execute it, automatically runs with all privileges (administrator). You run Defraggler in Administrator mode, right?

 

 

But until we know what files are, no one will know how to fix the problem. Only speculate on the problem.

 

Could you help by listing the file path and size, that Diskeeper says they are fragmented. Of course, the next time you're fragmented these files.

 

Greetings!

[Aethec]

Exemplifying the problem: On Windows x64, if for example you run Regedit.exe, only see the x64 Windows Registry, and no such branch CCleaner settings (HKEY_CURRENT_USER\Software\Piriform\CCleaner), because Ccleaner is a x86 application and its settings are in the x86 Windows registry.

 

Wrong.

[Uranus One]

Hi Aethec!

Wrong.

Not possible. What version Windows are you?

With that application be watching the Windows Registry?

[Aethec]

If I run regedit on my x64 Win7, I can see CCleaner's options.

 

However, there are things the 32-bit programs can't do, like looking at C:\Windows\System32\ - but Defraggler is 64-bit on 64-bit Windows.

[Uranus One]

Well, sorry for my bad example, you're right. That's what I meant. x86 applications do not see the x64 Windows Registry. After translating and correct, and try to maintain consistency, my brain goes crazy.

 

Just pointing that Defraggler, being new on x64, may have some errors in the detections. Just a possibility. Programming is a sum of successes and failures, we are all human, and however you work as a team, the mistakes always happen.