After I run SCANDISK and it shows no errors, I get this DEFRAG006 Error, "Windows cannot access" part of my hard disk, and I'm to run SCANDISK again. It's a vicious cycle, and one I have not run into before. What to do?

My PC has recently started to exhibit the same behavior. I've run disk checking utilities. The drive comes back OK (including SMART scans). I have since taken to ignoring it. This has been going on for about a month and have yet to encounter any problems (other than that Windows sucks).

I am having the same thing happen to me when I run ScanDisk. Have you found any suggestions for fixing it. I have heard that the DEFRAG006 error could somehow wipe out a hard disk. I surely hope not. Thanks for your advice.

I am also having this same error "defrag006" when trying to run the Windows 95 disk defragmenter. So far all other programs seem to function normally. My concern is that I am unable to defrag my hard drive. Sure would like some suggestions.

Answer is at Microsoft Personal Support Services, enter search for "defrag006" and read Article ID: Q160043. Follow instructions throughly.

I maintain several Micron Millennia PC's with this exact problem. Following the Microsoft directions exactly yeild no results. The errors still come up every time I run Defrag. I have taken to just re-starting Defrag repeatedly (sometimes as many as 8-10 times) until the message doesn't come up. I have even tried replacing the perfectly good hard drive with a different brand/model, but the error still comes up. I sent a message today to Micron Tech support with the details of all I have tried to correct this problem. If they get back to me with a soultion, I will post it here.

Not exactly sure what I did to get rid of this error, but here's what happened. I'm running Win95 on a Thinkpad 365XD prior to OSR2 (Win95), BTW. When I got defrag006, I was told by the HDD reseller (Apricorn) that if I can't defrag, then I should return it for a new one, When I called the retail tech support that actually sold me the HDD (Compusa.net), I was told that this probably wasn't a problem since defrag may have encountered a file it couldn't move (special Win95 file?). I tried the Microsoft fix mentioned above (thanks), but it did not work. On a chance, I tried the last half the Microsoft fix later (this is the part where you defrag on free space, then files, then both) and it worked. In the interim I had deleted a directory containing about 10M so I'm not sure if defrag worked because of second try, or because of deleting the dir. But it worked.