This article was previously published under Q136836
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
When you run Disk Defragmenter, the progress gauge may not move for a longtime, even though it seems that the hard disk is being accessed. In somecases, Disk Defragmenter may seem to stop responding (hang). This problemfrequently occurs when Disk Defragmenter is between 5 and 10 percentfinished.
This problem can occur when Disk Defragmenter encounters an area on thehard disk that takes a long time to defragment, but for which DiskDefragmenter did not reserve space on the progress gauge. This problemtypically occurs when Disk Defragmenter underestimates the amount of timeit will take to defragment a particular area of the drive.
In particular, because removing deleted folder entries can take a longtime, emptying the Temporary Internet Files folder or deleting a largenumber of files from another folder on your hard disk can cause thisproblem to occur. When the problem occurs for this reason, it occurs whenDisk Defragmenter is between 5 and 10 percent finished because this iswhen Disk Defragmenter removes deleted folder entries.
The Norton Desktop for Windows Smartcan tool creates an empty folder whoseformat can also cause this problem to occur. Disk Defragmenter reserves noprogress gauge space for this folder, but often takes up to 30 minutes toprocess the folder, making sure that the folder is actually empty andmarking the corresponding clusters so that they can be used.
Allow Disk Defragmenter to continue as long as the hard disk lightindicates that the drive is being accessed. Do not use the Close Programdialog box to quit Disk Defragmenter. The process gauge will start movingagain and Disk Defragmenter will start responding again when DiskDefragmenter finishes processing the area on the hard disk that is takinga long time to defragment.
Microsoft has confirmed this to be a problem in Windows 95, Windows 95 OEMService Release 1, and Microsoft Plus! for Windows 95. This problem doesnot occur with Windows 95 OEM Service Release 2.