> I have read through several posts regarding defragmentation problems and
> I haven't been able to locate an answer to my problem specifically, so I
> figured I would try to explain and see if someone knows of a solution.
First of all, I don't think anyone has actually demonstrated a genuine
"problem" with defragging in Vista.
I don't believe you have one, either. Vista defrag is designed to run
invisibly, in the background, with no user intervention and no user
feedback. Long run times of several hours (or even a few days) are not
unusual and no cause for concern.
Honestly, the best thing you can do is restore the proper weekly schedule
for the Vista defragger, and then forget all about it.
Having said that, I don't know why Vista defrag recommends a defragmentation
even after Auslogics has done its thing, but I'd be strongly inclined to
ignore it. I suspect that the opposite might be true, too: run the Vista
defrag, and then Auslogics. I bet Auslogics recommends a further defrag.
Finally, it is of course possible that your usage pattern is far enough away
from "normal" that Vista's defrag regime isn't appropriate. For instance,
if your laptop is switched off all the time except when you are using it,
and you use it hard, it is POSSIBLE the Vista defrag won't run for long
enough. In which case a manual run of Auslogics (or similar) would make
sense.
But I wouldn't worry about running one after the other and comparing their
fragmentation reports.
But I still think you should uninstall Auslogics, restore the proper
scheduling for Vista defrag, and then forget all about it. Fragmentation is
a non-issue in Vista.
SteveT
|
Similar Threads
