My experience (and that of others posting elsewhere) has been that this results in a page file that is has much worse fragmentation (e.g., > 1000 fragments, I saw one commenter say theirs had >26,000 fragments).

I suspect that what is happening is that the disk defragmenter allocates all the large blocks to existing files, so when you allocate a new page file after defragmentation, the new page file just gets the leftover pieces.

Three guesses on why there are only small pieces left over (may be a combination of all three):
1. on old disks with many OS system packs and hotfixes, system files become spread all over the disk, and the disk defragmenter can’t move files that are in use, and so the spaces in between them are small.
2. on old disks there may be sectors that have gone bad spread all over the disk. Can’t move those.
3. disk defragmenter and PageDefrag just defragment existing files, not free space. (In fact they may keep free space fragmented on purpose, so there will be space nearby when any file is extended.)

(I had hoped PageDefrag would move all the OS files [green slivers in disk defragmenter] together in larger blocks, but it doesn’t move them.)

Instead of actually deleting the page file, stop using the paging file without actually deleting it, so disk defragmenter can try to defragment it.

The initial portion of the pagefile will not become fragmented over time. Only when the system is forced to expand the pagefile will this occur. Windows will not do this without announcing this with a warning dialog. If you have not seen these warnings, the pagefile has not been expanded. In any event any pagefile expansion will be deleted on a reboot.

The proper way to prevent pagefile expansion is to set the initial size so this need never occur. Trying to do this by lowering the maximum setting is totally wrong and will severly impair performance or cause application failures.

If pagefile fragmentation is a problem then make sure the initial size is adequate and then use pagedefrag. Do this once and you will never have a fragmented pagefile again, even after months of heavy continuous use.

Larry Miller
Microsoft MCSA

(Yes, this is doable, & e.g. -> via this registry path area + its variables of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application so you can move the application event log file to another disk to unburden the main C drive of that task)

Thus, effectively helping to speed up its operations.

Credits Alexander Peter Kowalski on that idea from Windows IT Pro magazine article where he helped Mark Russinovich out pointing out this fact to him and that his program also had the pagefile.sys location hardcoded as well, but, even though he alerted Dr. Russinovich of this at that article on Windows IT Pro magazine forums, I do not think it has been fixed for the registry hives or the eventlogs (although Dr. Russinovich fixed them for pagefile.sys at Mr. Kowalski’s suggestions and reguest, using the methods Mr. Kowalski suggested).

Worth mentioning, with this in mind, are another two freeware programs; those being NTRegOpt and Erunt. http://www.larshederer.homepage.t-online.de/erunt/

These two download in a single package: Erunt creates a backup of your system registry including open hives at startup and saves it to your a file in user account where it can be accessed from the command prompt in the Recovery Console.

NTRegOpt optimises the open hives of yout NT registry that most defragmenters can’t get at by defragmaning and compacting.

Another point worth mentioning is that if you use Diskeeper (2007 or 2008) there is a boot-time runonce defragmentation option available from the program’s GUI which also defragments your MFT in addition to paging file.

Also in Diskeeeper is an option to pad out your MFT. (This is done manually with Diskeeper 2007 and automatically by Diskeeper 2008.) What this means is that when windows if first installed it creates a master file table with enough space for x many entries: This isn’t always large enough; and as the disk fills up it can cause the MFT to fragment causing system instability. Diskeeper resizes the MFT based upon an approximation of the expected number of files plus some, calculated by a complicated algorithm. This avoids MFT fragmentation as the disk fills up.