I know it sounds terrible, but this is exactly what happened.
I made a free space erasure and only this, and now the comp reboots
and checks disks over and over again without ability to reboot really.
I have to say thhat i know my way around comps,
so this would not be a problem here.
Anyone can help?
Thanks,
D B
What operating system?
AMD, Win 7 Home Premium, C and D disks.
But The q is HOW could it happen, when the promise was that ONLY FRRE SPACE will be deleted?
I double checked it when making the click.
I clicked F8 on reboot and chose Last known good config. Hold fingers.
Let us know what happens please.
It returns repeatedly to the check disk feature from any config chosen.
I take it to the shop tomorrow.
In any case, I demand, no less, an explanation from Piriform.
We'll go from there.
I'll keep posting.
I work from home, and i'm lucky for the laptop.
1st time after installing a sftwr in many many years that something like this happens to me.
And sftwrs I installed, believe you me.
Here's the explanation (not from Piriform but still valid).
A hard drive wears out. There is only so much read and writing that a Hard Disc Mechanism can do, this is a limited amount. When you chose to wipe the drive, especially if you had multiple passes set you pushed the drive past its limit. While it is regrettable that this happened, it's not really a problem with ccleaner as much as it was time for your drive to go.
Look, this is one explanation, that might be true. But if it is so,
then CCleaner people must specify it explicitly.
Let's see how it does tomorrow.
In any case, what will be the limt definition?
Of course, you would say depends on what you/I are doing.
Sounds swallowable? Not to my mind.
Wiping free space can stress a hard disk - that holds true rather it's CCleaner or some other tool doing it.
Does the PC boot using a linux Live CD?
dbjes, I also would be very interested in how the live CD goes if you try it.
Might be cheaper than a trip to the shop.