[be very careful wiping freespace]

Well my guess would be that your HD was maybe on the way out and running a 35 pass(!) wipe just pushed it over the edge. Personally I'm with Nergal on this one, its completely unnecessary and puts way too much extra strain on peoples HDs when they are assuming they should run it as it must be beneficial, and of course 35 pass must be better than 1 right?

 

But then that's the reason it's in the 'Advanced' section. Having said that if it was in a section with a big flashing "Do not use if you don't understand" warning, people would still tick all the advanced boxes and run it regardless

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Ok you have made it clear that I must be pretty stupid and that it is my fault that I trashed my own drive by using this tool. Ok. Thanks for the help then. Later and thanks again. Great forum. Keep up the good work. Is that about it then? Alrighty then!

[be very careful wiping freespace]

Don't fear CCLeaner just don't use (useless IMHO) Wipe FreeSpace.

 

Devs I hate to say it but once again I renew my plea for WipefreeSpace to be removed. If people really want it, make it a seperate GUI program but. . . sooooo many issues

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

So I guess you are saying that this has been an issue before with others? Please clarify for my tech-stupid self. Thanks.

Also, I think I saw a long list of error message scroll past and then disappear during my attempts to boot. They all had something to do with partition drivers.

[be very careful wiping freespace]

I have been using the cleaner for a year or more and no problems...UNTIL I decided that the guttman wipe was taking too long and I opted to hit the cancel button. It was wiping free-space at the time. I am contacting you via my "new" computer which I just got up and running.

 

When I tried to boot up the next day with the old system, it would not launch windows, even in safemode. Took it to the shop. HD had fried sector. This problem occured the very next session after cancelling the wipe of free space. I had no previous boot problems or system problems for that matter. Be very careful. This mistake costed me 200 bucks.

 

At this point, I am afraid to run cccleaner on my new system. Just thought you all might like to know about this.