Sometimes when you attempt to run Disk Defragmenter in Windows, your computer stops responding and sometimes even shuts down. You are finally doing the right thing by performing much needed computer maintenance, but if this problem is not solved even after you have run Scandisk, then maybe you have a serious error.
The disk defragmenter can also come up with a message saying that it could not move all the files on this volume. I had this message one day and thought it was ok. Who cares if disk defragmenter couldn’t move a file, however when I looked at the report log it told a different story. It had only moved one file and had 1899 that it couldn’t move. Now that was not good.
According to the Microsoft website this behavior can occur if your computer has been infected with one or more viruses, such as the w32.funlove.4099 or the vbs.network.b virus. Sometimes you can notice what file it hangs on or stops at. It is usually in the system32 that is contained in Windows itself.
Windows Stops Responding During Disk Defragmenter
Here are more possible causes:
- Sometimes a corrupt file can cause disk cleanup to stop working and cause so may different symptoms. I presume this could also be the case for the disk defragmenter. Therefore you should also see this article Disk cleanup stops working and will not remove files in Windows. If the cause is the same, then the solution is also.
- You can also try removing temporary files on your computer as something might be corrupt in there.
- Besides that it could also mean that your hard drive is on its way out. Of course you can easily do any number of tests to find this out. You can remove the hard drive and put it in an external drive (if it won’t boot in the computer) and test it that way.
When Windows stops responding during disk defragmenting it is not always something to be ignored.