Defrag Stuck at 1% No Matter How Many Time I Run It

Anonymous
2010-11-10T13:11:29+00:00

Defrag is stuck at one percent even though I have ran it a dozen times completely, this was the case with my system reserve partition too a while ago it was stuck at 14%, now my system reserve partition when it is defraged returns to 0% but my system partition is stuck at 1% no matter how many times I run defrag it seems can that be solved anyhow?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-01-21T18:58:19+00:00

Neither the Auslogics or Microsoft Disk Defragmenters defragment the pagefile. If you allow Windows to manage the pagefile and the free disk space is less than 50% of the volume in which the pagefile resides, the pagefile fragments.

The way to avoid this problem is to place the pagefile in it's own partition or to have a fixed minimum = maximum pagefile created before the free disk space reduces below 50%.

This Article tells you how to get round the problem using the Auslogics utility

http://www.auslogics.com/en/articles/how-to-defrag/

Whther the Auslogics solution always works is questionable.  To recreate the pagefile you have to restart the computer. The shutdown causes entries to be written to files so that if there was already limited free disk space these entries start the fragmentation process once again. The new pagefile is created early in the boot process but the files and free disk space have already started to fragment. The Auslogics solution will certainly improve the situation but less so if the free disk space is say only 20% of the drive.


Hope this helps, Gerry Cornell

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

53 additional answers

Sort by: Oldest
  1. Anonymous
    2010-11-11T15:56:41+00:00

    what is so difficult to understand that the defrag tool skips larger files? So they are not defragmented and show as fragmented each time:

    In Windows XP, any file that is split into more than one piece is considered fragmented. Not so in Windows Vista if the fragments are large enough – the defragmentation algorithm was changed (from Windows XP) to ignore pieces of a file that are larger than 64MB. As a result, defrag in XP and defrag in Vista will report different amounts of fragmentation on a volume. So, which one is correct? Well, before the question can be answered we must understand why defrag in Vista was changed. In Vista, we analyzed the impact of defragmentation and determined that the most significant performance gains from defrag are when pieces of files are combined intosufficiently large chunks such that the impact of disk-seek latency is not significant relative to the latency associated with sequentially reading the file. This means thatthere is a point after which combining fragmented pieces of files has no discernible benefit . In fact, there are actually negative consequences of doing so. For example, for defrag to combine fragments that are 64MB or larger requires significant amounts of disk I/O, which is against the principle of minimizing I/O that we discussed earlier (since it decreases total available disk bandwidth for user initiated I/O), and puts more pressure on the system to find large, contiguous blocks of free space. Here is a scenario where a certainly amount of fragmentation of data is just fine – doing nothing to decrease this fragmentation turns out to be the right answer!

    http://blogs.msdn.com/b/e7/archive/2009/01/25/disk-defragmentation-background-and-engineering-the-windows-7-improvements.aspx

    I hope you understand it now. if not I gave not up.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-11-11T16:11:16+00:00

    no I still don't understand or have the time to read that especially after all the effort I already put into it with out any resolution from here

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-11-13T14:56:25+00:00

    I ran a disk check with both functions checked and after rebooting and running defrag it still sais 1% fragmented.

    The problem is that this should not be the case because on previous installations of Windows it would alwyas return to 0% fragemented files after running defrag like it should.

    What is different in this installation of Windows compared to the others where it will never go below 1%, or compared to other installations of Windows where the System Reserved partition would not go below something like 14%, on this installation my System Reserved partition after running defrag will go from whatever % fragmented to 0% which is what it is at right now but my primary partition will not go below 1% fragmented files.

    I belive this is a problem with how defrag is reading the files not how fragmented my files are. The readings are inconsistant; one partition reads wrong on one installation, then the same partition works great on another installation and the primary partition reads wrong but the System Reserved partition works great.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-11-13T18:42:22+00:00

    I gave it up. The blog entry explains everything. Read it!


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    Was this answer helpful?

    0 comments No comments