Sometimes I have been in a similar situation, where I attempted to run Disk Defragmenter and it stops mid-process and says that it cannot continue. I do not recall the exact wording, but the message I received was also either about file/folder corruption, or some kind of disk error, or the volume being dirty, and it would advise me to run CHKDSK to fix that problem before it would let me defragment.
I would check if C: is being recognized as being "dirty" - I don't know your level of computer knowledge (though I'm not an expert), so forgive me if I state things too basicly:
On the Start menu, there should be a "Run" button; click that. Alternately, it can be accessed through holding the Windows key on the keyboard and then pressing the R button. After the Run box appears, in the white box after Open:, type "cmd" (without quotation marks) and press Enter (or click OK).
This should bring up the command prompt box. Type "fsutil dirty query C:" (C doesn't have to be capitalized) and press Enter. This command
does not change or activate or set anything; it asks whether the C: drive has been marked as "dirty" and should either output something like "Volume - C: is NOT dirty" or "Volume - C: IS dirty", though the capitalization (etc). may be a bit different.
If C: is not said to be dirty, than it's not the situation I've experienced before, and don't know anything else about what you should do. If, however, is IS dirty, read on:
This information is based on a combination of my past experiences and information from Microsoft articles I've read repeatedly before and just again right now; there is some speculation about possibilities for situations different than my own, though I've noted those to be such.
If C: has been marked as dirty, your computer is automatically going to run the CHKDSK
program the next time you restart (or turn on after having shut down) your computer; if this is the case, I'd recommend backing up the important data on your computer before you restart it or turn it off, as there is a risk of data loss when CHKDSK runs. I personally have never lost any data other than the files/folders already marked as corrupt, and have usually either had those backed up elsewhere or been able to recover them.
However, as I see your Disk Defrag says that the file it notices to be corrupt (it may not be the only one, as Defrag stopped after analyzing 10% of your drive and noticing the first corrupted file/folder - if there are others on the other 90% it didn't get to, it didn't continue to analyzing that part) is part of your system folder and not merely data (pictures/media) like mine had been, I'm not sure if there will be problems I haven't personally experienced before as I haven't had that particular kind of situation.
Regardless, I would backup what you consider important on C:. You may want to look at the Microsoft page on CHKDSK that I linked to, as it has some useful information about what CHKDSK does (read it as if the /f parameter applies). For one, it says "If you use chkdsk /f on a very large disk (for example, 70 gigabytes) or a disk with a very large number of files (for example, millions of files), chkdsk might take a long time (for example, over several days) to complete. The computer is not available during this time because chkdsk does not relinquish control until it is finished." To call 70 GB large, the article is clearly dated; I have a 144.82GiB hard drive, and I don't remember it ever having taken more than 24 hours to run CHKDSK for me (I used to have probably up to 800,000 files on it) - now that I've cleaned it out more (goodbye to millions of tiny files in subfolders within subfolders within subfolders) and have less than 300,000 files on it, it usually takes less than 15 hours, sometimes even just 8, and I'm actually using the /R parameter, which takes longer than /F by itself would (/R includes /F, among other things).
I am getting off topic, so I apologize - I just looked at your profile, and noticed a January post referring to a C: with 55.89 GiB total space and 44.05GiB used at that time - if that's the drive you're referring to, I would think it wouldn't take a day, or even half that, unless you have a real ton of files on there.
When you restart and CHKDSK runs, it should tell you what it's doing while it's doing it, with percentage of completion for each category; I remember some categories are way slower than others, and sometimes minutes (or dozens) would go by before another 1 percent would go by for that particular category, but I had over 500,000 files on my computer then, I think.
After CHKDSK runs and your computer boots, if you want to see the results/log, these are the steps to follow:
Open Run again and this time put in "eventvwr.msc" w/o quotes, then click on Application in the left. If it isn't already set to appear by date, I'd click on the 'Date' button on the top of its respective column until the most recent entries appear at the top (that may take one or two clicks, not sure which), then look for an entry with "Winlogon" under Source and "1001" under Event; the time should be the same as when the CHKDSK process actually finished. Doubleclicking that line should show you the log/results of the CHKDSK process, if you had wanted to see that (it should have appeared on your screen earlier anyway, though in my case after it finishes it soon boots to the login screen, so if I'm not actually at the monitor when it completes, I don't see that moment where it shows the results). I'd suggest you then save the contents of that log to a separate text document somewhere else, in case you for some reason need to look at it again.
I would then repeat the fsutil command into cmd that I mentioned earlier: if it now states that C: is not dirty, I would run Disk Defragmenter and then Analyze C: again, and Defragment it as you attempted earlier; I would think it should now defragment 100% without stopping. This, however, does not address anything related to why or how you had C: become dirty and files/folders/indexes/whatever-it-was corrupted, and whether that may or may not be something serious that you should look into or perform certain steps or tests or safeguards - you'll have to ask those more knowledgeable on that topic.
If fsutil says that C: is still dirty, or you have files stated to be corrupted again, I would suggest asking about your hard drive in the Internal Hardware forum, but that's just what I would do; I'm not claiming to be super-knowledgeable here.
Edited by teiresias, 07 November 2010 - 03:02 AM.